Posted on June 26, 2015 at 07:08Because I did not generate the STM32F1 code,
I could not conclude your problem is the STM32CubeMX's clock generation bug.
However, I also suffered from the STM32CubeMX.
I don't know the the following method is applied to your code, but you could get a hint in my process.
---------------------------------------------------------------------------------------------------------
In order to decide the generated clock code is correct,
you should probe the SystemClock_Config() function in the main().
At the last of this function, the following code is shown.
HAL_SYSTICK_Config(
HAL_RCC_GetHCLKFreq()/1000);
To watch the value in real-time, configure the break point to the return state.
uint32_t HAL_RCC_GetHCLKFreq(void)
{
SystemCoreClock = HAL_RCC_GetSysClockFreq() >> APBAHBPrescTable[(RCC->CFGR & RCC_CFGR_HPRE)>> POSITION_VAL(RCC_CFGR_HPRE)];
â—�
return
SystemCoreClock;
}
If the value of in the watch is correct, then it's not problem.
Maybe this value is configured you don't intend.
The next process is comparing with the example of Standard Peripheral library.
Maybe no SetSysClock() function is in the system_stm32f1xx.c.
If then, you should copy the definition of PLL configuration and this SetSysClock() function.
After copy the SetSysClock() function and related code like PLL configuration,
you would find the intended clock configured value in the watch window.
---------------------------------------------------------------------------------------------------------
