Skip to main content
Junde
Senior III
March 23, 2023
Solved

Why is the clock config error?

  • March 23, 2023
  • 1 reply
  • 944 views

Hi, when I use the cubemx to config the stm32h743iit6 project, the clock system shows some error as below. But I try it on another PC, and the same config can work well.

I don't know why?

0693W00000aJZg9QAG.png

This topic has been closed for replies.
Best answer by Foued_KH

Hello @Junde​ ,

For the STM32H743 , we have 3 revisions : V , Y and X. (errata sheet)

Use silicon revision V devices to reach a maximum frequency of 480 MHz.

Please make sure which revision you have and you can refer to :

  • To get 480 MHz, go to the RCC parameters and check that the product revision is "V".
  • For some reason the default is "Y".
  • Then set the power regulator voltage scale to 0.

Foued

1 reply

Foued_KH
Foued_KHBest answer
ST Employee
March 23, 2023

Hello @Junde​ ,

For the STM32H743 , we have 3 revisions : V , Y and X. (errata sheet)

Use silicon revision V devices to reach a maximum frequency of 480 MHz.

Please make sure which revision you have and you can refer to :

  • To get 480 MHz, go to the RCC parameters and check that the product revision is "V".
  • For some reason the default is "Y".
  • Then set the power regulator voltage scale to 0.

Foued

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.
Junde
JundeAuthor
Senior III
March 23, 2023

@KHALSI_Foued​ 

Thanks for your reply.

As per your description, there are different revisions on RCC config page(but just rev.Y and rev.V, NO rev.X).

And I want to know how to make sure which revision the chip I have is.

Just see the silk print on the chip surface?​

Foued_KH
ST Employee
March 24, 2023

Yes, you can just look at your MCU.

Or try to connect your board to the STM32CubeProgrammer.

Foued

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.