• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 78 subscribers
  • Views 1164 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

EEPROM data corrupt onTMS570LS0332

Abhijeet Mutha1
Prodigy 120 points
Other Parts Discussed in Thread: TMS570LS0332

Hi ,

we are using TMS570Ls0332 in our project , i have stored some data on EEPROM (0xF0201000 to 0xF0201FFF) .

The data on this EEPROM is accessed and updated very frequently by the application program.

Now the problem is that the data on EEPROM is found corrupt some time after System Reset.

please tell me the reason and solution for this problem ASAP.

Thank you.

  • 0
    Guru 74080 points
    What does "updated frequently" mean? And for how long is the device already doing these frequently updates? Maybe you already hit the maximum write endurance?
  • 0 in reply to Dennis Eichmann
    Prodigy 120 points

    Hi Dennis,

    we are updating the EEMPROM data depending upon the status of the Hardware ,on an average we are updating the data 4 ~5 times in a 1 second.

    I am not aware of the term " Maximum write endurance" , can please help me with this.

    Thanks

     

     

  • 0 in reply to Abhijeet Mutha1
    Guru 74080 points

    The memory wears off a bit each time you write data to it. Look in the datasheet:

    On page 49, table 4-21 shows the information for the data flash (your EEPROM):

    It has a write endurance of 100,000 cycles - within these count, TI guarantees a data retention of 15 years. After that the possibility of data corruption / earlier loss of data  rises (of course not instantly, but slowly).

    So if you write new data five times per second, then you will reach the 100,000 cycles within 20,000 seconds, which is about 5 and a half hours. That is quick. So you normally do not save data at the same location all the time. You cycle around different cells to lower their usage. Furthermore you can hold the values in RAM, only saving them when detecting a power loss.

    Dennis

  • 0 in reply to Dennis Eichmann
    Prodigy 120 points
    Thanks for data , but i think this is not the case with my device.

    1) The data is getting updated in 4~5 times in 1 second , but the data is not getting updated every second . As i can see the data is getting 60 ~ 70 time flashed in 1 complete execution.
    So i believe the device has not yet reached 100000 cycle of read/write.

    2) Once the data is corrupt , we connect the device with JTAG and re-flash the binary on the device and device start working fine .
    The data corruption scenario is observed immediately after the System restart . This scenario is observed once or twice in 200 ~ 300 times.

    So i believe the data is getting corrupt due to some other reason , Request you to please suggest the solution.

    Thanks
  • 0 in reply to Abhijeet Mutha1
    Guru 74080 points
    Reading the data is no problem, writing destroys it. When it is corrupt after a system reset, then maybe the write progress is interrupted by the reset and therefore the data is not written completely.

**Attention** This is a public forum