Hello - I'm having problems using the Internal RTC inside the AM625.
On the TI EVM, it's working just fine:
root@am62xx-evm:~# insmod rtc-ti-k3.ko [ 24.999420] rtc-ti-k3 2b1f0000.rtc: registered as rtc0 [ 25.004779] rtc-ti-k3 2b1f0000.rtc: setting system clock to 1970-01-01T00:00:31 UTC (31) [ 25.006859] systemd-journald[177]: Time jumped backwards, rotating. root@am62xx-evm:~# hwclock -r 1970-01-01 00:00:35.364488+00:00 root@am62xx-evm:~# hwclock -w root@am62xx-evm:~#
However, on our own product, which is based on the AM625 EVM design, I'm getting an error when trying to write to the RTC:
# insmod rtc-ti-k3.ko [ 99.212244] rtc-ti-k3 2b1f0000.rtc: registered as rtc0 [ 99.226029] rtc-ti-k3 2b1f0000.rtc: setting system clock to 1970-01-01T00:00:00 UTC (0) # ls -al /dev/rtc* lrwxrwxrwx 1 root root 4 May 21 19:53 /dev/rtc -> rtc0 crw------- 1 root root 251, 0 May 21 19:53 /dev/rtc0 # hwclock -r Thu Jan 1 00:00:00 1970 0.000000 seconds # hwclock -w hwclock: RTC_SET_TIME: Connection timed out
I've observed that the error message ("hwclock: RTC_SET_TIME: Connection timed out") is returning immediately from the call to hwclock, whereas on the TI EVK the successful call to hwclock take about a second to return.
I've compared driver source, device tree, and kernel configuration, and don't see any discrepancies or omissions. Can anyone at TI give any further suggestions?
