CC2650: I2C communication problem. I get Interrupt and random I2C transfer in my Logic Analyzer

TOUSSAINT Steven

Part Number: CC2650

Hello,

I'm having problem with my I2C communication. I'm working with a CC2650, a XDS110, and a MAX30101 sensor.

I tested each one of my I2C function one by one and they all works fine, but when I normally launch my program, after that I enable the LED of the MAX30101, I receive an interruption and other random I2C communication every 200ms.

I don't receive it in my program, so it doesn't activate my event, but when I receive the good interruption event, and I check the interruption status, it returns me 0. I guess it's because It's already read by the random I2C communication but, in my program, I don't read it before.

As we can see, I first Init the oximeter, then I enable the LED. And after that enable, it checks the interrupt status and read the FIFO but it shouldn't, since I don't get any interrupt status on my program.

Thanks for your help,

over 6 years ago

0 Alexis Crandall20 over 6 years ago

TI__Genius 15590 points

Hi Toussaint,

According to the change log for the latest SDK(http://software-dl.ti.com/simplelink/esd/simplelink_cc13x2_26x2_sdk/3.10.01.11/exports/changelog.html), there is a known issue where I2C_transfer() occasionally fails when called from an interrupt context. This may be what is causing your issue.

Thanks,

Alexis

0 TOUSSAINT Steven over 6 years ago in reply to Alexis Crandall20

Prodigy 130 points

Hello,

In fact we're not using this SDK. We're using the ble_cc26xx_2_01_01 sdk.

The fact is we didn't have this problem with MAX30100 and sometime we resolve the problem, but when we plug again the cards it starts again doing wrong I2C communication.

Thanks,

Steven

0 J Lindh over 6 years ago in reply to TOUSSAINT Steven

TI__Guru 57865 points

Hi Steven,

But the fact still remains that there seem to be an issue with the driver, are you saying that the symptoms doesn't match?

0 TOUSSAINT Steven over 6 years ago in reply to J Lindh

Prodigy 130 points

Hello,

I don't think that matches because it happens by phase. When it happens, it does for a while, and when it works fine, it works for a while too.

I didn't identify exactly when the state may change.

Furthermore, like I said, I din't have any problem with the MAX30100 whereas it was the same driver/SDK.

Thanks for your help !

Regards,

Steven.

0 J Lindh over 6 years ago in reply to TOUSSAINT Steven

TI__Guru 57865 points

Hi,

To be frank, I am not sure what is going on. Are you running any BLE operations as the same time?

0 TOUSSAINT Steven over 6 years ago in reply to J Lindh

Prodigy 130 points

Hi,

We resolved the problem. We realized that something was sending those I2C communication in the MAX30101 hardware.

So, sorry for asking there since it wasn't a problem in your product.

Anyway, thanks for your time !

Regards,

Steven

Bluetooth®︎

Bluetooth forum

CC2650: I2C communication problem. I get Interrupt and random I2C transfer in my Logic Analyzer