• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 76 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM263P4: SWRV_APP reading in Secure Booting

Kunukuntla Geetha
Intellectual 350 points

Part Number: AM263P4

Hi,

It is noted that The EFUSE SWRV_APP is read and is passed as is by the HSM Boot ROM to the application via the Asset Interface. This EFUSE has a length of 192bits and the interpretation of this is left to the HSM Runtime developers. 

Why cannot HSM Runtime read EFUSE SWRV_APP directly? What are the assests left HSM Boot ROM after eclispsing?

Thanks

Geetha K

  • 0
    TI__Guru 54410 points

    Hi Geetha,

    Any software revision of the application is handled by the HSM RT as per boot flow,

    Application authetication as well as verification of SW revision is supposed to be undertaken by the HSM RT firmware.