Running the application hardware build allows you to see your application running on an accelerator card, such as the Alveo™ Data Center accelerator card, or an embedded processor platform targeting a Versal® ACAP or Zynq® devices. The performance data and results captured here are the actual performance of your accelerated application. Yet the profiling data from this run might still reveal opportunities to optimize your design.
- Edit the xrt.ini file as
described in xrt.ini File.
This is optional, but recommended when running on hardware for evaluation purposes. You can configure XRT with the xrt.ini file to capture debugging and profile data as the application is running. To capture event trace data when running the hardware, refer to Enabling Profiling in Your Application. To debug the running hardware, refer to Debugging During Hardware Execution.Tip: Ensure to use the
v++ -goption when compiling your kernel code for debugging.
- Unset the
XCL_EMULATION_MODEenvironment variable.Important: The hardware build will not run if the
XCL_EMULATION_MODEenvironment variable is set to an emulation target.
- For embedded platforms, boot the SD card. Tip: This step is only required for platforms using Xilinx embedded devices such as Versal ACAP or Zynq UltraScale+ MPSoC.
For an embedded processor platform, copy the contents of the ./sd_card folder produced by the
v++ --packagecommand to an SD card as the boot device for your system. Boot your system from the SD card.
- Run your application.
The specific command line to run the application will depend on your host code. A common implementation used in Xilinx tutorials and examples is as follows:
When running the design you can specify a number of trace options as described in Enabling Profiling in Your Application to capture design data during runtime. Any reports generated during the run are collected into the xrt.run_summary file. This collection of reports can be viewed by opening the run_summary in Vitis analyzer, and includes a Summary report, System and Platform Diagrams to illustrate the hardware design, Run Guidance offering any suggestions for improving the performance of the system, and a Profile Summary and Timeline Trace when enabled in the xrt.ini file during runtime. Refer to Using the Vitis Analyzer for additional information.