In this module, we treat the VCK190 board as if it were a custom solution tailored to our customer’s specific needs. Our approach involves leveraging the AMD Versal™ Adaptive SoC Extensible Part Support Example Design and harnessing the power of a pre-built Linux common image, along with the createdts command, to generate essential software components. These components are then used to construct a dedicated embedded Versal acceleration platform designed exclusively for our customer’s board. As the final step, you will run several applications to test this platform. If you merely create a platform to validate your kernels, then the Vitis Platform Quick Start would be a quick choice for you.
For your reference, the overall structure of this example system closely resembles the following:
In a general Vitis acceleration platform design, the Vitis platform and application development can be divided into these parts:
Platform hardware design creation in the AMD Vivado™ Design Suite. It exports an XSA file with clock, reset, AXI interface, and interrupt signals and properties.
Platform software preparation with common image or using PetaLinux tool, including Linux kernel, rootfs, device tree, and boot components.
Platform creation in Vitis to combine all hardware and software components and generate XPFM description.
Create applications in Vitis against the platform. Vitis generates a host application, xclbin, and
sd_card.imgto a SD card or update host application and xclbin to an existing SD card.
In this module, you will utilize the Versal Extensible Part Support Design (CED) to create a hardware design. In contrast to the Versal Extensible Design, which is used in Vitis Platform Quick Start, the part support design takes a slightly different approach. Specifically, it empowers you to handle board-level configurations independently. This includes configuring processing system (PS) side peripherals and fine-tuning parameters related to double data rate (DDR) as needed. This flexibility ensures that you have full control over the configuration process to meet the unique requirements of your application.
To prepare the software components, you will utilize common image released by AMD and
createdts command to generate the device tree file. After the whole software and hardware components are ready, you will package the platform.
In each step, you will validate the generated files to make sure they work as expected. A frequent test methodology can help to narrow down the root causes if any error occurs. Lastly, you will run several test applications on this platform to test this platform.
The total flow is similar the following:
Navigate through these steps with the following table of contents links.
createdtsadd support for your device tree.
From this version, you begin to use pre-built Linux common image instead of building Linux components with PetaLinux because the pre-built common image provides most common features for Vitis acceleration, and it can help expedite the platform creation process. If you wish to leverage the PetaLinux tool to customize your system, refer to the PetaLinux Customization Tutorial.
Simplify the device tree generation flow by using the newly introduced
Add validation for every step’s output.
In Step 1, the Vivado project exports the XSA for hardware and hardware emulation seperatedly. When creating the platform in step3, it is recommended to provide seperate XSA for hardware and hardware emulation.
Copyright © 2020–2023 Advanced Micro Devices, Inc