So random potentially-not-helpful-but-maybe-so advice: UUs indicate that the kernel is using that address, via some module. So, on your BBB perhaps it's a cape and the module was loaded? UUs I think, don't necessarily guarantee you have a device there, just that kernel has loaded a module that's claimed that address (I might be wrong on this).
But presumably, by "work" you mean that the i2c device (what is it?) actually works on the BBB besides just showing up? Also, maybe check a different i2c bus? i.e. do i2c-detect on -r 1/2 etc... On Thu, Feb 18, 2016 at 12:21 AM, davidj <sa...@orion-fire.com.au> wrote: > > I started working with the Exadler DMCC and a Beaglebone Black for a motor > control application and it is working OK. I bought some BBG's as they are > neater for what I am doing (we don't need a power connector or HDMI) but the > I2C won't work. There are actually 2 I2C boards added to the BBB. I2C > detects them on the BBB but not the BBG. > > The results for i2cdetect are below. I have tried mutliple BBG's with the > same result. > > Working unit (Beaglebone black) > > root@beaglebone:/Development/BBBB# i2cdetect -r 0 > > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- > > 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- > > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 70: UU -- -- -- -- -- -- -- > > > > > The one that won’t work (Beaglebone Green) > > root@beaglebone:/Development/BBBB# i2cdetect -r 0 > > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- > > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 70: -- -- -- -- -- -- -- -- > > > Does any one have any suggestions for the cause? > > -- > 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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
