2024-10-06 11:15 PM - last edited on 2024-10-09 06:20 AM by Andrew Neil
I executed "Clock Example" on stm32H747I DISCO. I found that after two minutes of execution, the analog clock was about 15 seconds slower. After 53 minutes of execution, it was about 5 minutes slower, and it will become slower and slower. I did not add any The program code is in the M7 core. The way I compare is to enable RTC and uart in the M4 core, use the HAL_RTC_GetTime() function to read out the rtc time every second, and print it out through the uart. My question is, If the analog clock really slows down, is there any way I can correct it without users noticing?
Solved! Go to Solution.
2024-10-09 05:08 AM
Hello @Kenwang,
I tested the example on the simulator and didn't experience the clock slowing down. In addition, I don't understand why you decided to increase the priority of videoTask since it is not responsible for animations.
Following the suggestions given by our lovely friends would be a good solution to ensure the clock won't fall behind.
Best regards,
2024-10-09 05:27 AM - edited 2024-10-09 05:29 AM
Primary understand, that example is only *** eample, not Swiss clock. Tgfx tick is not valid timebase , technicaly crystal RTC need too special calibrating for one week precise clock ...
For real clock you rewrite example code ... Here dont work many design thinks, for example hours dont move between ...