Orin nx stuck at recovery mode

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

Hi,
I am using Orin NX based custom carrier board, with L4T 36.4.

After flashing the boards, we are intermittently seeing some soms are not booting to normal mode and is stuck at recovery mode.

UART logs during bootup after flashing: flash_recoverymode.txt (12.0 KB)
Previous Flash logs from host pc: flash_recoverymode_host.txt (68.8 KB)

I am able to flash and boot to normal mode when i connect a different som and ssd with the same host pc and carrier board.

Can i consider this as a SOM failure? Please support.

Thanks
Ashik P.

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it seems like you’re experiencing intermittent boot issues with your custom carrier board using Jetson Orin NX and L4T 3.6.4. The issue is that some SOMs (System on Modules) are not booting to normal mode and are stuck in recovery mode.

To troubleshoot this issue, let’s break down the information you’ve provided:

  1. Intermittent boot issues: This suggests that the issue might not be related to the hardware or software configuration, but rather to a specific combination of factors that occur occasionally.
  2. UART logs during bootup: The logs you’ve provided might contain valuable information about the boot process. However, without access to the actual logs, it’s difficult to provide a detailed analysis.
  3. Flashing and booting with different SOM and SSD: The fact that you can flash and boot to normal mode with a different SOM and SSD using the same host PC and carrier board suggests that the issue might be related to the specific SOM or SSD being used.

Considering these points, it’s possible that the issue is related to the SOM or SSD, but it’s not conclusive evidence of a SOM failure. Here are a few potential explanations:

  • SOM or SSD compatibility issues: It’s possible that the SOM or SSD being used is not fully compatible with the custom carrier board or the L4T 3.6.4 software. This could be causing the intermittent boot issues.
  • Hardware or software configuration issues: There might be a configuration issue with the SOM, SSD, or the custom carrier board that’s causing the boot issues. This could be related to the UEFI settings, the boot order, or other configuration parameters.
  • Flashing or boot process issues: The flashing or boot process might be faulty, causing the SOM to get stuck in recovery mode. This could be related to the flashing tool, the boot loader, or the kernel.

To further troubleshoot the issue, you could try the following:

  • Verify the SOM and SSD compatibility: Ensure that the SOM and SSD being used are fully compatible with the custom carrier board and the L4T 3.6.4 software.
  • Check the UEFI settings and boot order: Verify that the UEFI settings and boot order are correct and configured properly.
  • Use a different flashing tool or method: Try using a different flashing tool or method to see if the issue persists.
  • Analyze the UART logs: If possible, provide the UART logs for further analysis, which might help identify the root cause of the issue.

In conclusion, while the issue might be related to the SOM or SSD, it’s not conclusive evidence of a SOM failure. Further troubleshooting and analysis are required to determine the root cause of the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hi Team,
Any update on this issue?

5

Hi,

Could you please install latest BSP version 36.5 JetPack Archive | NVIDIA Developer to cross check the issue?

Thanks