AM62P: Secure Boot signature validation error when the hashes are not locked

Chris Yorkey

Part Number: AM62P

Team,

We held a Secure Boot discussion with our [AM62P] customer and have a quick clarification.

In follow up, the customer was asking how TI indicates a Secure Boot signature validation error when the hashes are not locked. We would think that during boot, the console would have information regarding whether secure boot is enabled and if there are in fact validation errors. Of course, on a locked card, if the card will not boot. etc

Do we have any additional insight we can offer here?

TY,

4 months ago

0 Hong Guan64 4 months ago

TI__Guru* 79020 points

Hi Chris,
Please refer to <3. Difference on x.509 certificate/signature verifications on GP and HS (HS-SE and HS-FS)> in the FAQ
[FAQ] AM64x/AM62x SoC redundant/recovery boot support in ROM booting R5 bootloader
Best,
-Hong

0 Chris Yorkey 4 months ago in reply to Hong Guan64

TI__Genius 16380 points

Thank you, Hong. I think the key statement here with the Q&A forum post you pasted is "- The development SW signed with "self-signed x.509 certificate" in initial SW development/testing phase on GP/HS-FS are auto-nullified when moving onto the production phase on HS-SE, where only SW with real "x.509 certificate" signed with the user's matching "real" RSA private key would work." especially in terms of GP/HS-FS and HS-SE devices. Thank you again for your quick reply.

-Chris

0 Jim Taylor 4 months ago

Prodigy 20 points

The real question is what kind of logging occurs. With NXP, the log shows secure boot status and errors when the board isn't locked. Does TI Secure Boot process also provide logs around secure boot status and errors?