Skip to main content
Pavel A.
October 5, 2021
Question

[BUG] CubeMX, weird behavior of the Clock config view

  • October 5, 2021
  • 2 replies
  • 1327 views

On STM32H753, I want to change the clock source of I2C1.

Previously it was HSI with divisor 4 that gives 16 MHz.

0693W00000FBXXFQA5.pngI noticed that PLL3R outputs almost 16 MHz and try to change I2C1 to this source.

Then Cube craps out and declares conflict. Auto-resolving it changes settings of PLL1 and clock rates of other peripherals.

0693W00000FBXZLQA5.png 

What's wrong with it?

Finally I managed to tweak PLL3 ... maybe by pure luck.

CubeMX ver 6.2.1

This topic has been closed for replies.

2 replies

TDK
October 5, 2021

The outputs from DIVMx, which are the input to the PLL, need to be within 1-16MHz. Seems like it should be giving you an error in the top picture as well. Could be more clearly written in the RM, but it's there.

0693W00000FBY8BQAX.png 

0693W00000FBY8GQAX.png

"If you feel a post has answered your question, please click ""Accept as Solution""."
Pavel A.
Pavel A.Author
October 5, 2021

Thank you TDK!

Well, then bug report:

  • When PLLn (1-3) is unused, clock config should not show invalid or meaningless values.
  • When PLLn parameters are auto-resolved, changes should not affect other PLLs, if possible.