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.

  • TI Thinks Resolved

CC3200: I2C communication problem

Prodigy 220 points

Replies: 35

Views: 1448

Part Number: CC3200

Hi 

i currently work on a cc3200 module and i try to use I2C bus to pilot some LEDs

It work perfectly during one or two minutes then the program block in I2C write function. you can see it here :

tank for help

regards

  • Genius 10460 points

    In reply to harizi louison:

    Hello,

    Have you tried to debug your software further to figure out what exactly in the LoadBleFiCfg function causes the I2C to fail? I'm not familiar with the blefi example but if possible, start commenting parts of the LoadBleFiCfg to find the point of failure. The idea is, I doubt a simple function call is going to break I2C, this function must be doing something that causes it to fail.

    To Jan's point, it may still be a HW issue where once Bluetooth is configured and ready, it interferes with I2C or it may be actually be a SW issue where it's overriding some setting or causing a scheduling problem.

    Jesu
  • Genius 10460 points

    In reply to harizi louison:

    Hello,

    I'm going to close this thread due to inactivity. Feel free to respond if you have anymore questions.

    Jesu
  • In reply to Jesu:

    Hi,

    We can't try your method cause LoadBleFiCfg function simply load or create then load a configuration file so nothing in this function break I2C directly.
    We also try to run the program with a deported PCA9685PW (LED driver) but the result is the same.

    The other I2C slave, SI7020-A20-GM1 (Temperature Sensor), work fine everytime so I don't think that is a hardware problem.


    Regards
  • Genius 10460 points

    In reply to harizi louison:

    Could you think of any pins or peripherals the blefi function may be using that causes your problem? Maybe there is overlapping somewhere?

    Jesu
  • In reply to Jesu:

    Hi jesu,

    We found the cause and the solution of our problem.

    CC3200 was stuck in the loop waiting for the ACK from PCA 9685.

    Our guess is something happens and delays the CC3200 for the I2C transaction.

    So we put the I2C task priority to the top, and now it's works.

    Wifi and Bluetooth transmissions are still working and the prototype is running since 72 hours without interruption.

    Thanks for the help.

    Best regards,

    Michaël

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.