I've been also been trying to use I2C with some example provided by intel for use with the mraa lib.

With the hint above, I can initialize the I2C, but as soon as I try some call like WriteByte, it fails with "mraa::ERROR_INVALID_HANDLE" by the mraa lib.

Anyone got the I2C working with the mraa lib and C++?

Is this maybe linked to the warning coming up on connecting the device:

"The selected target does not match the requirements of the launched project .... This can lead to unexpected behavoir. Do you want to continue?"

Synching libraries with the target (IOT2000) isn't working either...

------------------------------------------------------------------------------------------
Split from I2C and SPI using C++ or Arduino IDE Not working.

Problem solved.

It's not a real bug, but some kind of problematic:

I had a broken wire, so my device could not ACK the communication coming from the IOT.

Now the "problem" which resulted from that broken wire:

The MRAA lib uses a enum for its retuned results. The I2C-part of the mraa uses ioctl to communicate with the I2C-Module of the SoC. ioctl returns value "5" in case the communication fails (here because of broken wire). mraa lib just does a cast and returns the value then without any further check. And since "5"=Invalid handle in the result enum of the mraa this leads to the misleading return values.

BTW: I would pin the hint with the "modprobe i2c-dev" as a hot topic, since this can cost time  searching problems in the code were none are.

bergmanu

The upcoming warning should be a reason for this.

 Can you specifiy what you mean by this ?

By the way: Did you report this issue on github? I mean at the mraa project?

https://github.com/intel-iot-devkit/mraa/issues