Patch_CubeFW_F3 still have a lot of unused parameter warnings.

T B · ‎2018-06-07

Posted on June 07, 2018 at 16:21

Hello!

I have updated LL drivers for stm32F3. Unfortunately I still get a lot of unused parameter warnings.

And I even found one bug.

-Thomas

This is a Bug.

Must be RTCx->ALRMBR:

__STATIC_INLINE void LL_RTC_ALMB_SetDay(RTC_TypeDef *

RTCx

, uint32_t Day)

{

MODIFY_REG(

RTC->ALRMBR

, .....);

}

This are the warnings for STM32F303:

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_rcc.h: In function 'LL_RCC_ConfigMCO':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_rcc.h:1457:69: warning: unused parameter 'MCOxPrescaler' [-Wunused-parameter]

__STATIC_INLINE void LL_RCC_ConfigMCO(uint32_t MCOxSource, uint32_t MCOxPrescaler)

This are the warnings for STM32F301:

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_adc.h: In function 'LL_ADC_DMA_GetRegAddr':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_adc.h:2526:76: warning: unused parameter 'Register' [-Wunused-parameter]

__STATIC_INLINE uint32_t LL_ADC_DMA_GetRegAddr(ADC_TypeDef *ADCx, uint32_t Register)

^~~~~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h: In function 'LL_COMP_SetCommonWindowMode':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:734:71: warning: unused parameter 'COMPxy_COMMON' [-Wunused-parameter]

__STATIC_INLINE void LL_COMP_SetCommonWindowMode(COMP_Common_TypeDef *COMPxy_COMMON, uint32_t WindowMode)

^~~~~~~~~~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:734:95: warning: unused parameter 'WindowMode' [-Wunused-parameter]

__STATIC_INLINE void LL_COMP_SetCommonWindowMode(COMP_Common_TypeDef *COMPxy_COMMON, uint32_t WindowMode)

^~~~~~~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h: In function 'LL_COMP_GetCommonWindowMode':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:760:75: warning: unused parameter 'COMPxy_COMMON' [-Wunused-parameter]

__STATIC_INLINE uint32_t LL_COMP_GetCommonWindowMode(COMP_Common_TypeDef *COMPxy_COMMON)

^~~~~~~~~~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h: In function 'LL_COMP_SetPowerMode':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:791:57: warning: unused parameter 'COMPx' [-Wunused-parameter]

__STATIC_INLINE void LL_COMP_SetPowerMode(COMP_TypeDef *COMPx, uint32_t PowerMode)

^~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:791:73: warning: unused parameter 'PowerMode' [-Wunused-parameter]

__STATIC_INLINE void LL_COMP_SetPowerMode(COMP_TypeDef *COMPx, uint32_t PowerMode)

^~~~~~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h: In function 'LL_COMP_GetPowerMode':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:814:61: warning: unused parameter 'COMPx' [-Wunused-parameter]

__STATIC_INLINE uint32_t LL_COMP_GetPowerMode(COMP_TypeDef *COMPx)

^~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h: In function 'LL_COMP_SetInputHysteresis':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:1042:63: warning: unused parameter 'COMPx' [-Wunused-parameter]

__STATIC_INLINE void LL_COMP_SetInputHysteresis(COMP_TypeDef *COMPx, uint32_t InputHysteresis)

^~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:1042:79: warning: unused parameter 'InputHysteresis' [-Wunused-parameter]

__STATIC_INLINE void LL_COMP_SetInputHysteresis(COMP_TypeDef *COMPx, uint32_t InputHysteresis)

^~~~~~~~~~~~~~~

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h: In function 'LL_COMP_GetInputHysteresis':

./src/stm32_lib/Drivers/STM32F3xx_HAL_Driver/Inc/stm32f3xx_ll_comp.h:1065:67: warning: unused parameter 'COMPx' [-Wunused-parameter]

__STATIC_INLINE uint32_t LL_COMP_GetInputHysteresis(COMP_TypeDef *COMPx)

^~~~~

Amel NASRI · ‎2018-06-07

Posted on June 07, 2018 at 17:40

Hi @T_B,

Thanks for highlighting these issues.

Please note that I reported them internally to be checked and fixed by our development team.

-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.