Packaging the System

Vitis Unified Software Platform Documentation: Application Acceleration Development (UG1393)

Document ID
UG1393
Release Date
2023-07-17
Version
2023.1 English
Figure 1. Linking the System Design

While a v++ linker-generated fixed .xsa can be used to create custom boot, and software platform images as described in the Versal adaptive SoC System Software Developers Guide (UG1304), the Vitis v++ --package command provides ease-of-use flows to generate SD card and other Flash images as well as .xclbin device binary images for software applications that employ the Xilinx Runtime (XRT). The v++ --package step, or -p option, packages the final product at the end of the v++ compile and link process. As described in Packaging for Embedded Platforms, this is a required step for all Versal platforms, including AI Engine platforms, and embedded processor platforms.

The --package Options let you package your design and define various files required for booting and configuring the AMD device for use during emulation or in production systems. It collects the various elements to create an SD card, or other means to program the device, to define the operating system, and to load the application and kernel code.

Tip: After packaging the design the AMD Vitis™ compiler generates a v++.package_summary that includes the packaging command and log file. The summary file can be viewed in Analysis view of the Vitis analyzer alongside the compile, link, and run summaries as explained in Working with the Analysis View (Vitis Analyzer).