Cannot flash Orin Nano Devkit for first time: Could not read eeprom

Hi all,

I’ve got a brand new Jetson Orin Nano devkit board and am having trouble flashing it for the first time or getting anything to boot. I’ve tried a lot of methods/versions/etc. to get this working, so I’ll just post the one I made the most progress with:

I installed the Jetpack SDK manager (2.0.0) on Ubuntu 20.04 and downloaded the 5.2.1 SDK/Linux_for_Tegra stuff. I set the board in recovery mode and ran:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk1p1 \
  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal

I seem to hit an EEPROM error (from debug UART):

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 0x4000021
I> Populate eeprom info
I> Populate eeprom info for module cvm
E> I2C: Timeout while polling for transfer complete. Last value 0x00000002.
E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start true.
E> I2C_DEV: Failed to send register address 0x00000000.
E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 at 0x00000000 via instance 0.
E> eeprom: Failed to read I2C slave device
E> NV3P_SERVER: Failed to get eeprom handle for cvm from eeprom manager.
E> NV3P_SERVER: Could not read eeprom for module cvm.
C> XUSBF: comp_code went out of sequence. Expected 1 instead of 223.
C> XUSBF: comp_code went out of sequence. Expected 1 instead of 223.

Full cmdline and debug UART:
flash_cmdline_output.txt (180.2 KB)
flash_debug_uart.txt (1.6 KB)

The script seems to chug along after this, but the debug UART goes pretty silent. When booting the board afterward, there is no output on debug UART or via display port.

So, I’m wondering where to go from here. Full command output and debug UART attached.

Thanks!

Hi,

Are you sure it’s a DevKit instead some custom carrier boards?
Have you tried 6.0 DP in addition to 5.1.2?
I feel like it’s a hardware failure, and it’s weird it happens on a brand new module.

Yeah, pretty sure it’s legit. And, yes, 6.0 gives the same result.

Looks like it’s a hardware failure.
Please RMA it.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.