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.

TMS320F28379S: DCSM Configuration and Emulator Connection

Part Number: TMS320F28379S


Tool/software:

Hello,
I have a question about DCSM usage and JTag connection.
I'm studying DCSM through the project Import in CCS using dscm_security_tool.syscfg.

The configuration settings are as follows:
Flash A~H Sector - Lock
RAM LS0~4 - Lock
Password(CSMPSWD0~3) - My desired value
Boot Mode - Flash
PSWDLOCK - Final Lock

Questions:
1. Although it operates with Flash execution Code, the PWM Interrupt is copied to RAM.
In this case, since it's protected by GRABRAM rather than EXEONLYRAM, will the Code in the RAM area operate normally?

2. After executing steps 1-4 above, I set the PSWDLOCK.
How do I connect JTag after this?
The syscfg tool doesn't support Other(Wait/Flash) in Get Mode.
In the attached image, it's also selected as Flash Boot.
Should I use Wait Boot instead?

Have a great weekend~!

  • Hi Bae,

    I'd recommend programming the GET mode to flash, since a boot mode is always reserved for wait boot:

    Get / Flash is the only boot mode that is user configurable, and you likely always want to be able to use flash boot.

    The code you've allocated to RAM should function normally since it is in secured memory and you have not designated any memories as EXEONLY. Because of this, your code should have full permissions to read and write secure  memories. Not that any functions residing in unsecure memory will not have permissions for secure memory, even if those functions are called from code that resides in secure memory.

    Thank you,

    Luke

  • Thank you for the quick response.

    I would appreciate it if you could answer my second question.

    I am using CCS v11.