What guidelines should be followed while using a custom XSA/HDF generated from Vivado in a PetaLinux or Yocto environment?

Moderator · June 22, 2026, 12:37pm

The Validated & exported custom XSA/hdf/vivado file should be imported in Petalinux/Yocto flow.

The Petalinux or Yocto should be built with the given iWave BSP.

Use below command in the respective build directory.

Petalinux:
petalinux-config --get-hw-description=system.xsa

Yocto:
Replace the xsa/hdf in hw-description folder and update the checksum in the

conf/machine/<machine-name>.conf file

During the build process, pl.dtsi is generated automatically from the XSA. Use below command to find the file.
find . -name “pl.dtsi”

Based on the pl.dtsi file, modify/remove the corresponding nodes in the system-user.dtsi and save the file.

Use the below commands to clean the fsbl & pmu firmware and re-build the project.

Petalinux:
petalinux-build -x distclean -c fsbl-firmware;petalinux-build -x distclean -c pmu-firmware;

petalinux-build

Yocto:
bitbake -c cleanall fsbl-firmware;bitbake -c cleanall pmu-firmware;
bitbake petalinux-image-minimal

For further inquiries, please get in touch with mktg@iwave-global.com