i2cdetect -y -r 0 is snappy and returns address results in a few milliseconds.
However i2cdetect -y -r 1 takes about three seconds per address!
If I try to read or write to a connected board over i2c I inevitably get ERRNO 110 timeout error.
I have seen multiple other topic entries with similar problem concerning the i2c bus on nano dev boards. All ended up having to go through RMA process.
I am also getting various i2c probe errors on bootup which is concerning, I think the bus is completely corrupted.
Diagnostics
I tried to reflash with a fresh JP4.4 sd card, but the problem persists.
I checked voltage on sda/scl gpio pins which look correct
Questions
Does anyone know why there are so many issues with I2C on nano boards?
Is there a way to recover the i2c bus once it is corrupted? i2cdetect man does not seem to have any cmds regarding restarting the bus itself.
Is there a way I can switch over to using I2C BUS 0 instead of 1 by adjusting the device tree?
Any tips/feedback or suggestions appreciated. cheers
Yes connected PCA9685 PMW Servo Module and cannot probe for address. I tried the same board on a Raspberry Pi and I am able to connect and communicate over I2C just fine.
It appears to specifically be a problem the I2C Bus 1, as mentioned before even the I2C 0 bus is working well on my nano.
Yes, thats why i said strange error. I can check Bus 8 and I am retrieving addresses and everything looks ok.
However, I run into problems when I try to connect anything to Bus 1. I cannot even retrieve addresses on Bus 1.
I have tried connecting PCA9685 16 Channel 12-Bit PWM Servo Motor Drive which connects on Bus1 so it does not work. I connected to a Rasp Pi and it works correctly.
I also have tried to connect he Arducam PTZ board which uses Bus 1. Works on Pi but not on the Nano.
@ShaneCCC Do you have any recommendations on looking into why my Bus 1 is corrupted. Are there certain configuration files I should look at?