• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 276 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.

I2C0 on OMAPL138

Boris Ruvinsky
Expert 1410 points
Other Parts Discussed in Thread: OMAPL138, TPS65070

Dear E2E:

Thank you for your help.

We use TPS65070 with OMAPL138 in our avionics system.

In general everything is working OK.

But sometimes after several hours of normal operation - I2C interface between OMAPL138 and TPS65070 gets locked up.

The normal operation can be continued only after OMAPL138 reset.

I checked the latest OMAPL138 Errata - there is nothing about I2C0 interface.

TPS65070 has no Errata on this matter.

Do you know - what can cause I2C0 lock-up on OMAPL138?

Do you know if somebody else experienced the same problem with I2C0 interface between OMAPL138 and TPS65070?

Thank you for your help,

Boris Ruvinsky 

  • 0
    Guru 26430 points

    Not sure I can help. I'll ask the obvious questions.

    - SCL speed? Pullup values? Waveforms look "good"?
    - What is meant by locked up?
    - State of the SCL and SDA lines after locked up?
    - Check to see if the TPS65070 is holding down the bus. Can the TPS65070 be reset independently of the OMAP? Can the TPS65070 be disconnected from the bus?
    - Can the OMAP do anything with the SCL and SDA lines after locked up? Not a blip?

  • 0
    TI__Guru*** 125430 points

    Boris Ruvinsky said:
    Do you know - what can cause I2C0 lock-up on OMAPL138?

    I think at a minimum we'd need to know the state of the I2C bus as well as see a register dump after the bus is locked up.  It would also be good to know what happened on the bus immediately prior to the lockup if it's possible to capture that info.