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.

OMAP-L138: OMAP-L138 SPI SECURE BOOT

Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138

i'm a newbie, currently i have OMAP-L138 secure boot chip, the bootmode we use is SPI, my requirement is

1. Unlock JTAG to debug the device.

2. Load custom SBL that i currently have which is  working fine in the non secure version of OMAP-L138.


so far from the documents and previous discussions  i read what  i understood is that, to unlock JTAG the ini file should be configured as

bootExitType = NONSECURE  TAPCFG= 0x0000FFFF BOOTMODE=SPIMASTER (since our boodmode is SPI) and generate ais file using SecureHexAIS_OMAP-L138.exe

i got  the command to generate ais file from some of the previous discussions in the forum

SecureHexAIS_OMAP-L138.exe -ini <file name>.ini -otype binary -o <file name >.ais <file name>.out

After the ais file is created connect the UART0 to pc and write this ais file to the device using OMAP-L138 Secure UART BOOT Host Tool, and i can unlock the JTAG

The ini file that i got from forum is attached here,  https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/4048.spi_5F00_test.ini

my questions are

1. The steps mentioned above is right or wrong ?

2. Does this ini file meet my requirement to unlock jtag or should i configure something else in this file ?

3. will my custom BL which runs on non secure omapl138 suit this secure boot omapl138 if not what changes i have to make it suit the secure boot device?


(if you tell me what to do exactly rather than providing some links or pdf it would be nice)




  • The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • Hi Anthony
    Looks like we missed responding to this query -
    Do note that our security expert for this device is out this week, so responses maybe further delayed.

    I went through this post , and I do not see any specific issues as long as you are following and up to speed on the guidance provided in the following wiki
    processors.wiki.ti.com/.../Basic_Secure_Boot_for_OMAP-L138_C6748

    Given that you have no way to test the secure device unlock till you get your custom hardware, I would say just make sure that you understand the differences between LCDK and your custom board and make sure you are accounting for the board differences e.g. boot type, boot media part # (do you have the same SPI on your board as used by our software/example) , external memory settings etc? Those changes will be needed to be comprehended as you would even when working with a non secure device on a custom board.

    I have not reviewed your ini file in detail - but if you run into issues when you get your board/ or are trying this ini file , please let us know and we should be able to help support you.

    Regards
    Mukul
  • hi Mukul Bhatnagar

    Thanks for the reply, well i have custom HW with me ryt now but i thought after confirming the procedure i could proceed so that things wont get worse.

    if we need to unlock jtag only way is to flash the ais file via UART ryt ? the bootmode is SPI so will the UART work at the time of boot, or the UART is independent whatever the bootmode is ?


    what did u mean by this "# (do you have the same SPI on your board as used by our software/example) , external memory settings etc?"

    Are you talking about bus width ? what all settings i have to configure, can you explain in detail?


    you mentioned that your security expert for this device is out this week, if so ill wait.
  • If your board supports UART boot , you should be able to try unlocking the device as listed on the wiki
    processors.wiki.ti.com/.../Basic_Secure_Boot_for_OMAP-L138_C6748

    >>what did u mean by this "# (do you have the same SPI on your board as used by our software/example) , external memory settings etc?"
    The sample examples for SPI boot mode maybe for the TI EVM , so depending on whether the SPI flash on your board is similar and whether on not the DDR memory on your board is similar or not, you may need to adjust timing/configurations to boot appropriately for devices on your custom board.

    Given you have your custom board, please go ahead and try based on the steps listed in the wiki and if you run into issues please open a new post with specific issues.

    I will mark this thread closed. You can either reopen it or better yet create a new one for any specific issue you run into.

    Regards
    Mukul