I am using a Jetson AGX Orin custom carrier board with L4T 35.3.1.
The system is booting normally.
And the issue was the MB1 booting but the MB2 not booting sometimes after the system shutdown.
Thanks for your help.
MB2-boot-failed-log.txt (54.0 KB)
Hi michtw,
I can’t find the error or fail messages in your log.
It seems booting from slot 0 first, then switching to slot 1.
Have you run any command to switch boot slot?
Could you share the steps to reproduce the issue?
Just press the power button to turn on the system. That’s all.
I don’t run any commands during the booting.
It’s the AGX Orin boot flow.
The following diagram shows the flow of control in the boot software.
May I know how about the failed rate?
Could you verify with the latest R35.5.0?
Or could you reproduce the issue on the devkit? We want to know if the issue is specific to your custom board.
The failed rate is high. Maybe around 5/200.
Our QA testing and software development are all base on the l4T 35.3.1. So, it’s not a good idea to switch to 35.5.
We make a custom jig for power cycle test on our custom carrier board and the jig can’t used on the devkit.
Is the MB2 binary stored in the AGX Orin SOM？
Is there any method to have more MB1 and MB2 debug messages?
Is there any possible that the MB2 is not running?
Yes, QSPI in the module.
The debug log has been enabled by default.
We would like to know if devkit would hit the similar issue so that we can perform further debug.
Or we may suspect the issue is specific to the custom design on your board.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
