If you are successfully sending I2C commands, then everything is hooked up correctly, and the device tree is properly configured.
I2C is a bi-directional bus. If it works in one direction, then it has to work in the other direction down at the hardware level. How are you "reading" the I2C devices? What app or tool? or what program in what language? --- Graham == On Thursday, May 11, 2017 at 11:44:40 AM UTC-5, Torsten K. wrote: > > > Hi, > > two weeks ago I received my BeagleBone Blue. > > So far, I've managed to get > > - an OrangeRX DSMX receiver > - a GP-735T GPS receiver > - a Servo > - and a 2S LiPo Akku > > going, more or less without any problems. > > However, all the I²C devices I connected to the available I²C bus #1 so > far only work "one-way". I.e., I can send data to the devices and they do > what they are supposed to, but I can't seem to get any data from a device > to the BBBlue. > > E.g., I've got a I²C DC motor controller (with more juice than the builtin > one). > I can set my motors spinning, braking, reversing, ... using this > controller, but I can't get any status information back from the device. > > I already swapped all cables (and measured them) - they seem to be okay. > > Can it have something to do with the I²C-settings in the dtb? How does > u-boot select the right dtb anyway? > > Thanks in advance, > 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/c44175f3-689a-4771-baf6-e1c8e605fb07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
