Why does my AIE system application hang? - 2024.1 English

Vitis Tutorials: Vitis Platform Creation (XD101)

Document ID
XD101
Release Date
2024-06-19
Version
2024.1 English

If you test the platform with the PL+AIE system application and it hangs on the board with following error message, pressing Ctrl+C reports command stall, you are probably using the sd_card.img in package_aie_debug directory rather than package directory. The application in the package directory is used for debugging. It will stop after loading and wait for debugger to connect to it.

[   52.262013] [drm] Pid 715 opened device
[   52.265891] [drm] Pid 715 closed device
[   52.299093] [drm] Pid 715 opened device
[   52.302958] [drm] Pid 715 closed device
[   52.307012] [drm] Pid 715 opened device
Loading: 'binary_container_1.xclbin'
[   52.579320] [drm] zocl_xclbin_read_axlf fbc72c83-5ab0-43f2-97aa-60c7672e835a ret: 0
[   52.584870] [drm] bitstream fbc72c83-5ab0-43f2-97aa-60c7672e835a locked, ref=1
[   52.592572] [drm] No ERT scheduler on MPSoC, using KDS
[   52.604924] [drm] Interrupt is not enabled for at least one kernel. Fall back to polling mode  .
[   52.604934] [drm] 12 non-zero interrupt-id CUs out of 13 CUs
[   52.613562] [drm] CU ffffff02 is free-running.
[   52.619222] [drm] scheduler config ert(0)
[   52.623663] [drm]   cus(3)
[   52.627666] [drm]   slots(16)
[   52.630369] [drm]   num_cu_masks(1)
[   52.633330] [drm]   cu_shift(16)
[   52.636807] [drm]   cu_base(0xa4010000)
[   52.640030] [drm]   polling(1)
[   52.643894] [drm] bitstream fbc72c83-5ab0-43f2-97aa-60c7672e835a unlocked, ref=0
^C[   52.654496] [drm] bitstream fbc72c83-5ab0-43f2-97aa-60c7672e835a locked, ref=1
[   56.707230] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   57.241186] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   57.753177] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   58.265177] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   58.777175] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   60.313187] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   60.825177] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   61.337174] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   61.849185] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   62.361191] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   62.873190] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   63.385190] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   63.897188] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   64.409185] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   64.921183] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   65.433177] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   65.945174] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   66.457185] [drm] pid(715) waiting for outstanding 1 cmds to finish
[   66.969193] [drm:zocl_client_release [zocl]] *ERROR* Please investigate stale cmds
[   66.983017] [drm] addr 0xa4020000, status 0x4
[   66.983019] [drm] addr 0xa4010000, status 0x1
[   66.987375] [drm] bitstream fbc72c83-5ab0-43f2-97aa-60c7672e835a unlocked, ref=0
[   66.991728] [drm] Pid 715 closed device

Copyright © 2020–2023 Advanced Micro Devices, Inc

Terms and Conditions