With the HLS kernel outputs ready and the new platform built, you generate the programmable device image (PDI) and package for an SD card. The PDI contains executables, bitstreams, and device configuration data. The packaged SD card directory includes all files to boot Linux, the generated applications, and the .xclbin binary.
Run the command for this step as follows (default TARGET=hw_emu, N_FIR_FILTERS=1, N_FIR_TAPS=15, EN_TRACE=0):
make package
or
cd ../build/fir_hls_$(N_FIR_FILTERS)firs_$(N_FIR_TAPS)taps/hw_emu
v++ -p \
-t hw_emu \
--save-temps \
--temp_dir build/fir_$(N_FIR_TAPS)_taps/x$(N_FIR_FILTERS)_firs/hw_emu/_x \
-f xilinx_vck190_base_202520_1 \
--package.rootfs $(COMMON_IMAGE_VERSAL)/rootfs.ext4 \
--package.kernel_image $(COMMON_IMAGE_VERSAL)/Image \
--package.boot_mode=sd \
--package.out_dir build/fir_$(N_FIR_TAPS)_taps/x$(N_FIR_FILTERS)_firs/hw_emu/package \
--package.image_format=ext4 \
--package.sd_file build/fir_$(N_FIR_TAPS)_taps/x$(N_FIR_FILTERS)_firs/hw_emu/fir_hls_xrt.elf \
build/fir_$(N_FIR_TAPS)_taps/x$(N_FIR_FILTERS)_firs/hw_emu/vck190_hls_fir.hw_emu.xsa \
--package.sd_file design//exec_scripts/run_script.sh
If EN_TRACE is active, also set the following v++ flags:
--package.sd_file design/profiling_configs/xrt.ini
This includes the XRT .ini file with tracing parameters.
Switch |
Description |
|---|---|
–package | -p |
Packages the final product after compiling and linking in the Vitis build process. |
–target | -t [hw|hw_emu] |
Specifies the build target. |
–save-temps | -s |
Directs the V++ command to save intermediate files and directories created during the compilation and link process. Use the |
–temp_dir |
Sete the location for temporary files created during the build process. The Vitis compiler deletes them unless you also use |
–platform | -f |
Specifies the name of a supported acceleration platform from the |
–package.sd_dir <arg> |
Where |
–package.rootfs <arg> |
Where <arg>Specifies the absolute or relative path to a processed Linux root file system file. The platform |
–package.kernel_image <arg> |
Where <arg>Specifies the absolute or relative path to a Linux kernel image file. This overrides the existing image available in the platform. The platform image file is available for download from the Adaptive Computing Support downloads page. Refer to the Vitis Software Platform Installation for more information. |
–package.boot_mode <arg> |
Where <arg>Specifies <ospi|qspi|sd> Boot mode used for running the application in emulation or on hardware. |
–package.image_format |
Where <arg>Specifies <ext4|fat32> output image file format. |
–package.sd_file |
Where <arg>Specifies an executable and linkable format (ELF) or other data file to package into the |
Detailed Description of All Vitis Compiler Switches Details of Packaging the System
Inputs Sources |
Description |
|---|---|
$(COMMON_IMAGE_VERSAL)/rootfs.ext4 |
The Root Filesystem file for Petalinux. |
$(PLATFORM_REPO_PATHS)/Image |
The pre-built Petalinux Image the processor boots from. |
$(BUILD_TARGET_DIR)/fir_hls_xrt.elf |
The PS Host Application executables created in the |
$(BUILD_TARGET_DIR)/vck190_hls_fir.hw_emu.xsa |
The XSA file created in the |
The output of the V++ Package step is the package directory that contains the contents to run hardware emulation.
Output Objects |
Description |
|---|---|
$(BUILD_TARGET_DIR)/package |
The hardware emulation package that contains the boot file, hardware emulation launch script, the PLM and PMC boot files, the PMC and QEMU command argument specification files, and the AMD Vivado™ tools simulation folder. |