• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 810 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.

Original question:

SK-AM62-LP: sequence for enabling secure boot using custom keys

SK-AM62: Building secure boot with processor SDK

Matthew Vernon
Prodigy 100 points

Part Number: SK-AM62

Tool/software:

The processor SDK using Yocto can automatically build a tiboot3.bin image for R5 which is signed with a key matching the one programmed to OTP. Once HS mode is set using OTP the image must be correctly signed in order to boot.

Moving on to the A53 bootloader:

  1. It appears that the SDK does not produce secure images for the A53, as there are no calls to secure-binary-image.sh. Is that correct?
  2. If the R5 SPL is signed does that mean the A53 images need to be signed to run?
  3. If #2 above is true, is there a way to configure the R5 bootloader to allow unsigned A53 images in order to incrementally test the build system?

Thank you,

Matthew