As a follow-up, I got I2C working through specifically addressing the chip as specified in the docs, but i2cdetect never, even now, returned accurate information. i2cdetect response such as this (30-37, 50-5f) useless for troubleshooting; does not indicate anything about state of i2c bus.

Thanks to the OP for downvoting my last comment, I hope you downvote this one as well.

As a follow-up, I got I2C working through specifically addressing the chip as specified in the docs, but i2cdetect never, even now, returned accurate information. i2cdetect response such as this (30-37, 50-5f) useless for troubleshooting; does not indicate anything about state of i2c bus.

Thanks to the OP for downvoting my last comment, I hope you downvote this one as well.

Need an easy, effective way to spin up new devices directly after a factory reset from either an SD Card or Serial connection, provisioned to connect to our network with our software already loaded. A simple "dump these files in these locations" would work, but going through setup manually is time consuming for provisioning 3 or 4 omegas, and I need to provision a stack of 20.

@Arshad-Alam said in I2C communication (write/WriteBytes returns None, Readbytes returns 0xff) using pyOnionI2C #I2C #OMEGA2:

RTC chip

Working on i2c interface as well; I get an identical return from i2cdetect for a completely different chip (digital potentiometer). Typically it should just return one address!

I disconnected the i2c wires from the breadboard and still get identical (junk) output, so I'm wondering if it might be an error state? Hardware or software though?