Hi, I’m just starting a design that will likely use the Jetson Orin NX SOM, and I’d like to understand any considerations we should make to enable the option to move to using secure boot and secure data fusing in the future if we decide that we want to.
Is there a way to design the software or hardware incorrectly that could prevent implementing security features like secure boot and securely signing firmware/software in the future?
Are there any ‘gotchas’ to watch out for?
Thanks for any guidance.
there’re several topics about Jetson security, i.e. SecureBoot / OP-TEE/ Disk Encryption / Secure Storage
however,
as you can see in developer guide for Security session. Jetson Orin NX only support with SecureBoot.
for example, SecureBoot, Applies to the Jetson Orin NX and Nano series, Jetson AGX Orin series, the Jetson Xavier NX series, and the Jetson AGX Xavier series. OP-TEE, Applies to the Jetson AGX Xavier series, Jetson Xavier NX series, and Jetson AGX Orin.