Is my Orin NX 16GB broken?

Hello experts,

I try to switch my Orin NX 16GB from 6.0 DP to 6.0 (rev 1), but that fails quickly using the sdkmanager. I have then tried to only program the qspi nor flash, but that fails also immediately. The logs are attached. Is my Orin NX module broken ?
host.log (20 KB)
serial.log (6.4 KB)

You can just test any previous “working” jetpack version on your jetson again. If any of them can flash your board, then your module is not broken.

If none of them can do it, then need further check.

Hello Wayne,

sdkmanager (that has been updated) does not propose 6.0 DP anymore, so I retried to flash with jetpack-5.1.2, that used to work too. Now it fails with

12:40:53 INFO: *** Retrying to install. attempt number: 2
12:40:53 SUMMARY: File System and OS - target_image: Install completed successfully.
12:41:04 INFO: Device info before flash: Jetson Orin NX 16GB | 002/023 | 2-1.1 | 2.00 | Recovery | 0955:7323
12:41:04 DEBUG: running command < true >
12:41:04 INFO: command finished successfully
12:41:04 DEBUG: running command < /tmp/device_mode_host_setup.cam5.sh >
12:41:04 INFO: command finished successfully
12:41:04 DEBUG: running command < true >
12:41:04 INFO: command finished successfully
12:41:04 DEBUG: Flash Jetson Linux - flash: using adapter to install NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS to /home/cam5/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS
12:41:04 INFO: Flash Jetson Linux - flash: *** Checking target board connection ...
12:41:04 INFO: Flash Jetson Linux - flash: *** Reading ECID ...
12:41:05 INFO: Flash Jetson Linux - flash:
12:41:05 INFO: Flash Jetson Linux - flash: [ 0.5019 ] Sending mb2_applet...
12:41:05 INFO: Flash Jetson Linux - flash: [ 0.7699 ] M
12:41:06 INFO: Flash Jetson Linux - flash: [ 1.0159 ] Retrieving board information
12:41:06 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 1s ]
12:41:06 ERROR: Flash Jetson Linux - flash: command terminated with error
12:41:06 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

in the sdkmanager TERMINAL window, and

I> Applet (version: 0.0.0.0-t234-54845784-8d394889)
I> t234-A01-0-Silicon (0x12347)
I> Emulation:
I> Entry timestamp: 0xffffffff
I> Task: Pinmux init (0x4000062d)
I> Task: Boot device init (0x40001321)
I> Applet do storage init
I> Boot_device: QSPI_FLASH instance: 0
I> Qspi clock source : clk_m
I> QSPI-0l initialized successfully
E> Error in command_complete 18000 int_status
E> OCR failed, error = 39390706
E> Failed to open sdmmc-3, err = 39390706
W> Ignoring init failure for device 0-3
E> Error in command_complete 18000 int_status
E> OCR failed, error = 39390706
E> Failed to open sdmmc-3, err = 39390706
W> Ignoring init failure for device 1-3
E> Unknown device 7
E> Unknown device 8
I> Task: Partition Manager Init (0x40002d61)
I> Found 60 partitions in QSPI_FLASH (instance 0)
I> Task: I2C register (0x400006a5)
I> Task: Register exit handlers (0x400005f5)
I> Task: Enter 3p server (0x40001925)
I> USB configuration success
I> Populate chip info
I> RAM_CODE 0x4000001
I> Populate eeprom info
I> Populate eeprom info for module cvm
E> I2C: Timeout while polling for bus clear. Last value 0x00000000.
E> I2C: Failed to clear bus for instance 0.
E> I2C: Failed to clear bus for instance 0.
E> I2C_DEV: Failed to initialize instance 0.
E> eeprom: Can't get handle to eeprom device @160
E> NV3P_SERVER: Failed to get eeprom handle for cvm from eeprom manager.
E> NV3P_SERVER: Could not read eeprom for module cvm.

in the serial terminal

So : hardware or software problem ?

1 Like

Are you using a NV devkit or custom board?

a custom board (of course, like everyone, based on the devkit :) )

Do you have other modules or carrier board that can cross check this situation?

I have replaced the module by a brand new one and flashing has succeeded now.

If I understand correctly, the hw problem with the other module is the inability to read the ‘cvm’ eeprom at 0xa0 on the module.

As a side note, there is an error in the error path : after the failure of the call to tegrarcm_v2, tegradevflash_v2 is called with the same options, but tegradevflash_v2 does not implement the ‘–chip’ option.

Old module could be broken. Please RMA it.