Hi again, Do you have another "trusted" I2C device you could parallel across the bus > as a test device? > I use an MCP9808 temperature sensor on most of my boards when bringing up > a new design. >
I think I'll do that on Monday, when I'm near my Beaglebone again, Or as suggested by David, put a bus analyzer on the bus to see if the chip > is not sending good data, or the Beaglebone is loosing the good data when > the chip sends it. > I've only got a small oscilloscope (1 channel) that probably won't help that much, but I can try. Anyway, I tried i2cget on the two devices connected to the third I²C bus (i2c2) on the Beaglebone Blue. One is the MPU9250, which also works with my Python code. If I ask this device for it's ID, I get a perfectly response: tkurbad@beaglebone:~$ i2cget -y 2 0x68 0x75 0x71 So, I'm more and more under the impression that somethings wrong in the way the second I²C bus (i2c1) is set up. This is the only broken out bus on the Beaglebone Blue, so I don't have a chance but put my motor controller there. So, I'll try another - confirmedly working - device on Monday and report back. Thank you so far and best regards, Torsten -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1d2f2d6c-2432-4cbf-bf25-757df5d2bd0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
