Modules purchased not as part of a dev kit fail to boot

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
, ,
1

I have purchased and successfully used several of both the Echopilot carrier and the Stereolabs carrier with the Orin NX 16gb. I’ve since moved to a custom carrier board. I’ve successfully used the Orin modules removed from the dev kits in this carrier board.

Now, I’ve purchased a couple Orin modules NOT as part of a dev kit, so just the module. I’ve installed these modules in the carrier board (with the same, untouched nvme), and they fail to start up. I’ve set eeprom size to zero. On the serial console, I get the following, and then boot loops.

I> MB2 (version: 0.0.0.0-t234-54845784-9c429857)
I> t234-A01-0-Silicon (0x12347)
I> Boot-mode : Coldboot
I> Emulation:
I> Entry timestamp: 0x00213b47
I> Regular heap: [base:0x40040000, size:0x10000]
I> DMA heap: [base:0x469800000, size:0x800000]
I> Task: ARI update carveout TZDRAM (0x50001e80)
I> Task: Enable hot-plug capability (0x50026c6c)
I> Task: PSC mailbox init (0x50016a7c)
I> Task: Crypto init (0x500065a8)
I> Task: Enable GP-SE clock (0x50001fe4)
I> Task: DICE Identity init (0x50019e50)
I> DICE is not enabled.
I> Task: OEM SC7 context save init (0x50019550)
I> Task: I2C register (0x50001e44)
I> Task: Map CCPLEX_INTERWORLD_SHMEM carveout (0x50001e2c)
I> Task: Program CBB PCIE AMAP regions (0x50019b64)
I> Task: Boot device init (0x50001d74)
I> Boot_device: QSPI_FLASH instance: 0
I> Qspi clock source : pllc_out0
I> QSPI-0l initialized successfully
I> Task: Partition Manager Init (0x50001d70)
I> Found 57 partitions in QSPI_FLASH (instance 0)
I> Task: Load and authenticate registered FWs (0x5001ce48)
I> Task: Load AUXP FWs (0x5002680c)
I> Successfully register SPE FW load task with MB2 loader
I> Skipping SCE FW load
I> Successfully register RCE FW load task with MB2 loader
I> Successfully register DCE FW load task with MB2 loader
I> Unpowergating APE
I> Unpowergate done
I> Successfully register APE FW load task with MB2 loader
I> Skipping FSI FW load
I> Successfully register XUSB FW load task with MB2 loader
I> Partition name: B_spe-fw
I> Size of partition: 589824
I> Binary@ device:3/0 block-118016 (partition size: 0x90000), name: B_spe-fw
I> Partition name: B_rce-fw
I> Size of partition: 1048576
I> Binary@ device:3/0 block-119168 (partition size: 0x100000), name: B_rce-fw
I> spe: Authentication Finalize Done
I> Binary spe loaded successfully at 0x468c00000
I> Partition name: B_dce-fw
I> Size of partition: 5242880
I> Binary@ device:3/0 block-107776 (partition size: 0x500000), name: B_dce-fw
I> rce: Authentication Finalize Done
I> Binary rce loaded successfully at 0x468900000
I> dce : oem authentication of header done
I> dce : meta-blob integrity check is success.
I> dce : will be decompressed at 0x472000000
I> version 1 Bin 1 BCheckSum 0 content_size 0 Content ChkSum 1 reserved_00  0
I> Reserved10 0 BlockMaxSize 5 Reserved11 0
I> dce : decompressed to 9445504 bytes
I> dce: plain binary integrity check is success
I> Partition name: B_adsp-fw
I> Size of partition: 2097152
I> Binary@ device:3/0 block-121216 (partition size: 0x200000), name: B_adsp-fw
I> dce: Authentication Finalize Done
I> Binary dce loaded successfully at 0x472000000
I> Partition name: B_xusb-fw
I> Size of partition: 262144
I> Binary@ device:3/0 block-72448 (partition size: 0x40000), name: B_xusb-fw
I> ape: Authentication Finalize Done
I> Binary ape loaded successfully at 0x469400000
I> xusb: Authentication Finalize Done
I> Binary xusb loaded successfully at 0x468d00000
I> Task: Carveout setup (0x5001f55c)
I> Program remaining OEM carveouts
I> Task: Enable FSITHERM (0x50016950)
I> Task: Enable FSI VMON (0x500164d8)
I> Task: Validate FSI Therm readings (0x50016530)
I> Task: Restore XUSB sec (0x50001d44)
I> Task: Enable FSI SE clock (0x50016ed8)
I> Task: Initialize SBSA UART CAR (0x50001f48)
I> Task: Ratchet update (0x50027d08)
W> OPTIN fuse not set, skip ratchet update
I> Task: Initialize CPUBL Params (0x50017e0c)
I> CPUBL-params @ 0x46e000000
I> Task: Prepare eeprom data (0x50017bd8)
E> I2C: slave not found in slaves.
E> I2C: Could not write 0 bytes to slave: 0x00ae 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 0xae at 0x00000000 via instance 0.
E> eeprom: Failed to read I2C slave device
C> Task 0x0 failed (err: 0x1f1e050d)
E> Top caller module: I2C_DEV, error module: I2C, reason: 0x0d, aux_info: 0x05

Additionally, I am unable to flash L4T if using one of the new modules. The board is never recognized, even though I do see it correctly on lsusb.

I’m building and installing directly from the 35.4.1 downloads page.

3

Are you using Orin NX or AGX Orin module?
The boot failed problem is on your customer carrier board or 3rd party carrier board?

Just guess those new Orin NX module might have new eMMC/DRAM ( NVIDIA Jetson Orin NX 16GB PCN 211361 Addition of Manufacturing BOM Components: DRAM), I will suggest to try with JetPack 6.1 SW to get them work well.

5

Orin NX.

The boot fails on my carrier board and the 3rd party carrier board with either of two different recently purchased standalone modules.

The older, bought-as-part-of-a-devkit modules boot successfully with both the 3rd party and in-house carriers.

I’ll try 6.1 when I return to the office tomorrow.

6

6.1 works.

Still odd though, this fails:

  1. Flash ssd with a new Orin connected
  2. Replace Orin with an old Orin
  3. Old Orin doesn’t work

Then, if I do:

  1. Flash ssd with old Orin connected

Now both the old Orin and the new Orin work correctly, interchangeably

7

Hi,

Thus, you could boot in the rootfs and get into the login with the new Orin?

Thanks

8

yes and yes

9

Hi

could you share the result with below commands in your old/new orin nx modules

cat /etc/nv_boot_control.conf

Thanks

10

Results are as follows. This is with the same SSD, same carrier, swapped Orin modules.

Old module:

nvidia@orin7[~]$ cat /etc/nv_boot_control.conf
TNSPEC 3767-300-0000-L.2-1-1-p3509-a02-p3767-0000-
COMPATIBLE_SPEC 3767-000-0000--1--p3509-a02-p3767-0000-
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

New module:

nvidia@orin7[~]$ cat /etc/nv_boot_control.conf
TNSPEC 3767-500-0000--1-1-p3509-a02-p3767-0000-
COMPATIBLE_SPEC 3767-000-0000--1--p3509-a02-p3767-0000-
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
11

Hi,

Could you share your flashing logs and serial log about the step in

  1. Flash ssd with a new Orin connected
  2. Replace Orin with an old Orin
  3. Old Orin doesn’t work

Thanks