mraa i2c read IOError Connection timed out about meta-iot2000 HOT 4 CLOSED

Sounds a bit like the targeted device (0x1d or 0x28?) is getting angry and blocks the bus afterwards.

You can test if i2c communication works via mraa's python binding in general by talking to that AT24 EEPROM at 0x54.

from meta-iot2000.

Is this issue still persisting?

from meta-iot2000.

Hello,

Reading 300 bytes from 0x54 is no problem. Seems to be related to the BNO055 device that I’m using.

Thank you for your help! :)

from meta-iot2000.

Sorry to necropost, but I am facing the same issue with a BMP280 sensor.

I can read a single byte from a register without issue but, like mrlowalowa, multiple byte reads causes the bus to block and needs a reboot to fix. I suspect this may be due to an inappropriate I2C bus speed for these sensors.

I verified that the same sensor works on Arduino and Raspberry Pi, whose I2C buses default to (or can be set to) standard mode (100 kbits/s), whereas I believe that the IoT2000's bus defaults to fast mode (400 kbits/s).

On the IoT2020 If instead of using the mraa function for reading multiple bytes, I instead call the single byte read multiple times I get all the data back and the bus stays up. Since this method is slower than the multiple byte in one read method, it follows that the bus speed is too high for this sensor.

Is there any way to adjust the I2C bus speed on the IoT2020? I checked the mraa documentation for galileo but the IoT2020 does not appear to be using the same driver for the I2C chip.

I also have a thread running on the Siemens IoT2000 forum with additional test results.

from meta-iot2000.