• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 552 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.

OMAP-L138: OMAP-L138

prashanth tm
Prodigy 60 points
Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138

Hi,

I am using OMAP-L138E device in my design, when i am trying to connect the ARM core i am getting following error "Connect to the PRSC failed" in the CCS message

it is mentioned the since the OMAPL138E is of secure boot option, they got the error, but when they replaced this with non-secure boot device, it is working fine for them
I don't know how to change the secure to non secure option.
https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/119925/connect-to-the-prsc-failed-problem?ReplyFilter=Answers&ReplySortBy=Answers&ReplySortOrder=Descending

For above problem I got reply from TI as

Regarding your concern, please check the section PRSC errors of the Debugging JTAG page below. software-dl.ti.com/.../ccs_debugging_jtag_connectivity_issues.html We have this e2e post related to secure boot option : e2e.ti.com/.../omap-l138-sequence-boot-of-omapl138-security. In terms of security, this device supports a version of security which is referred to as Basic secure boot using a single encryption key. The documentation for the security offering is shown below http://www.ti.com/tool/SECDEVTOOL-OMAPL138C6748

After following the steps mentioned in the above link, I am getting below error

can anyone suggest me what to do ? is it due to HW problem or anything else ?

Regards,

Prashanth

  • 0
    TI__Expert 8885 points

    Hi Prashanth,

    I am checking internally on who can help this question.

  • 0
    TI__Guru** 116170 points

    Prashanth,

    Can you please let us know what you are trying to accomplish here. Secure and non secure OMAPL138 devices have several differences so it cannot be used the same way as non-secure part during initial setup. On non-secure parts JTAG is open and ARM is the boot master on this device so ARM boots first and brings DSP out of reset.  On secure devices, JTAG are locked out by default unless you boot a secure image to unlock the JTAG. On secure devices DSP is the boot master and ARM is considered non secure core which is power up by the DSP. On Secure OMAPL138 parts, you connect to the DSP first.

    FOr SEcure boot images, you need to use the secure AISGen tools to create the images with INI files which controls the encryption keys, MPU/IOPU setup and the TAPCFG registers that unlock the JTAG.

    COming to the log message you are seeing with SEcure UART host tool, the tool is indicating that the device is not sending the valid BOOTME string to the tool when it powers up, which could be a HW/setup issues. The expectation for the tool is that when the device is setup in UART boot mode and you power up the board, the ROM on the device should be able to send the string "BOOTME" correctly using the device clocks. For sanity test, you can open a serial terminal using Teraterm or HyperTerminal on Windows and see if you are reecieving this string correctly on COM9 port that you are using with the tool.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Prodigy 60 points

    Hi Rahul,

    Here I am attaching the file where it is clearly explained what we are doing

    Procedure_followed_to_boot_secureOMAPL138 .docx

    Regards,

    Prashanth

  • 0 in reply to prashanth tm
    TI__Guru** 116170 points

    Prashanth,

    I have reviewed the doc and have some comments. I am not sure if it was clear through the documentation but you can only use SEcure UART host load tool when the device is in UART boot mode. You cannot load the image into SPI and then expect BOOTME On the serial terminal as the ROM only does this for UART boot mode.

    Also, the SFH tool is only provided for GP devices, this tool is not designed for secure parts. On secure devices, the only option, we have is to unlock the JTAG by loading a JTAG unlock image using UART boot mode. Then you will need to load a SPI writer utility over JTAG To program the SPI flash. 

    Regards,

    Rahul 

  • 0 in reply to Rahul Prabhu
    Prodigy 50 points

    Hi,

    Myself mohan, working with prashanth on OMAPL138

    when we run the code hello word on OMAPL138LCDKEVM (OMApL138 is unsecured component) we are getting the out from DSP  which is attached here.

     .

    Now we are planning to load DSP.out file from OMAPL138LCDKEVM(OMApL138 is unsecured component) to our custom board which is having OMApL138 secured component.

    Kindly provide us the detailed procedure with commands to Flash the DSP.out file through UART on to the secure IC of OMAP L138

    Regards,

    Mohan 

  • 0 in reply to Mohan V S
    TI__Guru** 116170 points

    Mohan,

    I can share some reference examples with you. Please connect with me and I can private message you these reference examples. Generally it is a good idea to debug your code on non secure device and then migrate to secure device when the application development is complete.

    Regards,

    Rahul