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.

TMS320F28035: CSM Inactivation

Part Number: TMS320F28035


Hello,

According to this code comment - file DSP2803x_CSMPasswords.asm, lines 79-83:

; For code security operation, all addresses between 0x3F7F80 and
; 0X3f7ff5 cannot be used as program code or data.  These locations
; must be programmed to 0x0000 when the code security password locations
; (PWL) are programmed.  If security is not a concern, then these addresses
; can be used for code or data. 

And according to the Piccolo 3-day workshop (example at ,), page 10-17, section "Code Security Module and Passwords":

The CSM module also requires programming values of 0x0000 into flash addresses 0x3F7F80 through 0x3F7FF5 in order to properly secure the CSM.  Both tasks will be accomplished using a simple assembly language file Passwords.asm.

My question is the following:

What happens if CSM_RSVD (0x3F7F80 - 0x3F7FF5) is programmed to a non-zero value when CSM keys are changed from 0xFFFF to some other value?

Will it prevent the device from locking, or cause the device to become unrecoverable?

  • Hi,

    What happens if CSM_RSVD (0x3F7F80 - 0x3F7FF5) is programmed to a non-zero value when CSM keys are changed from 0xFFFF to some other value?

    That will not prevent from locking and also with not make device locked permanently. This step is additional step which user should perform to complete the security initialization of device.

    Regards,

    Vivek Singh

  • Hi Vivek,

    Thank you for the prompt reply. Is setting the CSM keys to 0xFFFF the only way to prevent the CSM from locking?

    We are worried that an upset to the CSM keys might lock us out. The hope was that if writing 0xFFFF to the CSM_RSVD could prevent the CSM from locking, the odds of the entire CSM_RSVD field being corrupted to 0x0 are much lower than the odds of a single corruption to the CSM_KEYS and we would be able to manage the risk that way.

  • HI,

    Thank you for the prompt reply. Is setting the CSM keys to 0xFFFF the only way to prevent the CSM from locking?

    By default password values are ALL_1 (erased flash) hence CSM is unlock. User need not to program 0xFFFF again. But if flash operation gets interrupted in between that that could change these values and locks out the device and that does not depend on value.

    Regards,

    Vivek Singh