AnsweredAssumed Answered

stm32F1 systemClock_Config() causes error in stm32CubeMX in v_4.20 works well in v4.08 with rtos

Question asked by Krishna.Anish on Mar 27, 2017
Latest reply on May 1, 2017 by David Kaplan

Hello All,

I had been using stm32CubeMX v4.08 with w/wo freeRtos on stm32F103CB series mcu successfully , until recently when i upgraded cubeMx to version 4.20. I am totally stuck since then, since i have so got used to using HAL abstraction...

 

Calling systemClockConfig() in main() .. causes HAL_Timeout - causing function Error_Handler to be called in the following line..

if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)
  {
    Error_Handler();
  }

 

on commenting out

 

/* Configure the system clock */
//  SystemClock_Config();

 

 ..or..

 

//Error_Handler();

 

the cpu runs but presumably on the systemInit()'s reset default HSI clock..

I assume its a bug in hal_rcc drivers...

Can you please suggest some way to get out of this....

Regards

Anish.

Outcomes