2017-03-16 02:54 AM
I found a bug in the new Cube Version.
At line 1 internal oscillator is enabled although it is not used, in fact it is not actived:
RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE
|RCC_OSCILLATORTYPE_LSE;
RCC_OscInitStruct.HSEState = RCC_HSE_ON;
RCC_OscInitStruct.LSEState = RCC_LSE_ON;
RCC_OscInitStruct.PLL.PLLState = RCC_PLL_NONE;
if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)
{
Error_Handler();
}�?�?�?�?�?�?�?�?�?
This brings HAL_RCC_OscConfig() to fail (timeout).
Thanks and BR,
Andrea
#cube #clock #bug2017-03-16 03:03 AM
Hello Andrea,
I confirm this bug, this is already reported internally to our CubeMx team and will take care to fix this issue.
Sorry for such inconvenience.
Regards
Imen
2017-03-26 10:37 PM
bug,I am。
2017-04-04 07:25 AM
I confirm the bug. Replicated using STM32F4-discovery board. When configure HSE, this 'RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;' bug will occure.
2017-04-04 09:48 AM
Seem to be several people with similar/familiar issues with current release of CubeMX across platforms.
Please do more regression testing before releasing broken code to the ecosystem, the Adobe/Microsoft model for releasing streams of differently broken, but never fully fixed code, is really NOT appropriate for embedded systems where installed lifespan may exceed 10 years.
2017-04-05 08:51 AM
Hello,
The RCC config issue is fixed in the new patch CubeMx v4.20.1
So, please download and update the new version to resolve this issue.
PS: if you are using an old .ioc project, you should first EDIT the .ioc file and REMOVE the RCC.OscillatorType that you don't need
E.g: remove this line
RCC.OscillatorTypeHSI=RCC_OSCILLATORTYPE_HSI
Then re-generate the project, this will resolve your problem.
Best Regards
Imen
2017-04-06 08:34 AM
Ok, thank you Imen.
BR,
Andrea