• Locked Locked
  • Replies 0 replies
  • Subscribers 81 subscribers
  • Views 2261 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

[Concerto] Known Issue: Code Security Locked TMX Devices

Lori Heustess
Guru* 91215 points

Issue:

Flash may not be erased on some TMX samples.

Symptom:

This will show up as a locked code security module because the password will not be erased (all 1's).

  • Loading code to password protected blocks will fail.
  • Code Composer Studio will not be able to erase the flash.

Workaround:

Unlock the code security and erase the flash:

1.      Open a memory window in CCS: View --> Memory


2.      Enter the Flash password address location in hex format and you will be able to look at the values in the password location. 

128bit Password locations for M3, Zone 1:        0x200000, 0x200004, 0x200008 and 0x20000C

128bit Password locations for M3, Zone 2:        0x27FFF0, 0x27FFF4, 0x27FFF8 and 0x27FFFC

128bit Password locations for C28x:              0x13FFF8, 0x13FFFA, 0x13FFFC and 0x13FFFE

 

3.      Copy the password from the password locations and paste it in CSM KEY fields of Flash plug-in  (available in CCS version 4.2.4.00029 or later)

  • Tools -> on-chip Flash
  • The below screenshot shows the dialog for the M3.
  • On M3 - unlock both zone 1 and zone 2

 

Note: The password is visible to the debugger because the PSWDLOCK bitfield has not been programmed. On a fresh device this bitfield is all 1's. When the bits are all 1 (i.e. during development) the password can always be read and thus the device can be unlocked.  This bitfield should be programmed, so that it is not all 1s, in production to block this read access.

4.      After the device is unlocked, select "erase" from the flash plug-in

5.  Refresh the memory window(s) with the password(s).  If the erase was successful the password(s) will read back all 0xFFFF.

 

 

If you receive an error after unlocking the device, it may be a known plug-in issue.  Please refer to: Item 3 in Known flash plug-in issues at this forum thread:  http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/t/126824.aspx

The details in this forum thread may help as well.

http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/t/129146.aspx

 

 

EDIT: Corrected note in step 3