STM32F37x: What is ''tempo'' or probably temporization for the clocks

[Uwe Bonnes]

Posted on January 07, 2013 at 18:17

Hello,

rm0313 in figure 10 ''Clock tree part1'' has a ''tempo'' unit at each clock input. Beside a use of  the word ''temporization'' in 7.2.11 ''Watchdog clock'', I see no more use of that word and no explication at all. What is this ''temporization''? Thanks #unclear-term #poor-documentation

[Tesla DeLorean]

Posted on January 07, 2013 at 19:50

What is this ''temporization''?

''

the act of delaying

'' In the context used classically by ST it means a delay for the purposes of stabilization, in the case of the clocks the F1's LSI needs an additional 100us to become truly stable.

[Andrew Neil]

Posted on January 07, 2013 at 22:48

That doesn't seem to make much sense in the context of the figure to which

was referring?

[John F.]

Posted on January 08, 2013 at 09:31

Makes sense to me. Both the LSI and LSE oscillators will take a finite time to start and become stable after they have been enabled. For example, the LSIRDY flag in the Control/status register (RCC_CSR) indicates if the LSI oscillator is stable or not. At startup, the clock is not released until this bit is set by hardware.

Presumably the ''tempo'' blocks handle this functionality.

[Andrew Neil]

Posted on January 08, 2013 at 11:31

OK - now I see.

But it remains very poor that we should have to guess at this stuff - it should be clearly & explicitly stated in the documentation.