Hi all, we are experiencing strange behavior on some Orin AGX devices which causes devices not able to boot.
for some reason the eMMC storage is moved to the last position in boot order. It happens “randomly” during device operation. When we change the boot order back, the device boots normally but after some time it breaks again.
In UEFI firmware there is set that new devices should be moved to top.
We don’t know what is the trigger of such behavior. Do you have any idea, why this could happen and what we can do about it please?
L4T version r35.1.0 and r35.4.1
UEFI firmware version: 202210.3 (also happens with older versions)
Thank you for any suggestions.
Are you using the devkit or custom board for AGX Orin?
Could you also verify with the latest JP5.1.4(r35.6.0)?
Could you help to clarify the cause of this behavior?
Do you hit any reboot issue occasionally so that you found the boot order changed?
Or you can share the full serial console log when the issue occurs.
Hello, thanks for the answer. It is on custom carrier board but with original UEFI firmware. There are regular reboots. Unfortunately this occurred only in customer installation, so I don’t have access to the device at the time when the problem occurs and cannot find a way reproduce it. I can attach just logs from startup on already “broken” device. Network boot errors are expected (usually there is eMMC on first place).
Could you please suggest any leads what could cause such behavior? Why it is moved to the bottom of boot order (even if new devices are always added to top). orin_log.txt (35.6 KB)
Do you have any custom design may lead to eMMC loaded failed?
I suppose you are using internal eMMC from the module.
We can’t determine the cause of your behavior since it can’t be reproduced on the devkit and we don’t have your setup to perform further debug. We would suggest you enabling debug UEFI logs to check if there’re more useful info about this situation.
