cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H562/3: clarify the max frequencies in DS14258 rev6

Adu_It
Associate
  1. According to the STM32 datasheet, the maximum clock frequency of TIM6 and TIM17 is shown as 64 MHz, while that of TIM1 to TIM8 is shown as 200 MHz. There is a conflict in the documentation, so please confirm which one is correct. (DS14258 Rev6,page 132)
  2. The datasheet indicates that the maximum supported clock frequency of SPI is 100 MHz, but no errors are displayed when configuring 200 MHz in CubeMX. Please confirm the actual maximum clock frequency of SPI.

1 ACCEPTED SOLUTION

Accepted Solutions
mƎALLEm
ST Employee

Hello,

1) This is a known issue raised already by another customer. There is a typo regarding the maximum allowed clock frequencies for TIM16 and TIM17. The 64 MHz applies to TIM12 and TIM15 when HSI_KER_CK/1024, HSI_KER_CK/8, and CSI_KER_CK/128 are selected for input capture; otherwise, it is 250 MHz for all timers in VOS0. To avoid confusion, the 64 MHz value will be removed from the DS table. It will be fixed in the coming rev of the datasheet. (internal ticket number 221378)

2) The datasheet is always the reference so for the second question I suggest to open a new thread in STM32CubeMx forum board.

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.

View solution in original post

2 REPLIES 2
mƎALLEm
ST Employee

Hello,

1) This is a known issue raised already by another customer. There is a typo regarding the maximum allowed clock frequencies for TIM16 and TIM17. The 64 MHz applies to TIM12 and TIM15 when HSI_KER_CK/1024, HSI_KER_CK/8, and CSI_KER_CK/128 are selected for input capture; otherwise, it is 250 MHz for all timers in VOS0. To avoid confusion, the 64 MHz value will be removed from the DS table. It will be fixed in the coming rev of the datasheet. (internal ticket number 221378)

2) The datasheet is always the reference so for the second question I suggest to open a new thread in STM32CubeMx forum board.

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.

Thank you for your helpful response. This has resolved my questions.