• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 117 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 Held LOW after 3rd message

Hans Tschohl
Prodigy 40 points

Part Number: LAUNCHXL-F2800137

Hi, 

I need some help. I'm still relatively new when it comes to i2c communication. I have the understanding that the SCL and the SDA are held HIGH if the bus is ready for a device to start communication. However, my bus is high but the function "I2C_isBusBusy(myI2C0_BASE); " returns that the bus is busy. I double checked the registers and the BB bit is at 0x1. 

I measured the lines using a saleae logic analyser and both lines are HIGH. So the BB bit in the register should be 0x0, right? 

Does anyone know why the bus could possibly be seen as busy? can anyone help? 
 
Best, 
Hans
 
PS. Here is a picture that might help understand my problem. I am using FIFO mode and using a timer to poll the i2c bus every 10ms. 
 
Screenshot 2026-03-19 075052.png
  • 0
    Prodigy 40 points

    RxFIFO was receiving the transfered bytes but was never flushed. Not sure why it was receiving the data that the same device was being transfered - loopback mode was disabled. However, I solved it by flushing the FIFOs.