Jetson Orin NX secure boot: confirm BootSecurityInfo fuse value

Hi team.

We’re currently preparing a production fleet of Orin NX devices for a retail deployment and need secure boot plus disk encryption enabled before shipping.
A question came up during the process, could you route this to the Jetson BSP / security team? It’s a quick yes/no confirmation before we fuse production units, and since fusing is irreversible we’d like an authoritative answer.

Setup:

  • Jetson Orin NX, JetPack 6.2.1
  • Posture: PKC (RSA-3K) + SBK + OemK1 (for disk encryption)
  • Our unfused modules read BootSecurityInfo = 0x1E0 from the factory

Question:
Per the Jetson Orin Fuse Specification (v1.5, bits [8:4] reserved) and forum thread 335952, we plan to burn BootSecurityInfo = 0x3E9 (0x209 OR’d with the factory 0x1E0) rather than the documented 0x209. Can you confirm 0x3E9 is correct for this configuration?

hello eva7,

yes, 0x3E9 is the correct BootSecurityInfo value for your secureboot authentication scheme, it’s a target fused with RSA-3K PKC + SBK + OemK1.

here’re couple of FYIs,
(1) the root-of-trust that uses the NVIDIA SoCs fuses to authenticate boot codes ends at the bootloader.
once you fused a target, you must provide the identical keys to re-flash a target, otherwise it aborts the flash process in the very beginning stage with Boot Rom communication failed errors.
(2) as you can see from developer guide, Tool for EKB Generation.
it’s EKS image to include OEM_K1, you’ll need to generate a new EKS image for updating QSPI. otherwise, you’ll see error logs.. fail to unlock the encrypted dev at boot-up stage.