You must use the Vitis IDE to view and analyze trace data. After XRT or XSDB captures the trace data, you can open the Event Trace view in the Vitis IDE.
Figure 1. Event Trace
Open the run summary file to view event trace data. An example of the XSDB flow is as follows:
vitis -a ./aie_trace_profile.run_summary
An example of the XRT flow is as follows:
vitis -a ./xrt.run_summary
Limitations
- The event trace shows overruns caused by limited resources. Refer to Using Multiple Event Trace Streams to configure the number of trace streams to minimize the overruns issue.
- Specify
--xlopt=0for detailed event trace information. On AI Engine and AI Engine-ML the default isxlopt=1, which can in-line functions and limit debug capability; AI Engine-ML v2 already defaults toxlopt=0. - Host code is required to invoke
graph.end()to ensure that the XRT flow completes properly.