What could be possibly wrong to make the RTC hour keep count up above 23 hour. With some boards it works correctly, going to 00 from 23. but some other keep count up 24, 25...
How is that possible? There is any configuration to do that?
Obs.: Removing the battery and soldering it again, made the bug desapear for now. But honestly, this is not a solution if it happen again with a costumer.
"But honestly, this is not a solution if it happen again with a customer."
Perhap you could recognize it is occurring and reset the RTC. Surely a way to do that without removing the battery. Consider a link or switch so you don't need to physically desolder stuff.
Sense the failure state, so next time you can root-cause the issue with an FAE. Perhaps file a support ticket now so you can get feedback or answers from their FAQ.
Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
Failure to properly initialize auto/local variables, which live on the stack with random content, is the cause of a million latent failures. ST code is rife with them, as is the use of globals.
RTC_TimeTypeDef sTime = {0}; // Ensures at least you're starting with a clean and consistent sheet
It also helps the compiler/optimizer as it hints at intent.
Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..