TMS320F280x SDFlash Programming Utilities
F280x SDFlash Algo V1.1
Texas Instruments Inc. 24
9.3.6. While the test runs, monitor the selected pin using an oscilloscope. If the algorithms are configured
correctly for your CPU rate then the pin will toggle near 10kHz (100
µ
S +/- 10
µ
S cycle time).
If the pin is toggling at a different rate, then the algorithms are not configured correctly. Follow the
instructions detailed in section 7,
10. Depletion Recovery Algorithm
This release of the SDFlash utilities includes a depletion recovery algorithm. This algorithm is called instead of
erase for the following projects:
SampleF2808_DepRecover.sdp,
SampleF2806_DepRecover.sdp,
SampleF2802_DepRecover.sdp, and
SampleF2801_DepRecover.sdp projects.
Note: These sample projects are setup for depletion recovery only and do not contain code to perform a program or
verify operation. Thus, these operations will report a failure but do not perform any operation on the device.
How does depletion occur?
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. All efforts should be taken to not stop the erase algorithm as
this can also affect the CSM passwords. If the passwords are in an unknown state then the device cannot be
recovered. If, however, the CSM passwords are known and the device can be unlocked, then the depletion
recovery algorithm can be run to try and recover the part.
The depletion recovery algo 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 a time period that is acceptable.
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.
