• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 1116 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

EK-TM4C1294XL (TM4C1294NCPDTI) I2c problem

Don Huntley
Intellectual 300 points

I have code using I2C running perfectly on a TM4C123G Development Board. When I move the same code over to the EK-TM4C129XL, it does not function correctly. The only change in code between the two boards is the change in I2C port number. The EK-TM4C129XL is operating as a master connected to an external slave board. It's behavior is very erratic, so it's difficult to characterize. When viewing (with a scope) a burst write followed by a burst read, I've seen everything from back-to-back slave addresses being written to erratic data being written. The clock rate was verified to be 100KHz. I have tried different I2C ports; different system frequencies; different boards. For the TM4C129, I'm using TivaWare_C_Series-2.1.0.12573. Any advise would be appreciated.

  • 0
    Guru 85655 points

    Don Huntley said:
    The only change in code between the two boards is the change in I2C port number. 

    I think you need more changes that just the I2C port number. There are C API's for TM4C123 that has been changed for TM4C129. Compare, the Tivaware Peripheral Driver Library User's Guide for each kit.

    -kel

  • 0 in reply to Markel Robregado
    Guru 117850 points

    So - might it be that we now enjoy distinct versions of "rebrandware" for each/every rebrand MCU? 

    Perhaps a tad harsh - but we know that the I2C engine's "care/handling" does appear bit different in your "129."  (much of this brought about (we're told) by that new MCU's higher clock rate) 

    TI's "Amit" has rescued several here - I2C issues similar to yours.  (w/your MCU)  Forum search targeting Amit & I2C should steer you there...

    Of course such, "MCU based, code use restrictions" should be far better pronounced, then highlighted and forcefully distributed.  (or - they may be blipped - a la the NMI buried mentions - causing much (perhaps needless) suffering by the less wary...)

    Early adopters of new tech may be recognized by multiple arrows protruding - their soft/tender regions - while a red liquid "bathes" many nearby, fallen sheets - perhaps titled, (squinting now) errata?