Skip to content

Latest commit

 

History

History
100 lines (70 loc) · 7.47 KB

README.md

File metadata and controls

100 lines (70 loc) · 7.47 KB
Raw

Vitis™ Platform Creation Tutorials

See Vitis™ Development Environment on xilinx.com

Vitis Custom Embedded Platform Creation Example on KV260

Version: Vitis 2022.1

Note: Since KV260 BSP only releases 2022.1 version, this tutorial will skip 2022.2. The next release for this tutorial would be 2023.1.

Kria KV260 Vision AI Starter Kit is the development platform for Kria K26 SOM. The KV260 is built for advanced vision application development without requiring complex hardware design knowledge. It's based on the UltraScale+ MPSoC technology similar to ZCU104 evaluation board. In this example, we will extend the ZCU104 custom embedded platform creation example to KV260 Vision AI Starter Kit.

To highlight the differences between KV260 and ZCU104, this example will simplify the descriptions of general steps that are shared between all MPSoC platforms, but add more KV260 specific contents. If you have question in some steps, please cross reference ZCU104 custom embedded platform creation example or ask questions in Github Issues page.

This example total system structure is like the following for your reference.

missing image

Custom Platform Planning

The platform we create should be able to run these applications finally

  • Vitis acceleration examples like Vector Addition
  • Vitis-AI applications will be available in the future.

The hardware design of the platform would provide basic support for Vitis acceleration. It's similar to the ZCU104 example.

In regards of software setup, we will use the common image since it can expedite the process of platform creation.

Kria SOM Architecture and Vitis Acceleration Considerations

Kria SOM has some ease-of-use designs for application developers. It provides software-like development experience on FPGA and SoC, such as real time reloading applications without rebooting the system. In order to allow updating PL design without rebooting Linux, it boots Linux from ARM Cortex-A53 and loads FPGA bitstream using Linux. To ensure the board can always boot successfully and prevent the board get into brick status by accidental mistakes, Kria SOM boot flow forces to boot Linux from QSPI mode and the boot firmware in QSPI is read only. Linux will mount rootfs in the SD card. User can update the rootfs in the SD Card.

Vitis platform and application development can be divided into these parts:

  1. Platform hardware creation in Vivado. It exports an XSA file with clock, reset, AXI interface and interrupt signals and properties.
  2. Platform software preparation with common image or using PetaLinux tool, including Linux kernel, rootfs, device tree and boot components.
  3. Platform creation in Vitis to combine all hardware and software components and generate XPFM description.
  4. Create applications in Vitis against the platform. Vitis generates host application, xclbin and sd_card.img.
  5. Write sd_card.img to SD card or update host application and xclbin to an existing SD card.

Since Kria SOM Starter Kit provides an off-the-shelf boot image and has its enhanced boot sequence, Vitis platform developers and application developers can skip some steps above. Here is a summary for what needs to be done by Kris platform and acceleration application developers.

Missing Image

Procedure Required Actions Output Skipped Actions
Platform Hardware Same as step 1 XSA N/A
Platform Creation Same as step 2; Generate device tree overlay for platform PL of XSA; Create Vitis platform pl.dtbo, sysroot and XPFM skip adding the boot components
Application Creation Same as step 3; Create application Host App, XCLBIN skip generating the sd_card.img
Transfer files and run Use scp to copy generated files to Linux partition on SD card skip writing sd_card.img

Note: In step 2, after extracting the common image there are a lot of output components, the only valuable output product in this case is sysroot. It's used for host application cross-compilation. Since the boot images of KV260 Starter Kit is fixed, user doesn't need to generate any boot components, e.g., FSBL, etc.

Note: In this case we assume you start to do this experiment after you have already had your board booted up successfully. If you do not please refer to kv260 getting started page.

The following chapters will explain the details about these steps.

Step-by-Step Tutorial

We'll introduce the platform creation steps in the following pages. Each page describes one major step in the platform creation process.

Let's start from step 1: Vivado Design.

References

Copyright© 2022 Xilinx