Following are the RTC drift issue workarounds:
Workaround 1:
If the system has internet connectivity, NTP (Network Time Protocol) can be used to periodically synchronize the RTC. This helps maintain accurate date and time despite the observed drift.
Workaround 2:
iWave has observed a drift of approximately +1 second every 4 hours 48 minutes. To compensate for this in software, we plan to adjust the RTC by subtracting 1 second at this interval within the driver.
Please connect with iWave representative for the driver patch on top of the kernel patch for compilation. With software implementation achieving the accurate drift is not possible.
Previously, the observed drift was approximately 5 seconds over 24 hours. For 48 hours it is around 10 seconds.
With the software workaround, this has been reduced to approximately 3 seconds over 45 hours, which corresponds to about 1 second drift every ~15 hours.
In this implementation, the current system time is stored as a reference timestamp in a file, which is used for drift calculation.
For validation, please use the following steps:
date -s “2026-04-04 11:49:00”
hwclock -w
echo $(date +%s) > /run/media/mmcblk1p1/rtc_base
sync
hwclock -r
Workaround 3:
The issue can also be mitigated through crystal load capacitance tuning, which helps improving the accuracy of 32.768 kHz oscillator and reduce drift at the hardware level.
For further inquiries, please get in touch with mktg@iwave-global.com
Please find the detailed G30M product information in the below link,