Jump to content
  • 0

I2C Spy weird behaviour


lokobob99

Question

Hello everyone,

 

I'm trying to spy on a I2C communication. For that I'm using a Time-of-Flight Sensor which measures the distance. Now while the arduino code runs perfectly fine and the measurements are shown on the serial monitor, the I2C protocol looks kind of odd and gives me the message, that samples could be lost (see picture). I also include a picture of my arduino code.


Any help would be appreciated!

Kind regards

 

 

EDIT: When I use the SDK example (Digital_I2C_Spy.py) the output looks even more strange

 

image.thumb.png.58b0552ec9eb4ddec3aa92225c2ceed3.png

image.thumb.png.77e46f02fa7445f47d98edcebb7f33b5.png

image.thumb.png.e07a79e7d43400a93cd30dc37352483e.png

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Hi @lokobob99

Probably the average throughput is higher that the device can stream for spying.
With continuous 400kHz I2C transmission it could require up to 3.2MSps but the device supports up to about 2-4MSps depending on the available USB bandwidth, system...
You could use 100kHz I2C (or delay between transfers) to reduce the rate or use the Logic Analyzer with triggering to capture the important events like odd i2c values, NAKs...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...