2017-03-08 06:36 PM
when generating code for an stm32f769i-discovery with rcc set to enable external clock, the latest version does this:
RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;
which causes a fault when it hits HAL_RCC_OscConfig(). the fix, and the behavior in previous versions, is to not try to choose both clocks at once.
RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE;
Solved! Go to Solution.
2017-04-19 06:14 AM
Hello,
Please note that this bug is already fixed in a patch of STM32CubeMX (V4.20.1) delivered end of March to fix the regression issue.
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2017-03-09 01:59 AM
Hi John,
I confirm this bug. Our CubeMX team will take care of this to provide a fix soon.
Sorry for such inconvenience.
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2017-04-19 06:14 AM
Hello,
Please note that this bug is already fixed in a patch of STM32CubeMX (V4.20.1) delivered end of March to fix the regression issue.
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2017-07-12 09:38 AM
I found this bug also with F4:
STM32CubeMX V4.22.0
STM32F4 1.16.0Please confirm that it can be fixed removing
RCC_OSCILLATORTYPE_HSI
in
RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;
Have I to install a patch?
Why V4.22.0 didn't come with the patch that has been developed for V4.20.1?Regards,
Luca