CUBOX 510 hwclock set to 2020-10-10.09 after reboot

This forum is for supported devices using an ARMv7 Marvell SoC.

CUBOX 510 hwclock set to 2020-10-10.09 after reboot

Postby Iridium747 » Tue Jan 31, 2017 10:57 am

If I set the RTC with hwclock -w just before shutting down. When I power it back on again it is set to 2020. At first I thought it might be the battery, but surely if that is the case it should default to 1970?

Where does the RTC get set in the shutdown sequence? I've looked around and cannot find anywhere. Someone suggested /usr/lib/systemd/system-shutdown but that doesn't seem to get run.

Someone suggested that, if true, whick it is, hwclock shouldn't be run? Any ideas?

root@Arcturus:~# zgrep HCTOSYS=y /proc/config.gz

alarm@Arcturus:~$ sudo hwclock
2020-10-10 09:10:12.405393+0100

root@Arcturus:~# hwclock --debug
hwclock from util-linux 2.29
Using the /dev interface to the clock.
Last drift adjustment done at 1485799864 seconds after 1969
Last calibration done at 1485799864 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick... clock tick
Time read from Hardware Clock: 2020/10/10 08:29:32
Hw clock time : 2020/10/10 08:29:32 = 1602318572 seconds since 1969
Time since last adjustment is 116518708 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2020-10-10 09:29:31.500348+0100

root@Arcturus:~# timedatectl
Local time: Tue 2017-01-31 10:53:06 GMT
Universal time: Tue 2017-01-31 10:53:06 UTC
RTC time: Sat 2020-10-10 08:40:30
Time zone: Europe/London (GMT, +0000)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
Posts: 5
Joined: Fri Jan 27, 2017 10:17 am

Return to Marvell

Who is online

Users browsing this forum: No registered users and 2 guests