Hi William, Thanks for writing back. I haven't resolved it, no. I can't find any info about the proper device tree in the BBG documentation. Do you know where I could find one that includes the grove connector busses?
Ben On Sunday, October 18, 2015 at 12:10:59 PM UTC-6, William Hermans wrote: > > Hi Ben, > > Have you resolved your issue yet ? Personally I have not used I2C on any > Beaglebone yet. However I thought I might mention that for most ( perhaps > all ) devices of this nature on the Beaglebone's you need to load a device > tree file, which in turn often loads needed kernel module drivers, sets the > pins up, etc. > > On Fri, Oct 16, 2015 at 10:12 AM, Ben Shapiro <[email protected] > <javascript:>> wrote: > >> (apologies if this is a double-post... my first submission does not seem >> to have gone through) >> >> Hi, >> >> I've been having a hell of a time getting the BeagleBone Green to see >> Grove devices connected to it. >> >> Running i2cdetect -r 0 results in the following output regardless of >> which Grove sensors are connected: >> >> # i2cdetect -r 0 >> WARNING! This program can confuse your I2C bus, cause data loss and worse! >> I will probe file /dev/i2c-0 using read byte commands. >> I will probe address range 0x03-0x77. >> Continue? [Y/n] y >> 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: -- -- -- -- -- -- -- -- >> >> Similarly, i2cdetect -r 1 always results in the following output: >> >> # i2cdetect -r 1 >> WARNING! This program can confuse your I2C bus, cause data loss and worse! >> I will probe file /dev/i2c-1 using read byte commands. >> I will probe address range 0x03-0x77. >> Continue? [Y/n] y >> 0 1 2 3 4 5 6 7 8 9 a b c d e f >> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- >> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- >> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 70: -- -- -- -- -- -- -- -- >> >> I tried reflashing my board with the 2015-07-28 eMMC Flasher (console) >> image. My current uname -a output is: Linux greenbone 3.8.13-bone72 #1 >> SMP Tue Jun 16 21:36:04 UTC 2015 armv7l GNU/Linux. >> However, flashing did not help. >> >> I also tried on a second board. Same problem. >> The BBG Alarm System code >> <https://github.com/Lee-Kevin/BBG_Alarm_system_IoT> posted on the BBG >> product page also will not run. >> >> Am I doing something wrong? >> >> Thank you, >> Ben >> >> >> >> >> -- >> 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] <javascript:>. >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
