Please note that the 2020.3 release is only for device enablement of the Xilinx Versal ACAP evaluation platforms. For all other devices and evaluation platforms, please use the standard 2020.2 release.
The PetaLinux Tools installer is downloaded using the below link. The installer checks for the required host machine package requirements followed by license acceptance from the user. It can be installed in any desired path. Note: All BSPs (located below) require the PetaLinux Tools to be installed first.
Download only the required BSP(s) depending on the evaluation board that is being used. All BSPs have a prebuilt directory with bootable images. Hover your mouse over the download hyper-link to see a description of the BSP contents.
The ‘common image’ packages below contain a prebuilt Linux kernel and root file system that can be used with any Versal board for embedded Vitis platform developers.
These files need to be copied to an SD flash card along with the platform specific boot image (boot.bin) available from the Vitis Embedded Platform page.
Also included is the ‘sysroot’ required for embedded Vitis platform application development. The sdk.sh script must to be used to setup the compressed Yocto Project SDK on a Linux development host properly.
Note: PetaLinux Tools installation is not necessary to use the common images. The licenses and sources used to create the common image content is provided below.
This section contains all the 3rd party open source Licenses and Source code files. Please refer to this README for more details.
This section also provides the optionally downloadable ‘License and Sources’ for each BSP listed above.
To get the license and source details for a PetaLinux project please refer to Chapter 2 in UG1144 - PetaLinux Tools Documentation Reference Guide.
sstate-cache and downloads are only required when the PetaLinux Tools/BSP build does not have access to internet. sstate-cache files are provided per architecture and downloads provided are irrespective of the architecture.
Please see README to get more details on how to use sstate-cache per architecture.