Hi, Is there any method to get the UID that we could read by "tegrarcm --uid " in the stage of uboot?
What is the purpose of doing this in “uboot”? Also, tegrarcm is a host tool.
I need this UID to check the system is signed or not in the stage of uboot.
sudo ./odmfuse.sh -i 0x21 -c PKC -p -k ./rsa_priv.pem
the back of “tegrarcm --uid” is still ‘NS’ that the first numble is 4
sudo ./tegrarcm --uid
The log of odmfuse:
PKC HASH: 0xe2fd7ef5d68f39ccad88be7db940ae9b4598e9f9a26f03282ea5c68cd0f5eccd
*** Generating fuse configuration … done.
*** Start fusing …
./tegraflash.py --chip 0x21 --applet nvtboot_recovery.bin --cmd “blowfuses odmfuse_pkc.xml;”
Welcome to Tegra Flash
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0026 ] Parsing fuse info as per xml file
[ 0.0038 ] tegraparser --fuse_info odmfuse_pkc.xml blow_fuse_data.bin
[ 0.0055 ]
[ 0.0055 ] Generating RCM messages
[ 0.0066 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0080 ] RCM 0 is saved as rcm_0.rcm
[ 0.0096 ] RCM 1 is saved as rcm_1.rcm
[ 0.0096 ] List of rcm files are saved in rcm_list.xml
[ 0.0097 ]
[ 0.0097 ] Signing RCM messages
[ 0.0109 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0119 ] Assuming zero filled SBK key
[ 0.0205 ]
[ 0.0205 ] Copying signature to RCM mesages
[ 0.0253 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0271 ]
[ 0.0271 ] Boot Rom communication
[ 0.0282 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.0294 ] BR_CID: 0x421010016445b5062400000009fe00c0
[ 0.0310 ] RCM version 0X210001
[ 0.0469 ] Boot Rom communication completed
[ 1.0576 ]
[ 1.0577 ] Blowing fuses
[ 1.0616 ] tegrarcm --oem blowfuses blow_fuse_data.bin
[ 1.0632 ] Applet version 00.01.0000
[ 1.4771 ] Successfully burnt fuses as per fuse info blob
[ 1.5008 ]
*** The fuse configuration is saved in bootloader/odmfuse_pkc.xml
*** The ODM fuse has been secured with PKC keys.
*** Flash “signed BCT and bootloader(s)”.
there’s another scripts for fuse reading, if you’re download secureboot tools for the latest release package. (i.e. l4t-r32.4.3)
$ sudo ./odmfuseread.sh -c PKC -i 0x18 -k <key> jetson-tx2
I don’t find odmfuseread.sh in the latest release of jetson nano(i.e. l4t-r32.4.3). But it appear in the TX2.
Are you sure that it’s ok to work on the jetson nano.
currently, odmfuseread.sh scripts to read the fuse info from the target board only supports with T186 and T194 platforms.
AFAIK, you cannot read fuse via uboot, there’s
tegra-fuse for placing fuse information, you may using
$ sudo ./tegrafuse.sh to display all the fuses on the target.
But now the device couldn’t boot normally no matter that i flash the device with -u key or not
could you please share the commands you’re used,
you may also setup serial console to gather bootloader messages from device side for reference.