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.

MCF8316AEVM: Sudden I2C communications failure

Part Number: MCF8316AEVM
Other Parts Discussed in Thread: MCF8316A

Dear all,

I purchased an MCF8316AEVM to see whether the MCF8316A would be suitable for use in my application. At some point while experimenting with it, it stopped working. I got the dreaded "There is an issue with the device connectivity. Please restart the GUI." while trying to read or write to the EEPROM. Thinking I had done something stupid (which I really don't think I did), I purchased a second unit. This one failed much quicker than the previous one. The last thing I remember doing before it failed was changing the setting for the IPD current limit, then clearing the motor faults. After I did this I noticed that the IPD startup procedure was taking longer than usual, so I cut power from the external supply (24 V). After the this, the board no longer functions normally.

I decided to have a look on the I2C bus (on both boards) and noticed that the MCF8316A was no longer responding to I2C commands. On the second board that failed, I noticed that the nFAULT LED comes on a fraction of a second after the D1 LED. This suggest to me that the IC is mostly still working, except that it is no longer able to communicate via I2C.

This behavior raises serious concerns to me about the reliability of the MCF8316A part. Please advice. Thank you in advance.