2026-04-07 1:22 PM
After updating CubeMX to version 6.16.2, we are seeing HRtimer E and F problems which cause our product to fail. Reverting back to 6.15 and regenerating the code allows our device to work. I believe the issue is due to the change in the code database version: MxDb.Version=DB.6.0.161 but I can't be sure as the new version of cubeMX forces values into the HRtimer E and F configurations.
Hoping for commiseration and resolution!
Thanks
Rauk
2026-04-07 1:24 PM
Do a diff of your codebase before/after the change to find the actual code differences. There are release notes as well but comparing the code would be more precise.
2026-04-07 4:59 PM
2026-04-08 7:00 AM
Hello @raulatkinson
Could you provide your ioc in order to investigate the issue?
BR, Souhaib
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2026-04-09 12:28 PM
2026-04-09 3:48 PM
2026-04-13 9:07 AM
Hello @raulatkinson
After checking your IOC, it seems that you are facing the same issue posted in this thread: Solved: HRTIM configuration when updated to 6.16.1 CubeMX - STMicroelectronics Community.
this behavior is under investigation by the dedicated team, and a fix will be implemented in the upcoming releases.
BR, Souhaib
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2026-04-13 10:38 AM
Thank you very much for your response.
Will the fix for this be announced? I'd like to be notified.
-Raul Atkinson