/dts-v1/;
/plugin/;
/ {
    compatible = "ti,beaglebone", "ti,beaglebone-black";
    /* identification */
    part-number = "BB-I2C2";
    version = "00A0";
    /* state the resources this cape uses */
    exclusive-use =
        /* the pin header uses */
        "P9.20",     /* i2c2_sda */
        "P9.19",     /* i2c2_scl */
        /* the hardware ip uses */
        "i2c2";
    fragment@0 {
        target = <&am33xx_pinmux>;
        __overlay__ {
            bb_i2c2_pins: pinmux_bb_i2c2_pins {
                pinctrl-single,pins = <
                    0x178 0x73   // spi0_d1.i2c2_sda,  SLEWCTRL_SLOW |                                  // INPUT_PULLUP | MODE3
                    0x17c 0x73   // spi0_cs0.i2c2_scl, SLEWCTRL_SLOW |                                  // INPUT_PULLUP | MODE3
                >;
            };
        };
    };
    fragment@1 {
        target = <&i2c2>;   /* i2c2 is numbered correctly */
        __overlay__ {
            status = "okay";
            pinctrl-names = "default";
            pinctrl-0 = <&bb_i2c2_pins>;
            /* this is the configuration part */
            clock-frequency = <400000>;
            #address-cells = <1>;
            #size-cells = <0>;
        };
    };
};
--
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/groups/opt_out.
Hi all. Can you guys help me.I am using beaglebone black i2c2 pin 19 and 20 of p9. Somewhere in the net it was told i2c2 has told accessed with i2c-1 in /dev folder. I am booting default amstrom linux from emmc. Hardware is completely checked and verified. I have connected 3 io expansion modules to i2c bus. I can communicate to them by i2ctest commands from command line. But the problem is with the file writes. I cant write to /dev/i2c-1 file with "write" function. The file descriptor doeant have an error. Also the ioctl calls doest make any errors. But the write function is having problem. And thus I cant access i2c bus in application layer.
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/vbuM-4oShS8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
i2cdetect -r -y 1
   0 1 2 3 4 5 6 7 8 9 a b c d e f
00:Â Â Â Â Â -- -- -- -- -- -- -- -- -- -- -- -- --Â
10: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --Â
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --Â
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --Â
40: -- -- -- -- -- -- -- -- -- -- -- -- 4c 4d -- --Â
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --Â
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --Â
No size specified (using byte-data access)
   0 1 2 3 4 5 6 7 8 9 a b c d e f  0123456789abcdef
00: 00 00 00 00 11 31 00 00 20 00 00 01 7c 10 00 00Â Â ....?1.. ..?|?..
10: 00 00 00 10 00 10 00 00 01 00 80 01 0f 03 07 04Â Â ...?.?..?.??????
20: 00 00 00 04 00 08 f3 04 13 00 11 1f 00 00 00 00Â Â ...?.????.??....
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 30 30 22Â Â .............00"
40: 02 04 14 05 00 00 00 00 55 00 00 00 00 00 00 00Â Â ????....U.......
50: 00 00 00 00 00 07 00 00 81 00 00 00 00 40 78 15Â Â .....?..?....@x?
60: 01 10 00 00 00 01 0f 03 07 11 00 00 00 00 06 03Â Â ??...?????....??
70: 02 83 03 00 04 00 80 01 00 00 00 00 00 00 00 00Â Â ???.?.??........
80: 00 00 00 00 11 31 00 00 20 00 00 01 7c 10 00 00Â Â ....?1.. ..?|?..
90: 00 00 00 10 00 10 00 00 01 00 80 01 0f 03 07 04Â Â ...?.?..?.??????
a0: 00 00 00 04 00 08 f3 04 13 00 11 1f 00 00 00 00Â Â ...?.????.??....
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 30 30 22Â Â .............00"
c0: 02 04 14 05 00 00 00 00 55 00 00 00 00 00 00 00Â Â ????....U.......
d0: 00 00 00 00 00 07 00 00 81 00 00 00 00 40 78 15Â Â .....?..?....@x?
e0: 01 10 00 00 00 01 0f 03 07 11 00 00 00 00 06 03Â Â ??...?????....??
f0: 02 83 03 00 04 00 80 01 00 00 00 00 00 00 00 00Â Â ???.?.??........
Write 0x01 to register 0x14:
i2cset -y 1 0x4c 0x14 0x01
Dump the registers and not the change to 0x01:
i2cdump -y 1 0x4c
No size specified (using byte-data access)
   0 1 2 3 4 5 6 7 8 9 a b c d e f  0123456789abcdef
00: 00 00 00 00 11 31 00 00 20 00 00 01 7c 10 00 00Â Â ....?1.. ..?|?..
10: 00 00 00 10 01 10 00 00 01 00 80 01 0f 03 07 04Â Â ...???..?.??????
20: 00 00 00 04 00 08 f3 04 13 00 11 1f 00 00 00 00Â Â ...?.????.??....
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 30 30 22Â Â .............00"
40: 02 04 14 05 00 00 00 00 55 00 00 00 00 00 00 00Â Â ????....U.......
50: 00 00 00 00 00 07 00 00 81 00 00 00 00 40 78 15Â Â .....?..?....@x?
60: 01 10 00 00 00 01 0f 03 07 11 00 00 00 00 06 03Â Â ??...?????....??
70: 02 83 03 00 04 00 80 01 00 00 00 00 00 00 00 00Â Â ???.?.??........
80: 00 00 00 00 11 31 00 00 20 00 00 01 7c 10 00 00Â Â ....?1.. ..?|?..
90: 00 00 00 10 01 10 00 00 01 00 80 01 0f 03 07 04Â Â ...???..?.??????
a0: 00 00 00 04 00 08 f3 04 13 00 11 1f 00 00 00 00Â Â ...?.????.??....
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 30 30 22Â Â .............00"
c0: 02 04 14 05 00 00 00 00 55 00 00 00 00 00 00 00Â Â ????....U.......
d0: 00 00 00 00 00 07 00 00 81 00 00 00 00 40 78 15Â Â .....?..?....@x?
e0: 01 10 00 00 00 01 0f 03 07 11 00 00 00 00 06 03Â Â ??...?????....??
f0: 02 83 03 00 04 00 80 01 00 00 00 00 00 00 00 00Â Â ???.?.??........
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.