I have a Jetson Orin NX SOM that I tried to flash, It failed to flash and now powers up in Recovery mode without needing to push any button. Is it normal behavior for the Orin NX to power up in Recovery mode before it’s flashed? Thank you for any insight.
*** Please note that this reply is generated by LLM automatically ***
The behavior you’re experiencing with your Jetson Orin NX SOM powering up in Recovery mode without needing to push any button after a failed flash attempt is not entirely abnormal, but it does indicate an issue that needs to be addressed.
Normally, a Jetson module like the Orin NX should not automatically enter Recovery mode unless it’s forced to do so by pressing the Recovery button (usually the Force Recovery button) during power-on. Recovery mode is a state that allows for flashing the device with a new image, typically when the existing software on the device is corrupted or not functioning correctly.
However, if your Jetson Orin NX is entering Recovery mode without the button being pressed, it could be due to a few reasons:
Failed Flash Attempt: The most likely reason is that the previous flash attempt failed, leaving the device in an inconsistent state. This can cause the device to automatically enter Recovery mode on the next boot, as it cannot boot into its normal operating mode.
Bootloader Configuration: There might be an issue with the bootloader configuration. The bootloader is responsible for loading the operating system, and if it’s not properly configured, it might default to Recovery mode.
Hardware Issue: Although less likely, there could be a hardware issue with the SOM or its connections. This might prevent the device from booting normally and cause it to enter Recovery mode.
To resolve the issue, you can try the following steps:
Reflash the Device: Attempt to flash the device again, ensuring that you’re using the correct flash configuration file and that the flashing process completes successfully.
Check Bootloader Configuration: Verify that the bootloader is correctly configured. You might need to consult the documentation for your specific Jetson Orin NX model and the flashing tool you’re using.
Inspect Hardware: Double-check the hardware connections and the SOM itself for any signs of damage or malfunction.
Reset to Defaults: If possible, try resetting the device to its factory defaults. This can sometimes resolve issues caused by incorrect configurations.
If none of these steps resolve the issue, it might be helpful to consult the official NVIDIA documentation for the Jetson Orin NX or seek support from NVIDIA’s forums or customer support, as there could be a more specific issue related to your device or its configuration.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Thank you Carolyuu and DavidDDD for your reponses. Yes, The 3 steps outlined by David is what I used to determine whether it’s in Recovery mode. It shows “Bus ID 0955:7323 Nvidia Corp APX”. I have another SOM that does not exhibit this issue. when I press the buttons for that one to go into Recovery mode, it gives the same Bus ID.
I tried using Nvidia SDK Manager to flash and it failed in the same way and at the same point as our own BSP did. It failed at “sending bct_mem”. I wonder if it has to do with the SDRAM PCN. I’m currently using Jetpack 5.1.5 or higher. I will try to flash using older Jetpack to see.
I used Nvidia SDK Manager and tried flashing with Jetpack 6.2.1, 5.1.5, and 5.1.3. They all failed the same way. Bummer. So perhaps it’s something else instead of SDRAM PCN issue.
So after trying a few things including various older/newer Jetpacks, replacing USB cables, disable USB autosuspend, disable firewall, none of which resolved the issue. Then I put a fan blowing directly on the SOM, in addition to the little fan on top of the SOM that was already there, and that resolved the issue. My issue was the flashing was failing at around the 69% completion mark, when it was reporting bct_mem activity. This failure then cause the SOM to power up in Recovery mode without needing to push any button. My guess is at this point, the bootloader could be trying to copy data to memory, and this consumes more power and run a little hotter. And without the additional fan, the SOM flashing failed.