We are using a custom carrier board derived from the Jetson Orin Nx design.
Flashing with the regular flash.sh
NVMe profile stops at “Retrieving storage information”, while the init‑rd flash tool succeeds.
sudo ./flash.sh jetson-orin-nano-devkit-nvme external
…
[ 4.1151 ] BL: version 1.4.0.2-t234-54845784-08a4de08 last_boot_error: 0
[ 4.1154 ] Sending bct_mem
[ 4.1155 ] Sending blob
[ 5.5200 ] completed
[ 5.5200 ] Retrieving storage infomation
[ 5.5210 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin
Flash halts here
However
./flash.sh --read-info jetson-orin-nano-devkit-nvme nvme0n1p1
Board ID(3767) version(300) sku(0001) revision(M.3)
Chip SKU(00:00:00:D4) ramcode(00:00:00:02) fuselevel(fuselevel_production) board_FAB(300)
ECID is 0x80012344705DD44A280000000C010100
==== Fuse Info (/home/glenwang/codebase/PE1100N_r3630/Linux_for_Tegra/bootloader/fuse_t234.bin) ====
PublicKeyHash: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PkcPubkeyHash1: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PkcPubkeyHash2: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BootSecurityInfo: 00000000
ArmJtagDisable: 00000000
SecurityMode: 00000000
SwReserved: 00000000
DebugAuthentication: 00000000
OdmInfo: 00000000
OdmId: 0000000000000000
OdmLock: 00000000
ReservedOdm0: 00000000
ReservedOdm1: 00000000
ReservedOdm2: 00000000
ReservedOdm3: 00000000
ReservedOdm4: 00000000
ReservedOdm5: 00000000
ReservedOdm6: 00000000
ReservedOdm7: 00000000
Sku: 000000d4
Uid: 0001010c000000284ad45d7004000000
OptEmcDisable: 0000000c
==== EEPROM content (/home/glenwang/codebase/PE1100N_r3630/Linux_for_Tegra/bootloader/cvm.bin) ====
00000000: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00 …
00000010: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30 …699-13767-00
00000020: 30 31 2d 33 30 30 20 4d 2e 33 00 00 00 00 00 00 01-300 M.3…
00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
00000040: b0 48 00 00 20 cd d8 2d b0 48 31 34 32 30 39 32 .H.. ..-.H142092
00000050: 33 30 34 36 30 39 38 00 00 00 00 00 00 00 00 00 3046098…
00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
00000080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
00000090: 00 00 00 00 00 00 4e 56 43 42 00 ff 4d 31 00 00 …NVCB..M1..
000000a0: 00 00 00 00 00 00 00 00 00 00 00 00 20 cd d8 2d … ..-
000000b0: b0 48 01 00 00 00 00 00 00 00 00 00 00 00 00 00 .H…
000000c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
000000d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
000000e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
000000f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0 …
Because of requirements we must use the classic flash.sh
method.
Could you advise which XML/parameter or device‑tree change is needed so that flash.sh … external
can detect our NVMe and proceed?
Many thanks!