We are encountering an issue with our AGX Orin-based custom carrier boards in a field deployment. Several of the boards are unexpectedly entering recovery boot mode, and it is difficult to switch them back to normal boot since the boards are located in the field and not easily accessible for manual intervention. We are unsure of the cause behind this unexpected behaviour and would like to understand what might be triggering the recovery boot mode.
Additionally, we need to know if there are any steps to prevent this from happening again. I have attached the log file from one of the affected boards for reference. recovery_boot_issue.txt (80.7 KB)
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!
It is too late to share the log. The recovery boot image log is same to everyone. It is pointless to give out this log and ask to analyze. That is, everyone’s recovery image is same. The log would be same.
What you need to do is check what was the log “before” recovery boot happened. There is definitely a continuous boot failure so that the system went into recovery boot image.
If you want to recover from recovery boot, please check
If you want to know why system went into recovery boot image, you could refer to
I guess there were kernel panic on your board before recovery boot image happened.