STM32Cube MCU Full Package for the STM32H7 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits))
[@ALABSTM] (https://github.com/STMicroelectronics/STM32CubeH7/issues/url) we are working on new release of STM32WL "STM32Cube_FW_WL_V1.3.0". release has introduced changes in RTC driver which we believe is fixed for the issue (RTC loosing time issue #24 )
But, after running RTC overnight we have seen RTC issue is still persist in different manner this time RTC is increasing time
Test Start time : 17:55:56, UTC time 1670415956
Test End Time: 9:48:00, UTC time 1670473080, (57124 Seconds)
Difference of UTC time should be : 57124 (1670473080 - 1670415956)
But, From attached logs we can see Test End time is 9:48:00 and total seconds are 57135s837 (check last line in logs).
RTC had generated 57135s837 seconds instead of 57124 Seconds.
So, 57135 - 57124 = 11 Seconds are increased in actual time
[@ALABSTM] (https://github.com/STMicroelectronics/STM32CubeH7/issues/url) we are working on new release of STM32WL "STM32Cube_FW_WL_V1.3.0". release has introduced changes in RTC driver which we believe is fixed for the issue (RTC loosing time issue #24 )
But, after running RTC overnight we have seen RTC issue is still persist in different manner this time RTC is increasing time
Test Start time : 17:55:56, UTC time 1670415956 Test End Time: 9:48:00, UTC time 1670473080, (57124 Seconds) Difference of UTC time should be : 57124 (1670473080 - 1670415956)
But, From attached logs we can see Test End time is 9:48:00 and total seconds are 57135s837 (check last line in logs). RTC had generated 57135s837 seconds instead of 57124 Seconds.
So, 57135 - 57124 = 11 Seconds are increased in actual time
RTCTestLogs.txt RTC Driver.zip Driver files are also attached for more details
Can you please explain what exactly is happening after RTC fix is applied? how to fix this?