cancel
Showing results for 
Search instead for 
Did you mean: 

possible bug in clock generation

Adalgiso
Associate II
Posted on June 09, 2017 at 09:26

I am using cube 4.21 with a STM32F205 CPU.

I configured the clock to run at 120 Mhz (25Mhz crystal M=20, N 192, P 2) in the file system_stm32f2xx.c generated by cube, I have the following:

uint32_t SystemCoreClock = 16000000;

instead of

uint32_t SystemCoreClock = 12000000;

3 REPLIES 3
Nesrine M_O
Lead II
Posted on June 09, 2017 at 11:46

Hi

Castrignano.Adalgiso

,

  • Did you have an issue to obtain the right system clock?
  • SystemCoreClockvariable takes first theHSIvalue then is updated depending on user clock configuration

  • souint32_t SystemCoreClock = 16000000; is right.

-Nesrine-

Posted on July 06, 2017 at 08:35

Hi,

You are right, 

SystemCoreClock = 16000000 is correct.

Posted on July 06, 2017 at 12:50

You are right, 

SystemCoreClock = 16000000 is correct.

https://community.st.com/0D50X00009bMM5DSAW