cancel
Showing results for 
Search instead for 
Did you mean: 

Bug with STM32L476 PLL source?

Coratron
Associate II
Posted on September 25, 2017 at 03:42

Hi All,

I have been experimenting with my

http://www.st.com/en/evaluation-tools/nucleo-l476rg.html

I have generated some code with CubeMX for SW4STM32 and I am getting some problems with the code, ending up in an Error Handler sometimes (in main):

void _Error_Handler(char * file, int line)

{

  /* USER CODE BEGIN Error_Handler_Debug */

  /* User can add his own implementation to report the HAL error return state */

  while(1)

  {

  }

  /* USER CODE END Error_Handler_Debug */

}

This happens when I do the following:

Use the main clock source for the PLL as HSI, and tick the option 'generate peripheral initialization as a pair of '.c/'h' files per peripheral', which I prefer to keep things tidy, in CubeMX.

If I use the MSI instead of the HSI, I don't get this problem.

I am attaching my project for your perusal. Is this a known bug? Or am I missing something?

Thanks!

#pll #nucleo-l476rg #clock #stm32l4 #cubemx #stm32l476
2 REPLIES 2
Coratron
Associate II
Posted on September 25, 2017 at 04:02

Someone has reported the potential cause:

https://community.st.com/0D50X00009Xkh6lSAB

I have introduced the M parameter and it seems to work now.

Imen.D
ST Employee
Posted on September 25, 2017 at 18:18

Hello, 

This is already raised internally to CubeMx team and we come back to you as soon as we have needed details.

Best Regards

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen