TMS320F280039C: 280039C DCSM with password lock download problem

Foriner

Part Number: TMS320F280039C

Tool/software:

Hi，TI expert：

I configured the software project using 280039c, and configured DCSM, enable the password lock, and then I burned the project into a new DSP, tried many times, and every time it was the same phenomenon: after using the out file for the first time, an error would be reported, and the DSP found that only the password could be displayed, and the other flash and OTP data were 0, that is, the locked state; In this case, the program is running abnormally, you need to connect again, after decrypting and burning the out file again, the password is completely locked, and then the program will run normally, what is the reason?

the first time download error is：

the first time, password didn't lock

but flash data is locked

5 months ago

0 Luke Jones 5 months ago

TI__Mastermind 20540 points

Hi Foriner,

Please refer to this thread:

https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1293263/tms320f280039c-dcsm-program-error/5020125?tisearch=e2e-sitesearch&keymatch=f28003%252520dcsm%252520issue#5020125

Let me know if you have additional questions.

Thank you,

Luke

0 Foriner 5 months ago in reply to Luke Jones

Intellectual 425 points

are ti expert suggest to do like this? tks

the link is page off in picture

0 Luke Jones 5 months ago in reply to Foriner

TI__Mastermind 20540 points

Hi Foriner,

Yes this is the correct method to program the user otp when using custom passwords. If not, the zone will become locked after the passwords are programmed, which will prevent the rest of user otp from being programmed. The entire flash will be inaccessible if the zone is locked and the GRABSECT values are left as all Fs.

Thank you,

Luke

0 Foriner 5 months ago in reply to Luke Jones

Intellectual 425 points

I tried what you said and it really worked. But I want to know, what exactly does the impact of these 2 options bring, and do these 2 options have to be unchecked at the same time? Older versions of CCS don't have the first option, and the second option is usually checked by default, if I just uncheck the first option, will that solve the problem?

0 Ryan Ma 5 months ago in reply to Foriner

TI__Mastermind 18476 points

Hi Foriner,

Luke is currently OOO until July 1st. I will see if we can get another expert on this thread.

BEst,

Ryan Ma

0 Foriner 5 months ago in reply to Ryan Ma

Intellectual 425 points

Okay, looking forward to a response from the new expert.
I want to determine which option has the greater impact, and what is the mechanism of this effect? Why does the default project configuration of ccs12 have the problem of DCSM burning? Does TI consider optimization?

0 Ryan Ma 5 months ago in reply to Foriner

TI__Mastermind 18476 points

Hi Foriner,

I have messaged a few other experts, let me ping again.

Best,

Ryan Ma

0 Vivek Singh 5 months ago in reply to Foriner

TI__Guru** 112995 points

HI Frontier,

Yes, user need to select both these options because on reading the security setting to verify, device get locked with new security setting. Similarly if you have unlocked the secure part using existing password for re-programming then on reset device will be locked again and programming operation will fail.

Hope this helps.

Regards,

Vivek Singh

0 Foriner 5 months ago in reply to Vivek Singh

Intellectual 425 points

Do you mean unchecked? What I want to know is that when burning DCSM, 1) option 1, why is it not allowed to reset the DSP before flashing? What is the difference between resetting and not resetting a DSP before flashing? 2) Option 2, if I cancel the verification after flashing, what should I do if there is a flashing error? Are there any risks? In addition, does this flashing flash include burning OTP?
In addition, if you need to cancel these two options when burning DCSM, why doesn't TI cancel these two options by default when building a project?

0 Vivek Singh 5 months ago in reply to Foriner

TI__Guru** 112995 points

Hi,

Foriner said:
1) option 1, why is it not allowed to reset the DSP before flashing? What is the difference between resetting and not resetting a DSP before flashing?

Before flashing the device, one need to unlock the device by entering correct 128bit password. If you reset the device then it'll re-lock the device and flash programming will fail.

Foriner said:
2) Option 2, if I cancel the verification after flashing, what should I do if there is a flashing error? Are there any risks? In addition, does this flashing flash include burning OTP?

This is only needed if user is flashing the USER OTP (with security settings). If not, then it's not needed.

Foriner said:
In addition, if you need to cancel these two options when burning DCSM, why doesn't TI cancel these two options by default when building a project?

I think we have this option. Let me check with our flash tool team and get back to you.

Vivek Singh

0 Luke Jones 4 months ago in reply to Vivek Singh

TI__Mastermind 20540 points

Hi Foriner,

Discussed this with Vivek and out team, since customers not using DCSM will always want these options enabled, these options will continue to be enabled by default in future CCS releases. Apologies for the inconvenience.

Let us know if you need further assistance.

Thank you,

Luke

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F280039C: 280039C DCSM with password lock download problem