Hello,
We use RA6M5. The FSP is 3.5.0.
Previously, we used the internal clock as the RTC source, but it caused time-drifting issues, leading to RTC inaccuracy. In the new hardware design, an external 32,768Hz crystal has been added, and we are now using it as the RTC clock source.
However, we encountered an issue with the RTC. Initially, we set the device time to 9:50 AM. When the time reaches 10:00 AM, the R_RTC_CalendarTimeGet() function retrieves the time from the RTC driver. Instead of returning 10:00 AM, it returns 12:00 AM. Additionally, we noticed that the time resets to 12:00 AM every 12 hours.
Do you know why the hour, which should be 10, resets to 0? Could you also provide insights into why the time resets every 12 hours?
By using the internal clock as the RTC clock source, there is no such issue.
Thanks!