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 lock itself. 4 Cards locked already

Other Parts Discussed in Thread: TMS320F28035, TMDSCNCD28035

Hello,

I've got a major problem with the TMS320F28035. The card is locking itself for no reason.

At first I thought that I had a mistake while programming but now I'm sure that this is not the case. On the last case, my program was working properly, I even made some Pause in debug mode to watch some value ( as always) and it was what exepected. After that I turned it off for 10min, and when I tried to program it again I couldn't.

C28xx: Flash Programmer: Error erasing Flash memory.

This is the message that is showed. I'm using CCS 5.2, and the docking station for the piccolo F2803x (with TMDSCNCD28035).

I bought 5 TMDSCNCD28035 already!! With the fourth gone a few minutes ago I only have one left and there is no more available in Europe.

Please tell me there is a way to unlock the card or an explanation about what could be causing this.

I really need your help! Thank you.

Regards, 

Simon Brethous

  • Is there a limit in the number of time the TMS320F28035 can be programed/Flashed? I think the cards locked around the 500th programming

  • Write cycles guaranteed minimum is 20,000, and should be OK 50,000 times if temperature is normal, say <40 degC.

    I have used same board for an year during development, did programming 5000-7000, without any problem.

    I assume locking happens during programming, chip cannot get locked when it is working normally. Reason could be loose connection between the JTAG pins to emulator. Have you experienced programming/ connection errors while the chip was working? Have you changed the CSM values from blank?

  • Hello,

    Well I see the locking when I try to program again, but I think I sax some strange things during the running just before, like the debug pause for 1s or so. It might be coming from the cable or the docking station but I checked the lack of short-circuit so I can't see where it's coming from...

    Regards,

    Simon Brethous