Rtc time

DRIVE OS Version: Provide DRIVE OS version. Example: 7.0.3

Issue Description: Provide issue description and attached logs as text message instead of images

When the Thor system boots up, the timedatectl command shows that the system time and RTC time are synchronized. After sitting idle overnight, the RTC time is 8 seconds ahead of the system time, and this phenomenon occurs on both machines。

tegra-ubuntu:~$ timedatectl
Local time: Mon 2025-12-29 16:47:25 CST
Universal time: Mon 2025-12-29 08:47:25 UTC
RTC time: Mon 2025-12-29 08:47:25
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no

tegra-ubuntu:~$ timedatectl
Local time: Tue 2025-12-30 11:03:49 CST
Universal time: Tue 2025-12-30 03:03:49 UTC
RTC time: Tue 2025-12-30 03:03:59
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no

tegra-ubuntu:~$ timedatectl
Local time: Tue 2025-12-30 14:17:44 CST
Universal time: Tue 2025-12-30 06:17:44 UTC
RTC time: Tue 2025-12-30 06:17:57
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no

Dear @youth_zhang ,
Could you enable NTP and see if it fixes issues.

Dear NV:

After the NTP function is started, the RTC clock will always be updated from the Internet synchronization time, without this phenomenon. However, our product prevents time jump and only runs timesync to synchronize the Internet time when starting up. And both NTP synchronization time and RTC maintenance time functions should be able to work independently and normally.

Dear @youth_zhang ,
Does that mean you don’t want to keep NTP service:active all the time? If so, how about enabling NTP via timedatectl and disable periodically?

Operation steps:

  1. System d timesync starts automatically upon startup
  2. After 1 minute, turn off systemd timesync
  3. Turn on the device and let it sit for one night
  4. Check the system time and RTC time the next day.
    In fact, this has nothing to do with NTP. The same is true when the system is not connected to the Internet. Even if the system d-timesync is always started, it cannot always synchronize with the Internet time. Moreover, maintaining NTP synchronization time and RTC time are two separate issues.
    Can you help me check if there are any further questions about this description?

Dear @youth_zhang ,
I don’t see RTC time in timedatectl. Could you please share repro steps.