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: tm4e1231h6zrb no-functional state

Part Number: TM4C1231H6PZ

Dear TI support team,

 

we are experiencing a no functional state on the TM4E1231H6ZRB. The part completely doesn't operate, it's not possible to access the uC. The only feedback is a continuos 15 Hz square waveform on the JTAG TDO pin.

Could you plese give us information is there is a failure mode which results in that kind of behaviuor?

 

Many Thanks,

Lorenzo

  • Hello Lorenzo,

    What is the full part number (I, IR, I7, I7R etc.) of the device you are seeing this issue with? I need to understand which revision of the silicon you are using before I can offer accurate feedback.

    Best Regards,

    Ralph Jacobi

  • Dear Ralph,

    Silicon revision should be 6.

    We see  the issue for the following two p/n: TM4E1231H6ZRBI and TM4E1G31H6ZRBI

    Thanks,

    Lorenzo 

  • Hello Lorenzo,

    Understood. I am going to make an assumption here that you are also using the EEPROM.

    If so, the errata for this device for Revision 6 includes MEM#04 as a condition under which the device can become non-functional.

    If the device becomes non-functional under such a condition, then the 15 Hz TDO output is one of the symptoms observed.

    One other possibility which is less likely but can affect both revisions is MEM#05. The same symptom would be present in that case as well.

    In general if the 15 Hz TDO output is observed, it means the devices has been rendered inoperable and cannot be recovered, so you will need to replace the device.

    Best Regards,

    Ralph Jacobi

  • Hi Ralph,

    Indeed I have already realised I need to replace the device, but I would like to be sure about root cause of that failure mode to avoid my system will be affected again.

    Is there other possibility in addition to MEM#04 and/or MEM#05 which could result into that behaviour?

    Furthermore, I'm currently using the EEPROM, to implement up time counter, is there a way to perform safe writing operation?

    Thanks for the support,

    Lorenzo 

  • Hello Lorenzo,

    I am not aware of any additional known repeated issues that would cause that, but there is always the possibility of a system specific failure such as ESD or overcurrent etc.

    For EEPROM the errata document outlines all possible workarounds.

    Best Regards,

    Ralph Jacobi