Long story short, I'm 95% sure it's not a hardware problem because I've tried 3 different pie models (RPi B, Banana Pi, and the RPi2 I just bought) and 2 different PicAxe Boards and chips on I2C. Both PicAxes and boards used to be detected, though was only able to bidirectionally communicate the one due to requiring a higher baudrate on the PicAxe chip.
I've worked on it countless hours since Monday. I really need help on getting this working, as I want to use it as part of a home defense system (new property manager thinks that a lease saying he can enter at any time written by a lawyer of another state overrides state laws requiring over 24 hours notice).
My I2C device is a PicAxe 28x2, which as I said used to work. I can still read and write to it well through USB.
To get it working before, I set [ SETFREQ m16 ] which sets the PicAxe I2C frequency to 16MHz.
When I did't have it set at M16, I could see the device listed with i2cdetect, but couldn't communicate bidirectionally.
My PicAxe 28x1 could also be seen by I2C detect, but doesn't have M16 available to communicate properly.
The Pi with upgrades does not see either board when connected.
I enabled I2C and Device Tree from Raspi-Config
I do not have any other I2C devices besides PicAxes and Pis to test.
Code: Select all
snd-bcm2835 i2c-dev i2c-bcm2708
Code: Select all
arm_freq=1000 core_freq=500 sdram_freq=500 over_voltage=2 dtparam=i2c_arm=on
I'm also at wits end enough, that if nobody has a clue what to do here, I'd be willing to download an image with I2C proven to be working, if anyone could make one... which is a big deal, because my DL speed caps at 3mbps where I live.
Thanks, and while I know this was long, I wanted to give all the information on it I could, and still condensed it. XD