Hello @JerryChang
I tried the command line you suggest, here is the result.
$ ./tegrarcm_v2 --uid
BR_CID: 0x98021911647076c20c00000002ff8280
Could you please tell me if this value was expected ?
hello ilies.chergui,
it’s a bug with l4t-r32.4.3 release.
when no PKC or SBK is specified, the odmfuse.sh still generates a config in odmfuse_pkc.xml.
for example, <fuse name="BootSecurityInfo" size="4" value="0x1" />
this is incorrect, that means PKC is enabled.
FYI,
such error fusing issue has already fixed in the l4t-r32.5 release.
however,
the BootSecurityInfo has been burned to enable PKC, but the PKC hash is zero (i.e. due to not setting the PKC key).
since fuse programming is non-reversible, there’s no ways to recover this board.
that’s say, this board is bricked.
Hello @JerryChang
Thanks to let me know that the device is bricked.
This is my second Jetson Xavier NX module that I broke because of the bugs or the documentations not updated.
How we can proceed about my Jetson Xavier NX module (eMMC version) ? Can I send it to your team and you send me new one ?
I hope you can help me because I already spent 800£ on Jetson Xavier NX
hello ilies.chergui,
yes, please contact the NVIDIA Customer Care team for the RMA process.
I have more details regarding to the failure.
it’s bootrom always tries to verify the PKC hash first to communicate with the board.
due to the fuse is actually PKC hash, which is calculated based on a given PKC key.
so, the board is bricked, unless you can find a PKC key which has an all-zero PKC hash.
to summarize the status of SecureBoot package,
for l4t-r32.4.3, it’s comment #25 to have workaround to enable secureBoot by programming all fuse at once.
for l4t-r32.5, the fixes of fusing error has included, it’s suggest moving to the latest JetPack release to enable secureBoot.