Skip to main content
Graduate II
January 18, 2024
Solved

Nucleo-F303RE want to set timer source muxes to use PLLCLK*2, to yield 2 * 72 MHz=144 MHz resolution

  • January 18, 2024
  • 2 replies
  • 1549 views

I'm on Nucleo-F303RE board, which according to the page 129-130 of the reference manual (RM0316 Rev 10) I should be able to set "TIMx (x = 1/2/3/4/8/15/16/17/20) can be clocked from the PLL running at 144 MHz when the system clock source is the PLL and AHB or APB2 subsystem clocks are not divided by more than 2 cumulatively":

ericfont_2-1705608111890.png

 

However, when I create a new project for Nucleo-F303RE board, and configure the clock tree to meet these conditions (system clock source is the PLL && AHB or APB2 subsystem clocks are not divided by more than 2 cumulatively), then I can't seem to toggle the dot in the muxes for TIMx source mux (where x=1, 8, 15, 16, 17, 2, 3/4), and the dots in the muxes are greyed out int he clock configuration tool:

ericfont_0-1705607810460.png

I'm new to STM32 environment, so I might be doing something basic wrong.

    This topic has been closed for replies.
    Best answer by AScha.3

    As long as you have nothing enabled/used , that uses a certain clock mux out , its not activated...grey.

    Select -maybe- TIM1 and then choose the clock for it - mux is no more grey then !

    2 replies

    AScha.3Answer
    Super User
    January 18, 2024

    As long as you have nothing enabled/used , that uses a certain clock mux out , its not activated...grey.

    Select -maybe- TIM1 and then choose the clock for it - mux is no more grey then !

    ericfontAuthor
    Graduate II
    January 18, 2024

    Aha! Enabling the timer first successfully ungreyed the mux so I could change the configuration dot to select PLLCLK*2=144 MHz. Thanks!

    Graduate II
    January 18, 2024

    Can't say I'd ever noticed this feature, but not a user of the F3's

    Generally on other STM32 the PLL VCO pulses at a higher frequency and is always divided by two to get a square wave (50/50 duty) as the CPU core is built on that expectation.