TMS320F28069: Cannot erase flash

Regi,

Your part is in depletion. If the depletion recovery step fails then replacement is the only option.

How does depletion occur?

A: If the erase operation is interrupted and not allowed to complete, the device may become depleted. When this happens, the device may then begin to fail to erase. The erase algorithm should not be stopped, as this can also affect the CSM passwords. The Flash API has a depletion recovery function to try to recover flash that has been "over-erased". If the flash programming process was interrupted during the erase stage, it is possible that the timed loops that do the erasing process were disturbed.

The CCS On Chip Flash Programmer does have support for the depletion recovery function. You will see it listed in the as one of the options that can be selected under "Operations" in the flash plug-in GUI. You can get additional information on this by clicking on the "Help" button, go to the search tab and enter "depletion".

The depletion recovery also looks for sectors that are in depletion and attempts to recover them. All sectors on the device are checked.

The current maximum timeout for the algorithm is approx 35 seconds per sector that is in depletion. Typically, only one sector would be in depletion unless erase has been called multiple times on multiple sectors without running to completion. If a longer timeout can be tolerated, the depletion recovery can be used multiple times.

There is no guarantee that this algorithm will be able to bring a sector out of depletion within a reasonable amount of time. The deeper in depletion the part is, the longer it will take to recover. The Flash API erase function has been implemented to erase the flash in such a manner that it is not put into deep depletion. However, if the CPU is halted during an erase pulse for a long period of time, the part can be put into a deep depletion that may not be recoverable in an acceptable time period.

This algorithm cannot recover the part if the flash passwords are unknown. For example, if power is lost during the erase of sector A, where the CSM passwords are located, then the device may be permanently locked and the recovery algorithm cannot operate on the flash.

Regards,

Manoj

5 cards ruined so far. I did not find any voltages out of spec or glitches during flash erase.

I found this example in the utils folders:

//###########################################################################
//
// FILE: Example_Flash2806x_API.c
//
// TITLE: F28069 Flash API Example
//
// NOTE: This example runs from Flash. First program the example
// into flash. The code will then copy the API's to RAM and
// modify the flash.
//
//
//###########################################################################
// $TI Release: F2806x Flash API Release V1.00 $
// $Release Date: MArch 31, 2011 $

I hoped for better results but again the Flash_Erase depletes my flash.

// SECTORA-SECTORH are defined in Flash2806x_API_Library.h
Status = Flash_Erase((SECTORB|SECTORC),&FlashStatus);
if(Status != STATUS_SUCCESS)
{
Example_Error(Status);
}

It returns that sector B is the first failed address. checking sector B its all F's. not sure why that is a problem.

is there any alternative to using this flashAPI. i need to get this working.

Previously, I have tried to erase depleted cards using uni-flash and it reports the exact same error.

On your recommendation...

I have a new non-isolated control card. I used uni-flash to erase the part and it was successful. 

I will review the document carefully.

I have attempted to limit the erase to one sector (sector B) and it resulted in the depletion as well. Also strangely, it returned that the first problem sector was sector G.

I am using both windows CCS 7 and Linux CCS 6.2 systems with the same results.

 Perhaps someone could run the example to confirm there are no issues then send it to me to run. 

Thanks

This morning I ran the newest version after verifying the timing was correct and i did work with out error.

I assume the latest version did the trick for me.

I appreciate the help with it.

Is there a change log i can review, Id like to know what was happening. The clock settings int he old version were not resulting in the correct timing.