AMD provides prebuilt platforms for select embedded evaluation boards. AMD recommends that you use the Vitis Integrated Flow, which enables loosely coupled, parallel development of subsystems on the evaluation board while the platform development team brings up a custom platform. Working this way enables rapid progress. With a prebuilt platform, you can develop, integrate, and test the subsystem independently on a pre-verified, known-good foundation. After the subsystem is sufficiently advanced and stable, you can integrate it with the appropriate version of the custom platform. This approach streamlines the system integration process.
Prebuilt embedded base platforms are installed with the Vitis installer. For a list of supported platforms, see Vitis Embedded Platforms in the Vitis Software Platform Release Notes (UG1742).
All prebuilt AMD platforms include a software platform with a Linux domain that supports the Xilinx Runtime (XRT). You can download common software images from the Embedded Platforms download page.
The common image packages contain the following components:
- Prebuilt Linux kernel.
- Prebuilt root file system.
- Boot files (
system.dtb,U-Boot.elf,boot.scr,bl31.elf, and so on). -
sdk.shscript to generate the sysroot.
Prebuilt Platform Naming Convention
Starting with 2026.1, prebuilt Vitis embedded platforms follow the same naming convention as the GitHub hardware platform source code, where Git branches control the versions. These platforms are prepared for AMD EDF.
<Board>_<Feature>For the full list, see AMD Yocto HW Platforms.
kv260_base, which still requires
PetaLinux.Three boards still use the older Xilinx naming convention for prebuilt platforms, because they are still early access for EDF:
<Vendor>_<Board>_<Feature>_<Vitis_Tool_Version>_<Release_Version>The following boards still use PetaLinux:
-
xilinx_vck190_base_202610_1 -
xilinx_vck190_base_dfx_202610_1 -
xilinx_vek280_base_202610_1