In this step, you will create an AMD Vitis™ platform running the Linux operating system. The Vitis platform relies on several essential software components that must be prepared in advance. To expedite the process, AMD offers common software images for quick evaluation, and you could leverage these common images to jump-start your project.
Please note that Device Tree Blob (DTB) files are not included in the common image package because different platforms may have unique device peripherals. You can use the createdts
command to generate the device tree file tailored to your specific platform.
If you require further customization of the system image, such as modifying the kernel or root file system (rootfs), please refer to the the PetaLinux customization page customization page for detailed instructions.
Listed below are the software components necessary for this platform:
Component | Conventional Path or Filename | Description | Provenance |
---|---|---|---|
Boot components in BOOT.BIN | fsbl.elf | First stage boot loader | Generated with platform creation |
Boot components in BOOT.BIN | pmufw.elf | Chip internal power and security related management | Generated with platform creation |
Boot components in BOOT.BIN | bl31.elf | ARM trusted firmware/ secure monitor | Extracted from common image |
Boot components in BOOT.BIN | u-boot.elf | Second stage boot loader | Extracted from common image |
Boot components in BOOT.BIN | system.dtb | Device tree information file | Generated from "createdts" command |
Boot components in FAT32 partition of SD card | boot.scr | U-boot configuration file to store in FAT32 partition of SD card | Extracted from common image |
Linux Software Components | Image | Linux kernel Image | Extracted from common image |
Linux Software Components | rootfs.ext4 | Linux file system | Extracted from common image |
Linux SDK | sysroot | Cross compile and header files | Extracted from common image |
Note: The Kernel Image, Linux file system, and Sysroot are not mandatory components for the platform itself. Instead, they are utilized by applications to generate the SD Card Image.
As most of the components are extracted from the common image package, we will prepare the common image first.