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: 1532

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 12490 points
    Have you tried using a logic analyzer to see what happens? Or tried using breakpoints and debugging to see where it breaks?

    Jesu
  • In reply to Jesu:

    Hi

    Yes i tried with breakpoints

    When i run step by step all work fine

    Regards

  • In reply to harizi louison:

    Harizi - 

    I can see the i2c.c file in the SDK here ==> C:\ti\CC3200SDK_1.1.0\cc3200-sdk\driverlib can you check that with the locate file button?

    we also have updated the SDK twice since that release - if you would like to update or get the v1.1 again, please visit here ==> 

    BR-

    Josh

  • In reply to Josh Wyatt:

    hi guys

    Thank for your reply.

    After your answer i updated my sdk version from 1.1 to 1.3 but the result stay the same.

    When i run the program, leds and sensors (on I2C too) work fine but after few minutes the problem happens again.

    I tryed to run my code for the leds in the I2C demo from the CC3200 SDK 1.3, it worked perfectly.

    thank for the help

    regards
  • Genius 12490 points

    In reply to harizi louison:

    Hi Harizi,

    Does the i2cdemo example work for the sensors too or is that the only device giving you problems?

    Jesu
  • In reply to Jesu:

    Hi Jesu,

    I'm an Harizi's co-worker.

    In the project, there is 2 tasks with I2C transmission. One for the sensors measurement and the second one to drive LED with an PCA9685.

    When we only active the sensor task, the I2C transmission works fine (over a night).
    but we have the issue with the LED task (illustrate in the first post).

    We implemented the PCA commands in the I2CDemo to be sure that our commands are good and drive the LED as expected. Thats's the case.

    If you have any idea of something to check ?

    Best regards
    Michaël
  • Genius 12490 points

    In reply to m.rabla:

    Hi Michael,

    From your description it seems like more of an RTOS problem than it is an I2C problem. How are your tasks running?

    Jesu
  • In reply to Jesu:

    Jesu,

    In ROV view, the BIOS don't detect any bug,
    The task "Led" (task with the lowest priority in the project) is in running mode and every other tasks are blocked waiting for semaphore.

    The Led task is the lowest priority task because it's only for LED animations (blink, breath effect,...) to inform the user. So it's not critical versus Wifi/BLE tasks.

    So, nothing weird for me.

    Michaël
  • Genius 12490 points

    In reply to m.rabla:

    Hi Michael,

    Just to make sure you're not having a scheduling problem could you make the LED task higher priority than the sensor task? The idea is if the LED task starts working then it's a scheduling problem.

    Jesu
  • In reply to Jesu:

    Hi Jesu

    We tried to disable the sensor task and ran the program with the led task but everytime we get the same issue that in the first post.

    The program is stuck in an I2C function as you can see in the screenshot below.

    The LED task remaining is the only one to use I2C communication so i don't think it.

    Best regards.

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.