Since updating to the 2.5 image we’ve been seeing quasi-regular ZCU111 board hangs, possibly even without an overlay loaded. We’ve also been starting to test new cores much more heavily, so we did change the cpuidle setting so we could use the System ILA in Vivado.
I had been chalking the need to power cycle the board ~2-3 / week up to us causing deadlocks or not properly connecting/disconnecting from the ILA, but this weekend it hung after a fresh boot without us having loaded any of our software for testing or starting anything other that the hw_server on the host PC.
How can I even start to debug this? When it happens after testing for a while and walking away I can tell from the JTAG connection in vivado that some things are still alive, but the Jupyter server isn’t responsive (This is NOT directly a cpuidle issue as I set that and can use python and the ILA concurrently).
Is there a way to trigger a reboot of the board from Vivado or some Xilinx tool on the windows host PC? This would move this from a major headache to a minor inconvenience. The boot from configuration memory in the hardware manager doesn’t seem to “just work”, I’d guess because it isn’t configured properly to be aware of the uboot loader or some such.