• State
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 18 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

AM6442: Secure boot

AM6442: SECURE BOOT

ganesh d
Prodigy 130 points

Part Number: AM6442

Hi HONG,

HONGS REPLY,

- Linux SDK on secure boot
https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/latest/exports/docs/linux/Foundational_Components_Migration_Guide.html
- binman configuration on AM64x
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-binman.dtsi?h=12.00.00.07
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-am64x-binman.dtsi?h=12.00.00.07

One simple option to build/sign u-boot (tiboot3.bin/tispl.bin/u-boot.img) is running "make u-boot" from the top-level SDK folder after the SDK package installation.

MY QUESTION,

I am not able to build the files using the above binman.dtsi in 9 SDK, is the dtsi file given are applicable only for 12 SDK or its applicable to 9 SDK...

After generating these images how o verify the images are signed... and what ae the next steps..

Thank you,

Ganesh D

 

  • 0
    TI__Guru* 89711 points

    Hello,

    The top level makefile abstracts the signing procedure of the U-Boot images in all the SDK versions. As long as you are using top level makefile to build U-Boot, you need not worry about the signing mechanism (binman or core-secdev-k3). All you need to do is replace the default keys with your custom keys and build the U-Boot using the top level makefile to make sure the U-Boot images are signed with your custom keys.