Flash.sh Stalls During Execution of tegrarcm_v2 --oem platformdetails storage

[kushiki.yusuke]

Could you advise me on how to improve the configuration for flash.sh?

Currently, I’m flashing a product that includes the Jetson Orin NX 16GB and a PCIe-attached 512GB NVMe.
While running flash.sh with the -u and -v options to enable Secure Boot, tegraracm_v2 within flash.sh stalls.

[   1.7200 ] Retrieving storage infomation
[   1.7235 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin

stalled_flash.sh.txt (161.7 KB)

[JerryChang]

hello kushiki.yusuke,

@kushiki.yusuke

While running flash.sh with the -u and -v options

did you fuse a target to enable Jetson security?
could you please try fuse read for confirmation.
for instance, $ sudo ./flash.sh --read-info -u <pkc> -v <sbk> <target_conf> <rootdev>

[kushiki.yusuke]

Hi @JerryChang

Thank you for your message.
I will look into the command you provided tomorrow, as I am currently out of the office today.
But, in my understanding, odmfuse.sh was successfully executed.

If possible, could you please clarify how the fuse is related to the stalling of tegrarcm_v2?

[kushiki.yusuke]

The flash.sh script we used in JP5.1.1 does not include the --read-info option.
Therefore, we utilized the latest JetPack and obtained the following output.

What can we infer from this?

==== Fuse Info (/home/pana/Desktop/JP610/Linux_for_Tegra/bootloader/fuse_t234.bin) ====
PublicKeyHash: e23cf5cd726787905074420ce475f442d51f0d199c09e6d09afa3ec97e635e44aa1930de231a0c9aba08e0e24032d986f25ae37d9db0f7178eb6b3505458a874
PkcPubkeyHash1: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PkcPubkeyHash2: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BootSecurityInfo: 0000020b
ArmJtagDisable: 00000000
SecurityMode: 00000001
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: 000000d3
Uid: c081fd0500000010e1e85d7004000000
OptEmcDisable: 00000000

[JerryChang]

hello kushiki.yusuke,

according to the logs, it might be the issue of stuck at NVMe communication.

[   1.7200 ] Retrieving storage infomation
[   1.7235 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin

BTW,
it seems like a customize board.
please double check it’s correct board configuration, nru50+, and it’s using correct file for image flashing.
for instance, are you able to flash a target (those without fuse) successfully?