Hello,
In my Jetson AGX Orin configuration, I have a base flash image (flashcmd.txt and ancillary files) made using the no-flash option and the necessary secure keys to encrypt associated bootloader and UEFI images. All of that works great and I use that single flash image to flash multiple devices in the same manner…that had their fuses burned using those keys.
However, the problem I’m running into is for a new device for where I just burned its fuses in the same manner (and keys) I used for the base flash image mentioned earlier. When I burn the fuses for a new device, the fuse burn is successful, but I cannot get the base flash image to successfully flash the device. Everytime I try to flash it using that image, it will stop after a third of a second with the following error:
[ 0.2875] ERROR: might be timeout in USB write.
Error: Return value 3
The only way I can get around this is to recreate a new base flash image (flashcmd.txt and ancillary files) made using the no-flash option and the necessary secure keys to encrypt associated bootloader and UEFI images. Then, if I flash with this image, it works fine.
From a production standpoint, how do I solve this issue? On the production floor, I plan on giving them the fuse config file to burn the fuses of each device (as step 1). Then, I plan on giving them the base flash image (that I previously created) to flash the device (as step 2). I do not want them to have to recreate the base flash image after every fuse burn application.
It almost seems like there is a date/time check or something similar that is forcing me to recreate my base flash image. Don’t know if that is accurate or not, but I’m not doing anything other than creating this image again in order to make it work. Obviously, this would not be desirable for the production floor.
Any suggestions?
Thanks,
Jim