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.
- For detailed event trace information, the
--xlopt=0option must be specified in compile. If you omit the--xlopt=0option, the default setting--xlopt=1applies. This limits debug capability and might cause functions to be in-lined. - Host code is required to invoke
graph.end()to ensure that the XRT flow completes properly.