scanning bus 0 gave the following:
debian@beaglebone:/var/lib/cloud9$ i2cdetect -y -r 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – UU – – – – – – – – – – –
30: – – – – 34 – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: UU – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: UU – – – – – – –
The bus scan from Bus 0 was very fast, that for bus 1 was slow, about 1 address per second.
I also tried to make sure that the pins were set to the right mode with config-pin.
other output from I2cdetect as follows:
debian@beaglebone:/var/lib/cloud9$ i2cdetect -l
i2c-1 i2c OMAP I2C adapter I2C adapter
i2c-2 i2c OMAP I2C adapter I2C adapter
i2c-0 i2c OMAP I2C adapter I2C adapter
debian@beaglebone:/var/lib/cloud9$ i2cdetect -F 1
Functionalities implemented by /dev/i2c-1:
I2C yes
SMBus Quick Command no
SMBus Send Byte yes
SMBus Receive Byte yes
SMBus Write Byte yes
SMBus Read Byte yes
SMBus Write Word yes
SMBus Read Word yes
SMBus Process Call yes
SMBus Block Write yes
SMBus Block Read no
SMBus Block Process Call no
SMBus PEC yes
I2C Block Write yes
I2C Block Read yes
Inspection of pins 19 & 20 with an oscilloscope shows no sign of any activity: both pins are at 3.3V.
scan of bus 2 also gives no result, but completes much faster.
any help much appreciated - looks like I’m missing something…
Thanks Robert,
The RTC chip has now been found - on I2c -2. Not sure why I didn’t think of this before. Now trying to make sure it’s working. /dev folder has rtc, rtc0 and rtc1 listed…