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.

TMS320F280025: DCSM relationship to ECSL and BOOT mode

Part Number: TMS320F280025

Hi Vamsi,

My customer wants to use F280025 and they have to use DCSM.

and I have a question on enable DCSM must enable ECSL?

since this is a problem if we enable ECSL, which we can not connect Emulator again?

I got this message on TRM, 3.12.1.2 Emulation Code Security Logic (ECSL)

https://www.ti.com/lit/ug/spruin7a/spruin7a.pdf?ts=1607073251078&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FTMS320F280025

And The solution to this problem is:
• Use the Wait Boot Mode boot option. In this mode, the CPU will be in a loop and hence will not jump to the
user application code. Using this BOOTMODE, the user can connect to CCS and debug the code.

on the other hand, I found there is a method to disable the ECSL.

3.12.7.7 ECSL Disable Considerations for Any Zone

if we copy the code and give the correct password in the initiation code, then ECSL is disabled and we do not need to pull the boot pin into wait mode anymore.

is my understanding right?

BR

Emma

  • Emma,

    Emma Wang said:
    I have a question on enable DCSM must enable ECSL?

    You can still have the DCSM enabled and have a provision to disable just the ECSL. For this, the lower 64 bit password of the entire 128 bit password need to be provided. It is explained in the Section 3.12.1.2: "To allow emulation of secure code, while maintaining the CSM protection against secure memory
    reads, the user must write the correct 64-bit password into the CSMKEY (0/1) registers, which matches the
    password value stored in the USER OTP of that zone. This will disable the ECSL for the specific zone."

    Emma Wang said:
    if we enable ECSL, which we can not connect Emulator again?

    If the ECSL trips, the emulator connection is disconnected. A device reset is needed before you can connect to the emulator again.

    Emma Wang said:
    if we copy the code and give the correct password in the initiation code, then ECSL is disabled and we do not need to pull the boot pin into wait mode anymore.

    If using the boot pin to enter Wait boot is not an option,  
    For the ECSL to be disabled, you don't need to provide the entire 128 bit password in your initiation code. You can just provide the lower 64 bit of the zone's password for the ECSL to be disabled.

    Hope this helps.

    Please click on "verify answer" button at the bottom of this post if this resolves your query.