• View
• Edit
• History
• Print

Back to FPGAs

PetaLinux appears to have some relationship with Yocto, maybe built on it.

Setup

Install the Petalinux base to a petalinux/<release>/ folder location, with the name being a release time like 2020.2. This provides a settings.sh script you'll run whenever you want to do Petalinux commands in your project folder.

The project will be installed for a specific board and release and acts as your working folder where you execute the Petalinux commnds (for example xilinx-zcu106-2020.2/) and this will come with a prepared .gitignore file.

The board installation folder sits at 42GB, while the petalinux base sits at just under 10GB. We don't want to store all that in gitlab. When you run the "git store prep" command petalinux-build -fx mrproper it removes a ton of stuff and the board working folder goes down to 7GB. But not all of that is stored. There is a pre-canned .gitignore file created when you start the project and it has a ton of stuff to leave out, including the pre-built/linux/ folder which is 5GB. So it's really down to 2GB of stuff that you store.

Commands

To bring up the menuconfig system, use petalinux-config at your project directory.

Example

ZCU106 PetaLinux steps to get started with default build:

1. Install tftpd server and create /tftpboot directory
2. Install PetaLinux base
3. Set up environment via script (source ?)
4. Install matching board BSP
5. Create a project using the ZCU106 BSP (petalinux-create ?)
6. Build system images which populates /tftpboot with files (petalinux-build ?)
7. Power the board and stop it at U-boot
8. Set the serverip and ipaddr EVs (setenv ?)
9. Get PXE config (pxe get)
10. Boot (pxe boot)

Once it's running, you can use the devmem command from BusyBox to access AXI memory locations.