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.

TMS320F2800157: Failure to use sci bootloader after using DCSM and JTAG encryption

Part Number: TMS320F2800157

Tool/software:

When I do not use JTAG and DCSM encryption, I use sci bootloader to transfer the boot written by myself, which can run normally and download apps. However, after using JTAG and DCSM encryption, I used sci bootloader to transfer the boot written by myself, and even normal operation could not be achieved. Check the EXEONLYRAM register, and the RAM is not set to execute only, as shown below:

I want to know what the problem might be.

  • Normal operation means that it does not work properly, for example, I did not receive the version number I sent after initialization

  • Hello,

    If you have secured the flash via DCSM, the SCI bootloader stored in the bootROM will be unable to modify a secure flash region to download your custom bootloader. I would suggest uploading your bootloader to flash BEFORE securing the memory via DCSM. A custom boot loader stored in a secure memory region will still be able to modify other secure flash regions.

    Thank you,

    Luke