TMS320F28335ZJZS locked (code security module is locking the flash)

No, this is not possible. Did customer investigate what led to this inadvertent locking in the first place?

In fact, problem is that while writing flash, code composer crashed and flash is in an unstable state.
Now, since this, we can't write the flash anymore.

Some more precisions about this issue :
1- Code Composer Version : Code Composer v5.5.0.00077
2- When we try to connect the target, here is the error we get
"C28xx: Flash Programmer: Warning: The configured device (TMS320F28335), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file."
3- When we try to load the program, we get this error :
C28xx: Flash Programmer: Error encountered when writing to flash memory
C28xx: GEL: File: D:\jdewaele\ISTS\Bootloader\bin\bootloader_1.0_debug.out: Load failed.
4- While connected with the JTAG debugger Spectrum Digital XDS200, we can access CPU and peripheral registers.

Thanks for your help,

Hi Marie,

2- When we try to connect the target, here is the error we get
"C28xx: Flash Programmer: Warning: The configured device (TMS320F28335), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file."

You should not get this error. This means CCS is not detecting the device correctly and in that case flash operations will not work even though device is not LOCK. Are you using the device ccxml file from controlSUITE? Which one?

4- While connected with the JTAG debugger Spectrum Digital XDS200, we can access CPU and peripheral registers.

What about the flash locations? What value you see in Flash location via CCS memory watch view?

Regards,

Vivek Singh

Hi Vivek,

2- We are not using ControlSuite. Whatever, we are using exactly the same configuration with a board working well and everything is ok.

4- Flash is containing data from address 0x330000 to 0x333C63 (included).
Everything else is 0xFFFF.

Dumping the flash memory is working well but the 4 first words are 0xFFFF and should be something else.
All other written words seem to be the correct words, except that some words are missing (our binary data should be located from address 0x330000 to 0x3385C3.

Thanks for your help,
Regards,
Marie

Hi Marie,

Look like you attached a file but it did not came though. Can you attach the file again.

Since you are able to read the flash content, device is not locked. On locked device flash content would show value 0x0.

The Ist error you are getting is not correct. Unless that is fixed, you should not try flash operation. Since you are using the same setup for other boards and it works fine, there could be some issue with this particular device or board.

Did it ever worked fine in past?

Regards,

Vivek Singh

Hi Vivek,

I didn't attach any file so it is not surprising you didn't find it.

In fact problem is that when we were programming flash memory, code composer crashed and didn't write all the words of our executable.
That's why we are missing a part of it.

How could we do something to erase the flash and start writing it again ?

Thanks for your help,
Regards,

Marie,

You should be able to erase the flash using CCS Flash plug-in but for that Ist you have to resolve the issue related to device configuration.

Can you check the value at following address location in CCS memory watch window and let us know.

0x380090
0x0880 to 0x0885

Regards,

Vivek Singh

Hi Vivek,

Using the CCS Flash Plugin, we get this error (same error for all the sectors, from A to H):
C28xx: Erasing Flash memory...
C28xx: Flash Programmer: Error erasing flash memory. Error erasing Sector A

Here is the memory content :
0x000880 = 0x006B
0x000881 = 0x080F
0x000882 = 0x00EF
0x000883 = 0x0001
0x000884 = 0x0100
0x000885 = 0x00FF
0x000886 = 0xFFFF
0x000887 = 0xFFFF
0x000888 = 0x02EF

0x380090 = 0x0000

Thanks for your help,
Regards,
Marie

Hi,

Value @address location 0x380090 is not correct. This location has the PARTID info hence you are getting the error/warning ( "The configured device (TMS320F28335), does not match the detected device ()).

Not sure why this has happen. I'll check with out flash expert and get back to you.

Regards,

Vivek Singh

Can you also let us know the value from 0x380080 to 0x38008F on this device.

Hi Vivek,

Thanks for your help. I'll wait hoping that you'll find a solution for us.

Regards,
Marie

I hadn't seen you're last message.
Here is the content of the addresses :
0x380080 = 0x0000
0x380081 = 0x0000
0x380082 = 0x0000
0x380083 = 0x0000
0x380084 = 0x0000
0x380085 = 0x0000
0x380086 = 0x0000
0x380087 = 0x0000
0x380088 = 0x0000
0x380089 = ----
0x38008A = ----
0x38008B = ----
0x38008C = ----
0x38008D = ----
0x38008E = ----
0x38008F = ----
0x380090 = 0x0000

Thanks for your help,
Regards,
Marie

Marie,

Could you please take a photograph of the top-side of the device (that shows the part number etc) and send it? In how many devices have you seen this issue?

Hi Hareesh,

Here is the photograph of the out-of-service device.

This is the only one that is not working anymore.

It happens while we were programming it and Code Composer crashed.

Since then, it is impossible to write againt in the flash memory.

Thanks for your help,

Regards,

Marie

Hi Marie,

Good to know that you have problem with just one device. Could you check the value in flash at locations 0x33FFF8 to 0x33FFFF via CCS memory watch window and let us know. It'll good if you could post the CCS memory view snap-shot.

Regards,

Vivek Singh

Hi Vivek,

Here are the values in flash from 0x33FFF8 to 0x33FFFF.

Thanks for your help,

Regards,

Marie

Thanks Marie. Could you also post photograph of the top-side of the working device.

Regards,

Vivek Singh

Indeed we have another device with exactly the same things on the top-side, that is working well.

I'm sure that the "not-working" device is not working since Code Composer crashed.
And I don't think that it is a defect in the device.

Are you thinking that it is a problem in the hardware and trying to find the cause ? Or are you trying to find us a solution to repair the "not working" device ?

Thanks for your help,
Regards,
Marie

Hi Marie,

Yes, we were trying to understand if there is some defect in the device which does not seem to be the case. Now it look like the OTP (One Time Programmable) Flash got cleared due to some issue during flash operation. Such error can not be recovered and you have to replace the part on the board for this.

Regards,

Vivek Singh

Hi Vivek,

I feared that it was not possible to do something else than changing the device...
But it is not so easy.

What we fear also is that it happens again. Indeed, Code Composer crashed and it is something that happens sometimes.
How can we be sure it won't happen again?

Thanks for your help,
Regards,
Marie

Hi Marie,

This did not happen just because of CCS crashing. It look like CCS crashed because of power supply issue which must have impacted the device OTP content.

Regards,

Vivek Singh

Hi Vivek,

It seems so strange that there were a power supply issue as we are using stabilized power supply.
Is there a way to know what happens ?

Thanks for your help,
Regards,
Marie

Hi Marie,

It's very difficult to back track how these locations got clear. Do you know which activity caused CCS to crash ?

Regards,

Vivek Singh

Hi Vivek,

We wasn't doing something special : only using Code Composer to write a program in flash memory with the command "Run -> Load -> Load Program...".

That's why we are not confident for next writings.

Thanks for your help,

Best regards,

Marie

Hi Marie,

Sorry for late reply. If you want, you could send us the device which has issue to check but we can not guarantee that we would be able to root-cause the issue.

Regards,

Vivek Singh

Hi Vivek,

Thanks for your proposal but we are not even sure that we will change it.
 We'll just use another board which is working.

If this happens again, we'll tell you and probably make some more investigations.

Thanks for your help,

Best regards,

Marie

Ok, thanks !!

Hi Marie, I am closing this thread. If you see this issue again, please re-open it or start a new post.