Do we need to make efuse package again

Hi: we update L4T from r32.4.2 to r32.7.3,
Do we need to make efuse package again used 32.7.3 secureboot?

hello 18502109920,

would like to know is this module fused or not?
if yes, keys already fused, you don’t and you can’t fuse the module again.

We have produced more than 4K products whitch used fuseblob made by R32.4.2 secureboot. Now our code had update to R32.7.3, do we need make efuse package again used 32.7.3 secureboot? And our new Image used R32.7.3 compiled whether it works with burned fuseblob made by R32.4.2?

hello 18502109920,

those products should be already shipped, right?
you should pass the correct the keys when generating the OTA payload package, and performing Image-based OTA update to upgrade devices.

there’s see-also discussion thread for your reference, Topic 202827.
thanks

those products should be already shipped, right?
yes, they had been shipped.
In fact, we had two questions:
1, do we need make new efuse used R32.7.3 with the same RSA Key Pair which generated when made the old efuse used R32.4.2?
2.The shipped products burned old efuse used R32.4.2, our code base had update to L4T R32.7.3, when the shipped products update the image bins, Whether it has any impact on product work?