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.

TM4C123GE6PZ: Detail Root Cause Description for EEPROM

Part Number: TM4C123GE6PZ


Hi All

In Errata, there are issue list for "EEPROM Data May be Corrupted if an EEPROM Write is Interrupted" and "Device may Become Non-functional if an EEPROM Write or Erase is Interrupted".

Errata describe the issue condition and behavior, Customer want to know more detail about root cause for such issue. Because customer product with using EEPROM already MP and Sale to market, they need more detail information to evaluate the risk and make judgement how to deal MP product.    

  • Hello Terry,

    Before going into those details, can you please verify with the customer they are 100% using Revision 6 silicon?

    This errata does not affect Revision 7 silicon!

    Page 3 of the Errata document outlines how to check for the revision.
  • Hi Ralph

    Yes, the part number in customer device is E6PZI without follow by "7".
  • Hello Terry,

    Thank you for checking.

    Reviewing the errata document and the description provided, it is very clear about the situations that the issue can occur in, so I am a bit unclear on what else we could even provide them.

    The documentation very clearly outlines that the issue can occur for any of the 3 power issues listed, so it is important to avoid those occurrences, and offers workarounds for how to avoid the issue.

    What additional information do they want beyond the detailed description provided which, to me, clearly lists how they can avoid the issue? Keep in mind we have to maintain a level of confidentially as far as the design itself goes so there are limits to what information we can share.
  • Hi Ralph

    If customer develop new product, they must will carefully follow the workaround to avoid the issue situation in Errata description.

    However now customer product already MP and Sale in market, they cannot modify product firmware or hardware to avoid the issue, so they want to know the issue internal root cause, so that they can evaluate risk for example how much percent the product will happen issue.

    Appreciate you can help share some more information if have not the confidentially limitation.
  • Hello Terry,

    I will have to speak with an engineer who was part of the team during the errata discovery if we can share any other information, but he is out of office until next week.
  • Hi Ralph

    Today I discuss with customer, they also want to know what modification we have done in Ver.7 Device to solve such EEPROM issue, they want more confidence to use Ver.7 in future MP PRODUCT. Do you think if we could tell such information? thanks.  

    BTW, if you think necessary, you also could reply the information to me by email terry-deng@ti.com

  • Hello Terry,

    I will send you an email and close this thread, I think it will be easier to have open dialogue offline.