• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 190 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.

LAUNCHXL-F2800137: I2C Clock not working

Hans Tschohl
Prodigy 40 points

Part Number: LAUNCHXL-F2800137
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Hi, 

I'm trying to set up an i2c communication. I set it up using sysconfig and want to see that the signals are being set - Im testing the signal out with an osciliscope since I dont have a slave device yet. My issue is that the clock signal stays on LOW and I dont know why. However, my SDA signal does switch from LOW to HIGH but then stays on HIGH (I assume it is because i dont have a slave device attatched and there is nn ACK signal received.)

I have tested the hardware and the pins work. I tried using other I2C pins and that didnt help either. 

Any help or advice would be greatly appreciated. Thanks in advance.

Here is my sysconfig set up:

image.png

  • 0
    TI__Mastermind 22631 points

    Hi Hans,

    Since you don't have a target I2C device, I recommend to leverage the I2C example in our C2000WARE SDK which directly configures a sample I2C module, this can allow you to play around with the settings and see how that affects the I2C module on the C2000 device. When the clock is pulled low, this typically indicates a clock stretching event, but can also be due to C2000 being stuck in some software routine

    Regards,

    Peter

  • 0
    Prodigy 40 points

    Found out what the problem was - my PinMux Pin Type was set to Open Drain but i didnt have an external pull-up resistor so the line was just left floting, which was seen as LOW by my i2C logic analyser program I was using. I changed the settings to Push-Pull output / pull-up enabled on input. 

  • 0 in reply to Peter Luong
    Prodigy 40 points

    Thanks for the advice Peter. I found the problem.