I see a partition defined for fuse bypass. What is the purpose of this partition? If the security fuses are written, does this partition allow you to override the verification check?
[Note: I saw it mentioned as Fuse Bypass for Nano. Even though the same partition name is used for TX2, so it may not be used for fuse bypass, in which case my question is irrelevant]
fuses can be bypassed only on non-production devices.
this feature can be used to overwrite any writable fuses by adding offset and value in a configuration file, i.e. fuse_bypass.xml.
these will get stored in a fuse bypass partition during flashing, on code-boot, bootloader retrieves the offset and value of fuses from the fuse bypass partition and overwrites those fuses with values specified during flash.
this avoid the trouble of sending bypass files on each cold-boot
thanks
At the moment I have issues with booting my Jetson Nano Developer Kit. Somehow I may have burned the fuses for SB with PKC in production mode. I keep the RSA key on safe location. This action should not have been supported, but I read this article latter - so I cannot flash the rest of the partitions signed with the PKC key nor boot it without SB PKC in normal non-secure NS mode.
I guess with the right fuse_bypass configuration I could be able to boot it without SB/PKC, right? Is there such sample fuse_bypass config available to bypass the SB with the PKC?
On the other hand, I’d like to test the SB with PKC for production module: can this be done on devkit device with fuse_bypass?