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.

66AK2E05: Security Features and Secure Boot Performance

Part Number: 66AK2E05

Hi,

Could you clarify what is causing a delay? We measure 476ms delay from reset release to the first SPI read, where the ROM bootloader is trying to load just a 35KB image. I don’t see how that could be boot size dependent because the ROM code won’t know what size to pull until it reads from Flash.

RESETSTAT goes active a handful of ms after reset release, so the part is coming out of reset as expected.  BOOTCOMPLETE was instrumented as well but discovered that it only goes active after all of the cores are booted.

Thanks,

Jeramie

  • Hi Jeramie,

    What are you trying to boot? Is this the RTOS IBL or a custom boot image?

    Do you use custom board or a reference TI EVM?

    Best Regards,
    Yordan
  • It's a secure boot using VxWorks but also investigating Linux / TI-RTOS. This is on a customer board.
  • Jeramie,

    We don`t typically support K2E Security related questions on Public E2E. Can you you post this on forum to posts security related issues. If you don`t have access, I can add you to that forum.

    I will respond to the SPI boot related question here. The ROM bootloader on the device for SPI and I2C mode operates the device in PLL in bypass mode which means that the device is running at the speed of input clocks so the device is running orders of magnitude slower. The other thing is before it reads the image it needs to read the hash of the public key and compute the key to authenticate the incoming image.

    Regards,
    Rahul