Generating AI Engine Status - 2022.1 English

Versal ACAP AI Engine Programming Environment User Guide (UG1076)

Document ID
Release Date
2022.1 English

Periodic AI Engine Status Output Using XRT

You can enable the run-time deadlock detection and status output using the xrt.ini file. This is a one-time set up, which results in periodic output of status data, including deadlock detection. To turn on this feature, add the following to the xrt.ini file:
To specify the interval of probing and analysis the AI Engine status:
The AI Engine status is copied to the following files when the host program is running:
  • xrt.run_summary: Run summary that contains list of files information that can be used by Vitis Analyzer. 
  • aie_status_edge.json: Status of AI Engine and AI Engine memory.
  • aieshim_status_edge.json: AI Engine interface tiles status.
  • summary.csv: Always created. For other profiling capabilities, like guidance.
If a deadlock is detected, an warning message is reported, such as the following:
[XRT] WARNING: Potential deadlock/hang found in AI Engines. Graph : gr
[XRT] WARNING: Potential stuck cores found in AI Engines. Graph : gr Tile : (25,1) Status 0x81 : Enable,Lock_Stall_W

Besides the AI Engine status, if any error event occurred, it is recorded in the JSON file.

You are responsible for determining the severity of the error, and whether it is recoverable. Use the summary and JSON files for analyzing in Vitis Analyzer.

Manual AI Engine Status Output

You can output a single snapshot of the AI Engine status to the JSON file at any time after the device has been loaded. This is a static snapshot of the AI Engine running status, along with the events that happened before.

Use the xbutil command with option -f json to output status to the JSON file. For example:
xbutil examine -r aie -d 0 -f json -o aie_status_xbutil.json

Later, the JSON file can be imported into Vitis Analyzer following specific steps.