Packaging the System - 2023.2 English

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

Document ID
Release Date
2023.2 English
Figure 1. Linking the System Design

The Vitis v++ --package command generates SD card and other Flash images required for booting the system, in addition to the .xclbin device binary from the .xsa generated for Versal devices. The v++ --package step, or -p option, packages the final system at the end of the v++ compile, link, and package 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.

A 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). But 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.

In the Vitis unified IDE, the package process is automated and the tool creates the required files based on the build target, platform, and OS. However, in the command line flow, you must specify the Vitis packaging command (v++ --package) with the correct options for the job.

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).