Hi Nvidia:
We are using AGX Orin 64GB on custom board, with Jetpack 6.0 GA.
After triggering a kernel panic, watch dog will reboot the system. But, after the system boot up again, the type-c camera, which is DMK 33UX546, became unavailable.
This issue is pretty strange since it only happened on some of the boards. We can’t reproduce the issue on every system nor devkit.
For now, we have a workaround that re-plug the camera again, and the device is back again. So we are thinking that maybe restart the power of USB type-c will also do the trick. But several posts we found were for Orin NX or Nano, not for AGX Orin. Also, echo disabled into state file in regulator folder isn’t working either since there is no such file to echo in.
Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device: Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs: Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system: Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!
Hi DaneLLL:
Thanks for the reply.
We did followed the compliance test guide to test the type-c port. However, following the guide, we are able to do the test for USB 2.0, not for USB 3.0. We also tried on devkit, yet we can’t send the test pattern for USB 3.0.
I think that’s another issue. What’s more, if the signal quality is not good enough, maybe the camera can’t start at the first time?
First, you need to make sure the signal won’t be blocked by any switch/mux on the USB trace, and also may need to check with vendor for test method if USB hub is used.