> im using fedora 25 on both a rasberrypi2 and a 3 > > I also have a ds1307 in the rasberrypi2 and it works fine. > > however ive tried first a ds1307 in the rasberry pi 3 and now a ds3231 > > neither show up in i2cdetect -y 0 or 1 or 2 > > i get messages as follows in dmesg > > dmesg | grep rtc > [ 5.730955] hctosys: unable to open rtc device (rtc0) > [ 22.881692] rtc-ds1307: probe of 2-0068 failed with error > [ 22.892945] rtc-ds1307: probe of 1-0068 failed with error -5 > > is there a problem with the pi3 and fedora25 and i2c There's a GPIO MUX device on the RPi3 that's not on the 2 which is used to deal with some bits around the WiFi/BT changes while keeping the 40 pin connector compatible. It might be that you need to adjust the pinmux depending on which i2c pins you're using. I'm not exactly sure of the details and some of it is hidden behind the firmware. > im also getting about 600 after being on less than 2 hours: This should be fixed when 4.9.x lands in stable, else you could try a 4.10 rcX release too. > [ 1300.005255] i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100 > [ 1300.006707] i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100 > [ 1300.008158] i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100 > > lsmod|grep i2c > i2c_dev 16384 0 > i2c_bcm2835 16384 0 > > if this is just something i need to wait for development , then thats fine, just want to be sure its not me. > > regards peter > > > _______________________________________________ > arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
