2025-04-10 5:36 AM
Hi there!
Both STM32CubeIDE and the ST MCUFinder tool incorrectly mark the STM32H503 as having a CORDIC and FMAC when they don't.
Could this please be fixed as it's very confusing.
Thank you!
Solved! Go to Solution.
2025-04-10 6:23 AM - edited 2025-04-10 6:40 AM
Hello @etheory
Your contribution is much appreciated.
Issue has been raised to development team for fix.
Internal ticket number 207350
I will keep you posted with updates.
THX
Ghofrane
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.
2025-04-10 6:23 AM - edited 2025-04-10 6:40 AM
Hello @etheory
Your contribution is much appreciated.
Issue has been raised to development team for fix.
Internal ticket number 207350
I will keep you posted with updates.
THX
Ghofrane
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.
2025-05-28 5:55 AM
This is still incorrect in the mcu selector and other tools.
Any idea when it will be resolved?
Thanks.
2025-06-10 3:36 AM
Just another ping on this one as it's been quite a while now and it's still wrong.
2025-06-24 10:15 AM
Unfortunately this has lead me astray as well. Can we have an update on this please?
2025-07-08 5:08 AM
The reported problem was solved, I suggest that you try using STM32CubeMX 6.15.0, which is currently available for download through this link: STM32CubeMX - STM32Cube initialization code generator - STMicroelectronics
BR,
Ghofrane
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.
2025-07-08 8:09 AM - edited 2025-07-08 8:10 AM
Thank you, I will try this.
But in the meantime, the Windows standalone MCU Finder app has just become broken.
Selecting any entry of the PRODUCT INFO -> Segment options, return no results. i.e. if I reset, then choose STM32H5 series, or STM32U5 series, no results are shown. This definitely used to work. The Android app still works, but still shows the incorrect H503 entries.