possible bug in clock generation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-06-09 12:26 AM
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;
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-06-09 2:46 AM
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-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-07-06 1:35 AM
Hi,
You are right,
SystemCoreClock = 16000000 is correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-07-06 5:50 AM
You are right,
SystemCoreClock = 16000000 is correct.
