• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 147 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.

LAUNCHXL-CC1310: I2C issue

Nick Sun
Intellectual 2265 points
Part Number: LAUNCHXL-CC1310

Hi team,

Here's the request from the customer:

The I2C can read sensorID and write configure normally, but it blocks at the if (!I2C_transfer(i2cH, &i2cTransaction)) function each time when reading the sensor interrupt status.

Could you help check this case? Thanks.

Best Regards,

Nick    

  • 0
    TI__Expert 4425 points

    Hi Nick,

    Can you please provide more information regarding this issue?

    Does the I2C_transfer function block or does it return false (indicating an error).
    Can you please explain the scenarios where the I2C transaction is successful, and when it is not successful? Please also include more of the code, if possible.
    Can you also explain what I am seeing on the two logic traces? How does it correspond to the code?

    Btw, if you are using the I2C driver in blocking mode, then I2C_transfer() must be called from a task/thread context, it must not be called from an ISR or similar.

    Thanks,
    Nikolaj

  • 0 in reply to Nikolaj_G
    TI__Intellectual 2265 points

    Hi Niklaj_G,

    Here's the respond from the customer.

    1.The I2C_transfer function blocks.

    2.The I2C works nomal when reading the ID, which can read the first set of data from the sensor. Than the interrupt status will block when read data from the sensor again.

    Video is shown in the following figure:

    The i2c Initial configuration is shown in the following figure:

    Best Regards,                                                            

    Nick    

  • 0 in reply to Nick Sun
    TI__Expert 4425 points

    Hello Nick,

     It looks like a CPU Exception has occurred. I don't know what the issue might be.

    Has the customer gone through the entire Deciphering CPU Exceptions chapter in the Users Guide?

    Has the customer inspected the ROV → Hwi → Exception information?

    http://dev.ti.com/tirex/explore/content/simplelink_cc2640r2_sdk_3_20_00_21/docs/blestack/ble_user_guide/html/ble-stack-3.x-guide/debugging-index.html#deciphering-cpu-exceptions 

    Regards,
    Nikolaj