• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 1309 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.

Original question:

TMS570LS0714: Lifetime of FEE on TMS570 chip?Is there any algorithm to make it equally used?

TMS570LC4357: Lifetime of the EEPROM of TMS570LC4357

Seungyong Jun
Prodigy 30 points
Part Number: TMS570LC4357

Dear manager,

I am using TMS570LC4357 for developing motor controller.

I have already read this thread https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/646227/2377225.

But I still have some questions about lifetime of the EEPROM and FEE functions.

From the TMS570LC4357 datasheet, the maximum of the write/erase cycle is 100,000.

Q1)

If I configured the size of Block1 as 256 Bytes and write/erase on only 8 bytes memory address, how does it effect on the lifetime of memory?

For example, If I configured FEE blocks like this:

 Then, If I use the FEE write function like this:

uint8 temp_front[8]={0, };

TI_Fee_WriteAsync(0x1, &temp_front[0]);

As the result of these, are only 8 bytes of the lifetime of memory affected?

It means that the maximum of lifetime can be  32 * 100,000 in FEE Block1?

Q2)

If I use writing/erasing on Fee Block1, Block2, Block3, and Block 4 Sequentially, does lifetime of the memory affect on block by block?

Can it be 4 * 100,000? 

Best Regards

  • 0
    TI__Guru**** 196776 points

    Hello Seungyong,

    1. The FEE is only erasable by sector. The FEE Flash bank is divided into two or more Virtual Sectors. Each Virtual Sector is further partitioned into several Data Blocks (4 in your example). A minimum of two Virtual Sectors are required for Flash EEPROM emulation.

    The data is written to the first empty location in the Active Virtual Sector. If there is insufficient space in the current Virtual Sector to update the data, it switches over to the next Virtual Sector and copies all the valid data from the other Data Blocks in the current Virtual Sector to the new one. After copying all the valid data, the current Virtual Sector is marked as ready for erase and the new one is marked as Active Virtual Sector. Any new data is now written into the new Active Virtual Sector and the Virtual Sector which is marked as ready for erase will be erased in background.

    Although the data size is smaller than the block size, the whole data block is written. Smaller data size doesn't affect the number of erase. The number of erase depends on the number of blocks and the size of blocks. 

    If you reduce the block size to 8 bytes (data size is only 8 bytes), the number erase will be decreased.

    2. The lifetime is 100K write/erase cycles. The smaller the blocks or the less the block, the less the FEE sector is erased, the longer the flash life.