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.

TMS320F28P650SH: What are the differences between the DCSM of 28P65 and 2800157?

Part Number: TMS320F28P650SH

Tool/software:

After 28P65 is encrypted with DCSM, it cannot connect to the emulator without entering the wait boot mode. The CCS versions I use are 20.1.1, 12.8.0, and 12.8.1, and none of them can connect. However, all 2800157 can be connected to the emulator after encryption.

  • Hello,

    Our DCSM expert is out of office until next Monday, please expect a response 1-2 days after they return.

    Best,

    Matt

  • Hello,

    If you've secured the flash using DCSM, you must use wait boot to connect to the device via JTAG. Can you confirm you're able to connect when using wait boot mode?

    Are you using JTAGLOCK / JLM_ENABLE?

    Thank you,

    Luke

  • I didn't use JTAGLOCK/JLM_ENABLE.

    Are you using JTAGLOCK / JLM_ENABLE?

    I changed the bootpin of 2800157 to 0. Every time it starts from flash, so it's impossible to enter waitboot. It can still connect to the chip after encryption, which is exactly what I want.

    However, after the bootpin of 28P650 is also changed to 0, it can never be connected again. So I want to know the difference between them. And how to solve this problem of never being able to connect

  • I yyoung,

    It could be that you secured different memory regions on F280015x vs. F28P65x. If the program counter is currently in an unsecure memory location, you will be able to connect to the device.  If you implemented any mechanisms to unlock the DCSM either from your application code or over JTAG then that would allow you to connect as well even if you weren't in wait boot.

    Thank you,

    Luke