cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeMX / HAL Bug Report: PLLSAI

evan23
Associate II
Posted on July 14, 2014 at 02:29

In trying to compile generated code from the STM32CubeMX application for the STM32F429I-DISCO board, I've found a problem with part of the HAL library.

Simply, the PLLSAI assert #defines have a bug in their definition:

/** @defgroup RCCEx_PLLSAI_Clock_Source 
* @{
*/
#define IS_RCC_PLLSAIN_VALUE(VALUE) ((192 <= (VALUE)) && ((VALUE) <= 432))
#define IS_RCC_PLLSAIQ_VALUE(VALUE) ((2 <= (VALUE)) && ((VALUE) <= 15))
#define IS_RCC_PLLSAIR_VALUE(VALUE) ((2 <= (VALUE)) && ((VALUE) <= 7)) 
/**
* @}
*/

This is the same setting as the normal PLL configuration. However, the PLLSAI configuration allows for a looser 49-432 definition (see

http://www.st.com/st-web-ui/static/active/en/resource/technical/document/reference_manual/DM00031pdf

). So, this needs to be instead defined as,

#define IS_RCC_PLLSAIN_VALUE(VALUE) ((49 <= (VALUE)) && ((VALUE) <= 432))

This begs the question: Is there any formal way of reporting bugs with the ST provided libraries / tools, rather than just on the forums?
2 REPLIES 2
Amel NASRI
ST Employee
Posted on July 14, 2014 at 11:13

Hello Elaske,

Thanks for reporting this issue, it will be forwarded to relevant people.

You can continue to submit the STM32 related issues you are facing here throw our forums.

Best Regards

-Mayla-

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.

Posted on August 28, 2014 at 12:29

Hi elaske,

Thanks for the report. We’ve noted this as a limitation in the STM32Cube HAL bugs list.

It's not really a bug, but it's a non coherence limitation with the new STM32F4 Reference Manual document. Please keep an eye out for the next releases of STM32CubeF4.

With regards.