Found the solution to odmfuseread.sh failure

[david_charlap]

Hi, @JerryChang

Over on the OE4T discussion forum, someone there solved my problem with odmfuseread.sh. You may want to note this for future support questions.

Continuing the discussion from Problem with fuse burning:

@david_charlap

But the NVIDIA odmfuseread.sh script fails

The module’s console shows no output whatsoever. The script generates the following output:

$ sudo ./odmfuseread.sh -i 0x23 -k .../rsakey_priv.pem jetson-orin-nano-devkit-nvme
Existing emcfuse(.../Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
Existing emcfuse(.../Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
copying minratchet_config(.../Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-ratchet-p3767-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet ".../Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins "mb2_applet applet_t234.bin" --cmd "readfuses fuse_t234.bin fuse_t234.xml; dump eeprom cvm cvm.bin; dump custinfo custinfo_out.bin; reboot recovery" --key ".../rsakey_priv.pem" --minratchet_config tegra234-mb1-bct-ratchet-p3767-0000.dts 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 
[   0.0512 ] Reading fuses
[   0.0545 ] tegrasign_v3.py --key .../Linux_for_Tegra/tmp/keys/rsa3k/rsakey_priv.pem --getmode mode.txt
[   0.0548 ] Assuming zero filled SBK key : not reading .../rsakey_priv.pem
[   0.0528 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[   0.1197 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[   0.1459 ] Pre-processing config: tegra234-mb1-bct-ratchet-p3767-0000.dts
[   0.1647 ] Parsing partition layout
[   0.1653 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.1671 ] Kernel DTB used: None
[   0.1672 ] WARNING: dce base dtb is not provided

[   0.1675 ] Parsing partition layout
[   0.1680 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.1690 ] Creating list of images to be signed
[   0.1696 ] Generating ratchet blob
[   0.1698 ] Generating coldboot mb1-bct
[   0.1704 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb --minratchet tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb --ratchet_blob ratchet_blob.bin
[   0.1711 ] MB1-BCT version: 0.13

It turns out that the cause of the problem is because the odmfuseread.sh script can’t handle relative paths. When I ran the script using the full absolute path to my key files (e.g., /home/dcharlap/builds/orinnano/keys/pkc_key_priv.pem) instead of the relative path I had been using (e.g., ../keys/pkc_key_priv.pem), it worked and showed me the fuse values:

$ sudo ./odmfuseread.sh -i 0x23 -k /full/path/to/pkc_key_priv.pem -S /full/path/to/sbk.key jetson-orin-nano-devkit-nvme 
Existing emcfuse(.../Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
Existing emcfuse(.../Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
copying minratchet_config(.../Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-ratchet-p3767-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet ".../Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins "mb2_applet applet_t234.bin" --cmd "readfuses fuse_t234.bin fuse_t234.xml; dump eeprom cvm cvm.bin; dump custinfo custinfo_out.bin; reboot recovery" --encrypt_key "/full/path/to/sbk.key" --key "/full/path/to/pkc_key_priv.pem" --minratchet_config tegra234-mb1-bct-ratchet-p3767-0000.dts 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
...
[  18.1284 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
[  18.1289 ] MB2 Applet version 01.00.0000
Fuse reading is done. The fuse values have been saved in: .../Linux_for_Tegra/bootloader/fuse_info.txt
PublicKeyHash: <redacted>
BootSecurityInfo: 000003e9
ArmJtagDisable: 00000000
SecurityMode: 00000000
SwReserved: 00000000
DebugAuthentication: 00000000
OdmId: 0000000000000000
OdmLock: 00000000
ReservedOdm0: 00000000
ReservedOdm1: 00000000
ReservedOdm2: 00000000
ReservedOdm3: 00000000
ReservedOdm4: 00000000
ReservedOdm5: 00000000
ReservedOdm6: 00000000
ReservedOdm7: 00000000

You may also want to let the developers know about this bug so they can fix it in a future L4T release.

h/t: Problem installing/upgrading after burning secure-boot fuses · OE4T · Discussion #2176 · GitHub

[JerryChang]

hello david_charlap,

here’s patch for odmfuseread.sh to support relative key paths.
0001-l4t-config-odmfuseread-Support-relative-key-paths.patch (1.7 KB)

[david_charlap]

Thanks. That patch works.