> > *$ ls /lib/firmware/ | grep I2C* > *BB-I2C1-00A0.dtbo* > *BB-I2C1-PCA9685-00A0.dtbo* > > *Looks like, at least for me, I have two I2C device tree overlays which I > can load. One generic I2C, and another which is unfamiliar to me, but seems > to be for a specific device.* >
So thinking about this further, I'm pretty sure if you're using the BBG specific Linux image, there should be a device tree file specifically for the I2C grove connector. Again, I'm not sure how these pins are brought out, and from which I2C peripheral, but it does make sense they have their own device tree file for the I2C grove connector . . . So if you ls /lib/firmware/ there should be a hint as to which device tree file you need to load. Based on the names. On Sun, Oct 18, 2015 at 1:51 PM, William Hermans <yyrk...@gmail.com> wrote: > > *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* >> > > Well, not exactly but . . . First, you need to be aware that every board, > be it Beaglebone black, white, or green all have their own initial device > tree file which is board specific that gets loaded at boot time. > > So if you looks at the /boot/dtbs/`uname -r` . . . > > $ ls /boot/dtbs/`uname -r` |grep green > am335x-bonegreen.dtb > > You should get the same output from the above command. Ok so here I have > to assume once your board has this file loaded at boot. Your board, should > effectively behave like any other Beagelbone. With this in mind if we look > at /lib/firmware/ . . . > > $ ls /lib/firmware/ | grep I2C > BB-I2C1-00A0.dtbo > BB-I2C1-PCA9685-00A0.dtbo > > Looks like, at least for me, I have two I2C device tree overlays which I > can load. One generic I2C, and another which is unfamiliar to me, but seems > to be for a specific device. > > From here you should be able to load the first dtbo file if you have the > same on your board, and be able to use your I2C utilities. Do however keep > in mind that I am completely unfamiliar with the BBG. So I do not know > anything about the grove connectors, how they work, how they're connected > to board, and all that. So before going off half cocked based on what I'm > saying, you should double check what you can. > > But if you have further questions, I'd be glad to help. I do have interest > in the BBG . . . But we already own 5 blacks . . . > > On Sun, Oct 18, 2015 at 12:25 PM, Ben Shapiro <ben.shap...@colorado.edu> > wrote: > >> 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 <ben.s...@colorado.edu> >>> 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 beagleboard...@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. >> > > -- 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.
