Unable to get into Force Recovery mode (Orin NX 8GB)

I am unable to get Orin NX 8GB into force recovery mode.

It does not show up in the SDK manager when I pull the force recovery pin Low.

In normal mode, It is showing this error,

[0000.888] W> DEVICE_PROD: module = 13, instance = 4 not found in device prod.
[0000.896] E> I2C: Timeout while polling for bus clear. Last value 0x00000000.
[0000.903] E> I2C: Failed to clear bus for instance 4.
[0000.908] W> DEVICE_PROD: module = 13, instance = 4 not found in device prod.
[0000.916] E> I2C: Failed to clear bus for instance 4.
[0000.921] E> I2C_DEV: Failed to initialize instance 4.
[0000.926] E> pmic: Can't get handle to i2c device @4
[0000.932] E> PMIC_CONFIG: Failed to initialize Rail: SOC rail config.
[0000.938] C> Task 0x2b failed (err: 0x57571c1c)
[0000.943] E> Top caller module: PMIC_CONFIG, error module: PMIC_CONFIG, reason: 0x1c, aux_info: 0x1c
[0000.952] C> Boot Info Table status dump :
011111110011100011111111111111111111111111100000000000000000000000000000000000011111

Full log:
boot-log.txt (9.6 KB)

I tried this on Devkit, but it is the same output as described above.

What could be the issue here?

Any assistance would be greatly appreciated.

Thank you!

Info:

  • SoM: Orin NX 8GB
  • JetPack 6.0 rev2
  • Tested on Devkit

What is you method to put the board into recovery mode? And is it on devkit?

Yes, it is on devkit. I connected Pin 10 (FC_REC) and 9 (GND) on the J14 button header.

Is your host PC able to detect any other Jetson before?

This question is trying to make sure

  1. This host is really able to detect usb device

  2. The usb cable you are using is really fine for usb detection. Some cheap usb cable only has function to charge. No data line.

Yes, I can flash from my host PC. This SoM (Orin NX) has worked before.

I can still successfully flash the Orin Nano Module using the same host, cable, and carrier board(devkit).

Then it is possible that the carrier board or SOM has hardware problem.

Cannot enter recovery mode is just a pure hardware event. No software is involved.

Thank you for the reply.

Are there any alternative ways to enter recovery mode?

Is there any diagnostics to confirm it is the hardware issue?

No, there is no other way to enter recovery mode in current status.

Also no method to do diagnostics.