Jetson Nano fuse burn error

Hi,

I was using the odmfuse.sh script to burn the secure boot fuses. I was able to perform the burn of the secure-boot fuses in a jetson nano emmc board; however, I couldn’t burn the userspace fuses after that. In my test, I used the r32.4.3 L4T, which required a fix of an issue that provoked the disable of the secure boot during fuse burning following this post answer: topic144888

The command used to burn the secure boot fuses are the following:
sudo ./odmfuse.sh -i 0x21 -p -c PKC -k keys_priv.pem

Then, when trying to burd the userspace fuses, using the -o option of the odmfuse script, I got the following error:

*** Start fusing  ... 
./tegraflash.py --chip 0x21 --applet nvtboot_recovery.bin --cmd "blowfuses odmfuse_pkc.xml;"  
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.0013 ] Parsing fuse info as per xml file
[   0.0020 ] tegraparser --fuse_info odmfuse_pkc.xml blow_fuse_data.bin
[   0.0028 ] 
[   0.0028 ] Generating RCM messages
[   0.0035 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[   0.0041 ] RCM 0 is saved as rcm_0.rcm
[   0.0046 ] RCM 1 is saved as rcm_1.rcm
[   0.0046 ] List of rcm files are saved in rcm_list.xml
[   0.0046 ] 
[   0.0046 ] Signing RCM messages
[   0.0053 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0060 ] Assuming zero filled SBK key
[   0.0099 ] 
[   0.0099 ] Copying signature to RCM mesages
[   0.0106 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[   0.0116 ] 
[   0.0116 ] Boot Rom communication
[   0.0122 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[   0.0129 ] BR_CID: 0x621010016445b507200000000c000100
[   0.1298 ] RCM version 0X13
[   0.2582 ] Boot Rom communication failed
[   0.2582 ] 
Error: Return value 3
Command tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
failed.

Regarding the procedure I followed, what could be causing this error?

Thanks,
Luis

hello luis.murillo,

the odm_reserved and odm_lock fields still are writable until the corresponding odm_lock bit is programmed by changing the value of the bit from 0 to 1.
hence,
Reserved_ODM fuse are programmable until it disabled by the ODM_lock fuse.
could you please check odm_lock bit,
for example,
$ sudo ./tegrafuse.sh