TMS320F28377D: Uniflash encrypt failed

Hi,

We notified our security expert to help you on this.
Please expect the reply in a day or two.

Thanks and regards,
Vamsi

OK，thinks, I'm looking forward .

Hi,

Can you unlock the device using the password programmed and then check the values at USER OTP location for PSWDLOCK and CRCLOCK? Are these 0xFFFFFFFF or some different value?

Regards,
Vivek Singh

Yes, I can unlock the device using the password programmed. what's " check the values at USER OTP location for PSWDLOCK and CRCLOCK"mean. How can I check the values at USER OTP location for PSWDLOCK and CRCLOCK?

I expect a reply. Thank you.

Hi,

You need to open memory watch window and check the value at USER OTP address location for these fields (0x78010 and 0x78014) . You may be getting error because these location may have been programmed already with different values.

Regards,

Vivek Singh

Hi,

Think you very much. Befor I do  anything The  memory watch window show below

When I "ProgramPassword", and then "Lock" 

the vaule as below：

And then I  "Program OTPSECLOCK", But failed，It appears 

All values no changed.  as below

Hi,

Did you get a solution for your problem? I'm running through the same issue. However the error message is "Error performing current operation, missing necessary option. Operation cancelled."

I have an extra question please:

Do you know why PSWDLOCK is a 32 bits register on UniFlash although it's a 4 bit field? (same for the CRCLOCK ) 

Thank you in advance

Hi again, you might have to change the Uniflash version. I used to work ith the 4.5 and it didn't work. It does with the 4.1 version

Hi,Think you very much, change the Uniflash version,I got it.

Good to know you were able to get it working. Which version you tried to get it working?

Vivek Singh

Hi,
I tried 4.5, 4.4 and the 4.3 none of them allows to program the PSWDLOCK. Only the 4.1 works however it has other issues.
I don't understand though, why should I program a 32 bits register on the uniflash (Zx-PSWDLOCK) while it's a 4 bits field that is really programmed? In fact, if I fix the value of Zx-PSWDLOCK to 0xFFFFFFFE, or any other value it doesn't work. It only does when I put the same value (example: 0xAAAAAAAA or 0x00000000)
Thank you

Thank you for your reply. I think I wasn't clear enough. Actually by trying different values, I change the microcontroller. I am aware of the fact that it's one time programmable field. However I still don't understand how I should program the Zx-PSWDLOCK. Can you give me examples of values that could be accepted? Thank You

Are you not able to program any value other than 0x00000000/0xAAAAAAAA or PSWDLOCK feature is not working if program any other value?

Since I'im not interested in locking all my boards, i didn't try other values but 0xFFFFFFFE doesn't work (uniflash doesn't accept to program the field. When I try 0xFFFFFFEF it accepts it but i still can see the value of the password in the memory (No security)

oxFFFF_FFEF will not work. PSWDLOCK bits are 3:0. 7:4 are don't care (reserved). It is strange that you are not able to program 0xFFFF_FFFE value. The only reason it could happen is that ECC bits are already programmed (for example it's been already written with value 0xFFFF_FFEF).

All,

Thank you for reporting the issue with programming OTPSECLOCK.

I had a look at the code and found an issue with how it is looking up the value of the CRCLOCK setting. I have implemented a fix for this and it is currently scheduled to be picked up in the next version of UniFlash (in December).

For now, please continue to use UniFlash 4.1 for programming OTPSECLOCK for now.

Sorry for the inconvenience.

Thanks,
Ricky

Hi,

I want to realize encrypt with .out file.  First, I join .asm file in my project.

 Second, I modify the CSMPSWD like this:

The third, copy the contents of   to my project's CMD file.

Compile it and then download the .out file. But I failed the vaule also FFFF 

May I have an answer, please?

May I have an answer, please?

Hi,
Try the Uniflash version 4.1. It might work. Please note your passeword value, becuase you won't be able to see it anymore in the memory once you program PSWDLOCK
Thank you

I was under impression that after using version 4.1 the issue is resolved. If you have any further queries, can you re-post the question.

Vivek Singh