How to resolve warning: initialization of 'uint32_t (*)(const TIM_TypeDef *), from incompatible pointer type 'uint32_t (*)(TIM_TypeDef *)

[Niranjan-eaton]

Origin

How to resolve Warning, while building Multi_Timers in 3.2.0 Zephyr version.
zephyr-v3.2.0/zephyr/drivers/counter/counter_ll_stm32_timer.c:40:9: warning: initialization of 'uint32_t (*)(const TIM_TypeDef )
{aka 'unsigned int ()(const TIM_TypeDef )'} from incompatible pointer type 'uint32_t ()(TIM_TypeDef )' {aka 'unsigned int ()(TIM_TypeDef *)'}
[-Wincompatible-pointer-types]

Type

zephyr-v3.2.0
board: nucleo_h743zi

Module

Multi_Timers example

nucleo_h743zi.overlay
&timers2 {
st,prescaler = <95>;
counter {
compatible = "st,stm32-counter";
status = "okay";
};
};

Purpose

Resolve below warnings,
zephyr/drivers/counter/counter_ll_stm32_timer.c:40:9: warning: initialization of 'uint32_t (*)(const TIM_TypeDef )'
{aka 'unsigned int ()(const TIM_TypeDef )'} from incompatible pointer type 'uint32_t ()(TIM_TypeDef )' {aka 'unsigned int ()(TIM_TypeDef *)'} [-Wincompatible-pointer-types]
40 | LL_TIM_OC_GetCompareCH1, LL_TIM_OC_GetCompareCH2,

zephyr-v3.2.0\zephyr\drivers\counter\counter_ll_stm32_timer.c

		/** Channel to compare get function mapping. */

Line No:38 #if !defined(CONFIG_SOC_SERIES_STM32F4X)
Line No:39 static uint32_t(*const get_timer_compare[TIMER_MAX_CH])( const TIM_TypeDef *) = {
Line No:40 LL_TIM_OC_GetCompareCH1, LL_TIM_OC_GetCompareCH2,
Line No:41 LL_TIM_OC_GetCompareCH3, LL_TIM_OC_GetCompareCH4,
};
#else
static uint32_t(*const get_timer_compare[TIMER_MAX_CH])(TIM_TypeDef *) = {
LL_TIM_OC_GetCompareCH1, LL_TIM_OC_GetCompareCH2,
LL_TIM_OC_GetCompareCH3, LL_TIM_OC_GetCompareCH4,
};
#endif

Note: After removed "const" in static uint32_t(*const get_timer_compare[TIMER_MAX_CH])( const TIM_TypeDef *), warnings are not getting, but not correct way to remove const.

[nordicjm]

@Niranjan-eaton You have selected the wrong category for this, if this is an issue then it should be opened with "bug" not "TSC" - the technical steering committee of zephyr does not need to read this or vote on it.

[FRASTM]

@Niranjan-eaton Can you please check your version of the modules/hal/stm32/stm32cube/stm32h7xx
I guess the pb you see is fixed with version v1.11.0 of the modules/hal/stm32/stm32cube/stm32h7xx
And it will come with the next zephyr 3.3.0
Maybe in between you could west update and get the hal_stm32 master branch c36136b253a46ed8dd63525eeee659393047ce83

[Niranjan-eaton]

Hi @FRASTM, Thank you for sharing hal_stm32 master commit.

I have taken the changes from main hal_stm32, and tried on H7(nucleo_h743zi) board, warnings got resolved.

[Niranjan-eaton]

Resolved, we can close this ticket.