Skip to main content
Associate II
August 5, 2025
Question

MX shows Clock Configuration error after updating

  • August 5, 2025
  • 1 reply
  • 168 views

I just upgraded STM32CubeIDE from 1.17 to 1.19 which in turn upgraded MX from 6.13 to 6.15

Prior to updating, in MX Clock Configuration I could clock the SPI system on the STM32H533 at the same rate as the CPU clock (250 MHz with no error). Now, to avoid the configuration error, I have to reduce it to 125 MHz.

My code ran fine at 250 MHz in the previous version. IS THIS A FIX OR A BUG?

Thanks!

1 reply

TDK
Super User
August 5, 2025

Max allowed SPIx clock is 125 MHz.

TDK_0-1754357225638.png

Bug fix.

 

"If you feel a post has answered your question, please click ""Accept as Solution""."