Module 07: PetaLinux - 2024.1 English

Create PetaLinux: Creating the PetaLinux Project with a BSP

First, create the PetaLinux project from a board support package (BSP) with the petalinux-create command. A BSP is a collection of software drivers and an operating system on which your Linux applications are built. It is the support code for a given hardware platform or board that helps in basic initialization at power-up and helps software applications to be run on top of it. Because you use a VCK190 board, the xilinx-vck190-v2024.1-final.bsp package is required.

mkdir -p build;
cd build;
petalinux-create -t project -s <PATH-TO-BSP>/xilinx-vck190-v2024.1-final.bsp -n vck190_linux

These commands create a new PetaLinux project directory structure under build/vck190_linux.

Config PetaLinux: Updating the PetaLinux Project with an XSA

Next, update the PetaLinux project with the XSA created in Module 04. The XSA contains the configured PS and the PL kernels you want to control from your Linux applications. This step enables you to make the PetaLinux tools software platform ready for building a Linux system, customized to your hardware platform. Import the hardware description with the petalinux-config command by giving the path of the directory containing the XSA file as follows:

petalinux-config -p build/vck190_linux --get-hw-description ../Module04_AI_Engine_and_PL_Integration/build/rev1/hw –silentconfig

The --silentconfig option allows you to reuse a prior configuration used during the petalinux_create command.

Config PetaLinux: Customizing the Root File System

Edit the build/vck190_linux/project-spec/configs/config file. In this configuration file, ensure that the root file system type is EXT4 by setting the following config options:

CONFIG_SUBSYSTEM_ROOTFS_EXT4=y
CONFIG_SUBSYSTEM_RFS_FORMATS="cpio cpio.gz cpio.gz.u-boot tar.gz jffs2 ext4"

To ensure the EXT4 root file system is generated, the bootargs in the uio-system-user.dtsi must be as follows:

 bootargs = "console=ttyAMA0 earlycon=pl011,mmio32,0xFF000000,115200n8 clk_ignore_unused root=/dev/mmcblk1p2 rw rootwait rootfs=ext4 uio_pdrv_genirq.of_id=generic-uio";

Lastly, the config file specifies the machine name as follows:

CONFIG_SUBSYSTEM_MACHINE_NAME="versal-vck190-reva-x-ebm-02-reva"

Next, add user packages by appending the CONFIG_* lines to the build/vck190_linux/project-spec/configs/rootfs_config file. By default, most config options are set to “is not set.” Update the following config options to =y:

• Packages for base XRT support: This is required for the AMD Vitis™ application acceleration development flow. It includes XRT and ZOCL.

CONFIG_packagegroup-petalinux-xrt=y

• Packages for easy system management (recommended):

CONFIG_dnf
CONFIG_e2fsprogs-resize2fs
CONFIG_parted
CONFIG_imagefeature-package-management=y

• Packages for libsysfs, libmetal, and OpenAMP libraries: The libmetal library provides common user APIs used to access devices, handle device interrupts, and request memory across different operating environments. OpenAMP builds on top of libmetal to provide a framework for remote processor management and inter-processor communication.

CONFIG_libmetal=y
CONFIG_open-amp=y
CONFIG_libsysfs=y

• The package for the AI Engine:

CONFIG_ai-engine-driver=y

• Enable debug tweaks:

CONFIG_YOCTO_ENABLE_DEBUG_TWEAKS=y

• Enable PetaLinux auto login:

CONFIG_auto-login=y

Config Petalinux: Updating the Device Tree

The DTSI file is provided for you. Copy the uio-system-user.dtsi file to the PetaLinux project.

cp uio-system-user.dtsi build/vck190_petalinux/project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi

This is a user-modifiable PetaLinux device tree configuration file. Open the uio-system-user.dtsi. This file creates a generic-uio driver for each PL kernel instance (dlbf_data_00, dlbf_data_01, dblf_coeff_00, and so on). With this device tree configuration, communicate to the memory addresses of the PL kernels through these UIO drivers without actually knowing the physical addresses.

Config Petalinux: Customizing Kernel Configuration

Create the vck190_linux/project-spec/meta-user/recipes-kernel/linux/linux-xlnx/bsp.cfg file. This is a Linux kernel config fragment file with the following config options:

CONFIG_I2C_XILINX=y
CONFIG_GPIO_XILINX=y
CONFIG_FPGA=y
CONFIG_FPGA_MGR_VERSAL_FPGA=y
CONFIG_XILINX_INTC=y

These configuration settings enable device drivers for general purpose GPIO IP, I2C IP, FPGA Manager, and Interrupt Controller. These drivers are not used in the Linux PS host application.

Config Petalinux: Clean-Up

Run the following command to clean up the configuration files you edited:

petalinux-config -p build/vck190_linux --silentconfig

Build PetaLinux: Building the PetaLinux Image

Build the PetaLinux system image with the following command:

petalinux-build -p build/vck190_linux

This step generates a device tree DTB file, platform loader and manager firmware (PLM), processing system management firmware (PSM), Arm™ trusted firmware (ATF), U-Boot, the Linux kernel, a root file system image, and the boot script for an AMD Versal™ adaptive SoC. Finally, it generates the necessary boot images. The compilation progress shows on the console when executing this command.

When the build finishes, the generated U-Boot and Linux images are stored in the build/vck190_petalinux/images/linux directory.

Build Petalinux: Building the SDK (Target Sysroot Generation)

The OpenEmbedded build system uses BitBake to generate the software development kit (SDK) installer script standard SDKs. PetaLinux builds Yocto SDK and installs it. The installed SDK can be used as a sysroot for the application development. Build the SDK with the following command:

petalinux-build -p build/vck190_petalinux –sdk

This command builds the SDK and copies it at build/vck190_petalinx/images/linux/sdk.sh.

Build PetaLinux: Installing the SDK (Target Sysroot Generation)

The generated SDK must be installed/extracted to a directory. The following command extracts the SDK to the default installation directory build/vck190_petalinux/images/linux/sdk/.

cd build/vck190_petalinux
petalinux-package –sysroot

Build PetaLinux: Generating the Boot Image

Lastly, generate the boot image (BOOT.BIN). A boot image usually contains a PDI file (imported from the hardware design), PLM, PSM firmware, Arm® trusted firmware, U-Boot, and DTB.

cd build/vck190_petalinux
petalinux-package --boot --u-boot

This generates BOOT.BIN, BOOT_bh.bin, and qemu_boot.img in the build/vck190_linux/images/linux directory. The default DTB load address is 0x1000. For more information, see the Bootgen User Guide (UG1283).

Support

GitHub issues will be used for tracking requests and bugs. For questions go to forums.xilinx.com.

_{Copyright © 2020–2024 Advanced Micro Devices, Inc}

^{Terms and Conditions}