On 10/18/2015 05:59 PM, William Hermans wrote:
My best guess is that I2C1 is brought out to the I2C connector, so enabling BB-I2C1-00A0.dtbo should work for you.

On Sun, Oct 18, 2015 at 2:43 PM, Ben Shapiro <[email protected] <mailto:[email protected]>> wrote:

    Sadly, there does not seem to be a BBG-specific image.

<chopped>


                On Fri, Oct 16, 2015 at 10:12 AM, Ben Shapiro
                <[email protected]> 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: -- -- -- -- -- -- -- --


Why do you think that they aren't enabled? The output of i2cdetect -r 1 shows the 4 cape eeprom addresses in use. The output of i2cdetect shows two addresses. How about the output of "dmesg | grep cape" "dmesg | grep i2c" ?

Mike

--
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.

Reply via email to