XRT Flow - 2022.1 English

Versal ACAP AI Engine Programming Environment User Guide (UG1076)

Document ID
UG1076
ft:locale
English (United States)
Release Date
2022-05-25
Version
2022.1 English

The XRT flow is as follows:

  1. Burn the generated sd_card.img to the physical SD card.
  2. Create the xrt.ini file in the sd_card folder as described in this section to enable xrt flow.

    An example xrt.ini file is shown in the following.

    [Debug]
    aie_trace=true
    aie_trace_buffer_size=100M
    aie_trace_metrics = functions_all_stalls
    
    aie_trace_periodic_offload = true / false
    aie_trace_buffer_offload_interval_ms = 10
    aie_trace_file_dump_interval_s = 3

    The aie_trace_periodic_offload option to enable offload trace data at regular intervals while the application is running. The default option is set to true.

    The aie_trace_buffer_offload_interval_ms option is used to specify every number of milliseconds AI Engine event when the trace data is read into trace buffers. This option is effective only when aie_trace_periodic_offload=true.

    aie_trace_file_dump_interval_s option to specify every number of seconds all the new received trace data is appended to event trace files. This option is effective only when aie_trace_periodic_offload=true.
    Note: The aie_trace_periodic_offload feature is supported with XRT flow and PLIO event trace port only. No circular buffer is supported. Trace data collection stops when buffer is full.
  3. Run the design on hardware to trace hardware events.
  4. Copy the captured trace data from the sd_card folder to your design at same level as the design Work directory. The trace data is generated in the same location as the host application on the SD card. They are xrt.run_summary, aie_event_runtime_config.json, and aie_trace_N.txt.
  5. Use the Vitis Analyzer to import and analyze data with this command.
    vitis_analyzer xrt.run_summary