Option 1: Automated and Periodic AI Engine Status Output - 2023.2 English

In the working directory /run/media/mmcblk0p1, create the file xrt.ini, and put the following contents into it:

[Debug]
aie_status=true

You can also specify the interval at which the AI Engine status should be probed and analyzed:

[Debug]
aie_status=true
aie_status_interval_us=10000

Run the application:

./host.exe a.xclbin

After some time, messages such as the following will be printed:

[XRT] WARNING: Potential deadlock/hang found in AI Engines. Graph : gr
[XRT] WARNING: Potential stuck cores found in AI Engines. Graph : gr Tile : (25,0) Status 0x1001 : Enable,Stream_Stall_MS0
[XRT] WARNING: Potential stuck cores found in AI Engines. Graph : gr Tile : (24,0) Status 0x201 : Enable,Lock_Stall_E

Note: These messages indicate that the design might be stuck. However, it is your responsibility to determine if it is a true deadlock based on the design.

Wait for some time. Either kill the application run by hitting Ctrl+C or suspend it by hitting Ctrl+Z. You will then see that multiple files are generated in the working directory:

• xrt.run_summary

• aie_status_edge_XXX.json

• aieshim_status_edge_XXX.json

• summary.csv

Copy them to the local server for further analysis in Vitis Analyzer.