• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 408 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.

MCF8316A: IIC Suddenly unable to be communicated

Susan Ren
Prodigy 345 points
Part Number: MCF8316A

Hi Team,

When using the evaluation version of MCF8316AEVM.In the normal situation there is no problem, but when reading motor data, the IIC suddenly appears to be unable to communicate.

Causing the UI software to drop the line, MCF8316 power failure restart will not be restored (the evaluation board above the fat is also normal, there is no light), directly the MCF8316 chip can be removed and replaced, and this phenomenon has appeared two or three times, are forced to change the chip to solve, this problem is very serious, I hope to get an answer.

Thanks,

Susan Ren

  • 0
    TI__Genius 9220 points

    Hi Susan,

    There could be many reasons the device stops responding to I2C communication. So we'll need your help clarifying the details of the failure:

    • The MCF8316A has a known errata #8: Device I2C communication fails when the registers are constantly read during motor operation. However, the device can be restored from this errata via a simple power cycle.
    • After the failure occurs, how much current does the device draw from the Vm power supply compared to a normal device? This could help determine if there was any damage/short in the device.
    • On a failure unit, can you please help measure and confirm the following voltage regulator outputs:
      • Vbk Buck regulator (5V by default)
      • AVDD (expected 3.3V)
      • DVDD (expected 1.5V)
    • Did the customer write to the device's EEPROM? It's possible that the MCF8316A's configurable I2C Target Address was overwritten, requiring the GUI to use a different I2C Target Address to communicate with the device.

    Thanks,
    Eric C.

  • 0
    TI__Mastermind 18981 points

    Hi Susan, 

    Please let us know if further support is needed on this question. Thanks 

    Best Regards, 
    Andrew