How unique is BR_CID of a Orin AGX soc/som?

Hey,

i was able to query the BR_CID of a Orin AGX when in recovery mode via

./bootloader/tegrarcm_v2 --new_session --chip 0x23 --uid

when inside the BSP tarball.

Since our usecase is based on a really unique ID that also cannot change in future, my question would be, how unique is this BR_CID and could it be changed in future via some update of the bootloader or so?

Also read about ECID in the past, whats the difference to that? would ECID be “more unique”? How can i read ECID from a Orin in recovery mode?

BR_CID and ECID could be converted to each other with some calculation/bit conversion.

They are unique.

Nice thank you, so does this also mean the BR_CID never changes since it is part of a the boot-ROM?

Yes, this part will never change.

Marked your answer as a solution, having a total different question now.

Is it just me or is the documentation for r35.4.1 broken right now?

See e.g.
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/SD/Security/SecureBoot.html#orin-reference-fuse-configuration-file

the codelisting doesnt have any content for me:

Already tried different browsers.

Please file a new topic and we will handle that there. Also, try jp5.1.3 document since that is the latest one.

1 Like

created a new topic here: Documentation of L4T 53.4.1 broken? Orin

The documentation for r35.5.0 seems to be okay: Secure Boot — NVIDIA Jetson Linux Developer Guide 1 documentation

are there any changes between r35.4.1 and r35.5.0 regarding the whole “security” documentation?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.