./sdk.sh -d <Install Target Dir>to install PetaLinux SDK. Use the
-doption to provide a full pathname to the output directory. For example:
./sdk.sh -d .. . means the current directory.
NOTE: The environment variable LD_LIBRARY_PATH must not be set when running this command.
Note: Sysroot is not mandatory components for the platform itself. It is the cross compile tool prepared for applications compilation.
Create a Vitis platform.
For this example, you will use the Vitis Unifeid IDE to create the Vitis Platform. Got to
WorkSpacedirectory and follow steps below to create the platform.
Run Vitis by typing
vitis -w .in the console.
-wis to specify the workspace.
.means the current workspace directory.
In the Vitis Unified IDE, from menu select File > New Component > Platform to create a platform component.
On the Create Platform Component setup dialog
Enter the component name and location. For this example, type
kv260_customand use default location. Click Next.
Click Browse button, select the XSA file generated by the Vivado. In this case, it is
Set the operating system to linux.
Set the processor to psu_cortexa53.
Check the option Generate boot artifacts. Then click Next.
Note: Enabling this option will trigger the tool to automatically generate a PMU firmware domain and an FSBL (First Stage Boot Loader) domain into the platform
Review the summary and click Finish.
Note: After a few moments, the platform component will be prepared and available in the component view. Simultaneously, the platform configuration file,
vitis-comp.json, will be automatically displayed in the main view. Users can access the
vitis-comp.jsonfile by expanding the Settings section under the platform component.
Set up the software settings in the Platform configuration view by clicking the Linux On psu_cortexa53 domain, browse to the locations and select the directory or file needed to complete the dialog box for the following:
Display Name: update it as
Bif file: Click the button to generate bif file or click Browse to select existing bif file.
Note: The filenames in
<>are placeholders in the bif file. Vitis will replace the placeholders with the relative path to platform during platform packaging. V++ packager, which runs when building the final application#, would expand it further to the full path during image packaging. Filename placeholders point to the files in boot components directory. The filenames in boot directory need to match with placeholders in BIF file.
<bitstream>is a reserved keyword. V++ packager will replace it with the final system bit file.
Pre-Built Image Directory: Browse to xilinx-zynqmp-common-v2023.2 and click OK.
DTB File: Browse to mydevice/psu_cortexa53_0/device_tree_domain/bsp and select system.dtb, then click OK.
Note: If the directory you specified for Pre-build image directory already contains DTB file, this DTB field will be automatically updated.
FAT32 Partition Directory: This directory is used to add additional file to the fat32 partition. User can set it according to your requirement.
QEMU Data: This Directory is used to add additional file for emulation. User can set it accordingly.
Note:: Qemu Args File and Pmu Args File are populated by the tool automatically. If there are additional QEMU settings, please update it accordingly.
Select kv260_custom platform component in the flow navigator, then click the Build button to build the platform.
Note: The generated platform is placed in the export directory. BSP and source files are also provided for rebuilding the FSBL, if required, and are associated with the platform. The platform is ready to be used for application development.
Note: Once the compilation is complete, users can find the XPFM file by expanding the Output directory, which offers a structured view of the output. The actual file path of platform file is located in the
WorkSapce/kv260_custom/export/kv260_custom/directory. Additionally, users can access the full path of the platform file by hovering the mouse pointer over the XPFM file.
Note: The Vitis Unified IDE will find the boot-related files mentioned in the software components in begin of this step from Pre-buit image directory and place them in the boot folder of the platform.
If you create a Vitis application component in the same workspace as this platform component, you can find this platform available in the platform selection page in the application Creation wizard. If you want to reuse this platform in another workspace, add its path to the
PLATFORM_REPO_PATHSenvironment variable before launching the Vitis GUI, or use the “Add” button on the platform selection page of the Vitis GUI to add its path.