Debugging BCCPLEXWDT reset source

I am developing software on top of the AGX Orin dev kit. I encountered the system lock up and reset with the BCCPLEXWDT reset code as observed by looking at PMC log statements (sudo dmesg | grep PMC)

In case it’s relevant, I am using VPI/CUDA in my system and MIPI cameras via nvargus.

How can I better debug the BCCPLEXWDT issue? I am assuming it is some kind of CPU watchdog. What other information can be gathered to narrow down on what is causing this?

Do you use latest Jetpack 5.1.1? If you use previous release, we would suggest upgrade to latest release and give it a try.

And for information, please share the UART log for reference. You can get the log by referring to:
Jetson/General debug -

Hi DaneLLL,

Thanks for the reply. I am not using Jetpack 5.1.1 yet. I can update when I find the opportunity. In the meantime, is there reason to believe this is something that will be resolved in Jetpack 5.1.1? Is there something in the changelog?


It is uncertain if this is not seen on Jetpack 5.1.1, but it would be great if you can use latest release. Certain bugs reported in previous releases are fixed in later release.

If you have a test code which can be run to reproduce the issue, please share to us and we can give it a try.

I was able to reproduce the issue on Jetpack 5.1.1. I do not have a reproduction case yet as it happens “randomly” while the system is under load.

Is there any information you have can direct me to on the BCCPLEXWDT reset reason and any information to collect to diagnose the issue?

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks

For further check, we would need a method to reproduce it on developer kit. Would need your help to try it on developer kit and see if it is also present.

I still need support. As I mentioned in the first post, I am able to reproduce this on the Jetson AGX Orin Developer Kit. I do not know how to reproduce it because it seems to happen at random.

Does this reset reason essentially mean that the Linux kernel was completely hung? Or does it have some other kind of meaning?