BlueWave Studio forum
RTC ds3231 error in Raspbian - Printable Version

+- BlueWave Studio forum (https://bluewavestudio.io/community)
+-- Forum: OpenAuto Pro (https://bluewavestudio.io/community/forum-86.html)
+--- Forum: Real Time Clock (RTC) (https://bluewavestudio.io/community/forum-82.html)
+--- Thread: RTC ds3231 error in Raspbian (/thread-1139.html)

RTC ds3231 error in Raspbian - pyto00 - 09-19-2019

Hi,

I am struggling to get the RTC working. I have a ds3231.
Installed and setup correctly.

I get this error when sudo hwclock -r

hwclock ioctl(rtc_rd_time) to /dev/rtc0 to read the time failed remotrre I/o error
 ds3231 is also not listed in /etc/modules. I only found ds1307.

Can it be that ONLY ds1307 is supported by openauto ?

RE: ds3231 not working on Build3.3.2-B2 - Daniel_BlueWave - 09-19-2019

If you would configure it correctly then it would work. The OpenAuto Pro is an application running under regular Raspbian OS and error you have mentioned is coming from OS. Looks like you did not read any posts in RTC section at forum or in User Manual.

We recommend to do that.

RE: ds3231 not working on Build3.3.2-B2 - pyto00 - 09-22-2019

(09-19-2019, 05:38 PM)Daniel_BlueWave Wrote: If you would configure it correctly then it would work. The OpenAuto Pro is an application running under regular Raspbian OS and error you have mentioned is coming from OS. Looks like you did not read any posts in RTC section at forum or in User Manual.

We recommend to do that.
Thanks for the recommendation, but I did follow the steps that I found in the RTC section.
I found the source of the error, it has something to do with adress interfering on the i2c bus I think
When I pull the touchscreen out of SDA and SCL, then hwclock -r returns the date&time
When I connect the touchscreen again, I get one of the following errors

rhwclock: ioctl(RTC_RD_TIME) to /dev/rtc0 to read the time failed: Invalid argument
hwclock: ioctl(RTC_RD_TIME) to /dev/rtc0 to read the time failed: Remote I/O error

 I also noticed that the touchscreen sometimes uses the same adress as the RTC ( 0x68 ).
 This is only with the touchscreen connected to the i2c bus., 
pi@raspberrypi:~ $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- 17 -- 19 -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- 38 -- -- -- -- -- -- --
40: -- -- -- -- -- 45 -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- 68 -- -- -- 6c -- -- --
70: -- -- -- -- -- -- -- --


Any tips?