• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 58 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

PROCESSOR-SDK-AM64X: SBL Signing

Christopher Holland
Prodigy 190 points
Part Number: PROCESSOR-SDK-AM64X

Hi,

I am trying to recreate the tiboot3.bin that is distributed as part of the linux sd card.

I am using this link as a guide in creating the tiboot3.bin

software-dl.ti.com/.../HSFS_MIGRATION_GUIDE.html

I believe I setup the paths correctly and I am assuming the addresses are correct.

When I build the file, the size is only 285 K. The same size as the one in the folder C:\ti\mcu_plus_sdk_am64x_09_00_00_35\examples\drivers\boot\sbl_emmc_linux\am64x-evm\r5fss0-0_nortos\ti-arm-clang 

and it's not booting. I don't know, maybe I am using the wrong sbl and I need sbl_sd.release.hs_fs.tiimage?

Also, I should just have to rename sbl_emmc_linux.release.hs_fs.tiimage to tiboot3.bin

https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/09_01_00_41/exports/docs/api_guide_am64x/BOOTFLOW_GUIDE.html

  • 0
    TI__Mastermind 25971 points

    Hi Christopher,

    May I know why you are trying to boot `sbl_emmc_linux` from SD card? Though it is possible to boot, the `sbl_emmc_linux` once booted will ultimately try to boot the further images from eMMC only.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 190 points

    May I know why you are trying to boot `sbl_emmc_linux` from SD card?

    >>I am trying to recreate the tiboot3.bin that is distributed as part of the linux sd card.

    idk, maybe I am trying to use the wrong bootloader and should be using the sbl_sd.release file.

    The end goal is to be able to use the newly generated keys / certificate, but before I program the keys, I would like to verify that I can create a valid tiboot3.bin file and an app_image, but that is next on the agenda.

    Thank you,

  • +1 in reply to Christopher Holland
    TI__Mastermind 25971 points

    Hi Christopher,

    The signing steps are already integrated in all the SBL's and applications makefiles of the SDK.

    The SDK is set to automatically generate the signed image for HS-FS devices identified by the extensions `.hs_fs.tiimage` and `.appimage.hs_fs` for SBL and application respectively.

    For HS-SE device, you only need to do the following changes:

    1) Change DEVICE_TYPE to HS in `devconfig/devconfig.mak`.

    2) Replace TI dummy keys with your custom keys in `tools/boot/signing` folder.

    Then, any example build will generate the HS-SE images identified by the extensions `.hs.tiimage` and `.appimage.hs` for SBL and application respectively.