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.

TM4C1231H6PZ: an issue about frequently write in TM4C1231H6PZ EEPROM

Part Number: TM4C1231H6PZ

dear all,

when i use TM4C1231H6PZI MCU with frequently data write in EEPROM, it will break down after a long time write. do i need some reset operate? 

In my application, we made about 500 boards and ran after half year customer found that about all TM4C1231H6PZI MCUs can’t work. It isn’t because short issue and not heat on MCU. So I think TM4C1231H6PZI not broken. But the MCU can’t work continue and can’t load program or debug online. We think maybe that is because the MCU be locked, so we tried to unlock it. But then it still not work. 

our application is very easy and the code is not very big. we doubt the issue maybe is because frequently write in EEPROM. In this case, MCU need write the time in a same EEPROM area in every 1 second. So we made a test that more frequently write in a some EEPROM area as 1ms. we found TM4C1231H6PZI EEPROM will can’t be written continue and keep a time all the time. And then TM4C1231H6PZI will can’t work, can’t realize any function and can’t load new code in it. 

what purpose reason for this situation?

thanks a lot. 

  • Damien Zhang said:
    when i use TM4C1231H6PZI MCU with frequently data write in EEPROM, it will break down after a long time write. do i need some reset operate? 

    Once it has failed, it has failed. There is no recovery.

    Damien Zhang said:
    In my application, we made about 500 boards and ran after half year customer found that about all TM4C1231H6PZI MCUs can’t work. It isn’t because short issue and not heat on MCU. So I think TM4C1231H6PZI not broken. But the MCU can’t work continue and can’t load program or debug online. We think maybe that is because the MCU be locked, so we tried to unlock it. But then it still not work. 

    Have you reviewed the errata? There are several important errata, including IIRC some that can brick the micro.

    Damien Zhang said:
    So we made a test that more frequently write in a some EEPROM area as 1ms. we found TM4C1231H6PZI EEPROM will can’t be written continue and keep a time all the time.

    You need to review the specifications. The time required to write to EE is long. The worst case is three orders of magnitude longer than you are attempting to write.

    Damien Zhang said:
    what purpose reason for this situation?

    Start with reading the errata, particularly those related to the EE.

    Robert

    I don't necessarily believe your problem come from just the EE, but you do need to deal with the EE limitations.

  • R.A. "Important safety tip: read the errata!" And - this post from a vendor agent - compounding the miscue...

    Steering the MCU to "Kitchen Sink" (do everything) - rather predictably - leads to such, "performance shortcomings."

    A small, low cost external device - designed/optimized to task - "AVOIDS" the mess - when such "kitchen-sink attempt" springs its (likely) leak!