Hi Nvidia:
We are using AGX Orin 64GB on a custom board.
We encounter a strange issue. After a lots of reboot, the system will not able to boot, and the system will hang at:
We were running an auto-reboot testing. To do so, we use a service in Linux to poweroff after the Linux is boot up for 2 min. Another device, will then cut down the power supply and resupply the power. As a result, the AGX Orin will Boot up → Power off → Cut down power → Re-supply power → Boot up.
However, after around 500 times cycles, the system will not able to boot again. The serial log is attached above.
We captured some logs, but they are stored in eMMC. Is there a way to recover this situation without killing the data in eMMC?
We tried ./flash.sh -r -k A_cpu-bootloader jetson-agx-orin-devkit internal and ./flash.sh -r -k B_cpu-bootloader jetson-agx-orin-devkit internal , since the log looks like an UEFI issue. But it doesn’t work.
Hi Kevin:
Sorry for the misleading.
When the issue happened, we were using UEFI binary from Jetpack 6.0 BSP. That’s what I mean “Never touch them”.
And, as the post said, we tried to re-flash the A_cpu_bootloader and B_cpu-bootloader, trying to recover the situation and get the log in APP partition. That leads to the logs you saw. The only change in our built UEFI binary is to change the logo.
But we still can’t get the data in APP partition.
The log we got is attached. It was created by journalctl -f | tee logs every time before we poweroff the orin.
We expect some unaware apt upgrades or package installed, just like the issue happend in here.