hello rd1,
please also refer to my previous comments here
you should maintain keys by your own and having correct key assignment for image flashing.
I’ve never test to flash secure image to non-fuse board, we’ll need some time to arrange resources for confirmation.
thanks
Hi Jerry:
I hope to try again on one new device after you had tested according to our test procedures.
and I hope you could help to raise the priority, because we will soon be in production.
hello rd1,
I think it’s kinda unusual test procedure to flash secure image to non-fuse board.
yes,it is unusual test procedure.
we just hope to reflash ok if do this unsual option, but now we cann’t reflash, so we need your help.
Hi Jerry:
did the file “tegrarcm” should update? we see flash image or burn efuse all used this file
hello rd1,
we had test this by flashing secure image to non-fuse board.
it returns Boot Rom communication failed at the beginning of image flashing process.
so, it’s expected since you cannot do this image flash.
thanks
but our deivce cann’t reflash whether flashing secure image or flashing no secure image .
what should we do ,it always return Boot Rom communication failed
Hi Jerry:
how do you secure image, what is you command?
hello rd1,
don’t you already had a success by flashing secure image to the fused device?
here’s our steps to create secure image.
for example,
$ sudo BOARDID=3448 BOARDSKU=0002 FAB=200 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh --noburn -x 0x21 -y PKC -u <key.pem> jetson-nano-devkit-emmc mmcblk0p1
after that, use the image to flash the non-fuse board,
$ tar xpvf mfi_jetson-nano-devkit-emmc.tbz2
$ ./nvmflash.sh --showlogs
it report Boot Rom communication failed due to incorrect process.
so, please flash secure image to a fused board, thanks
Hi Jerry:
if we bured efuse, how to recover ,just for test
hello rd1,
you cannot recover that, since program the fuse is non-reversible.
for example, once a fuse bit is programmed by setting to 1, you cannot change the fuse value from 1 to 0.
thanks
Hi Jerry：
we used another device to test again, it report Boot Rom communication failed due to incorrect process sometimes ,but it flashed on going, actually not flash correctly.
for this:
scala@SCA-SH-VM002:~/work/bin/efuse/new_key/mfi_jetson-nano-emmc-smpsd_20210402213123_signed$ sudo ./nvmflash.sh
Start flashing device: 1-2, PID: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
Ongoing processes: 6441
it cann’t stop , but check the log ,it didn’t flash correctly.