Hello @Vahid Ajallooeian ,
First let me apologize for the somewhat late reply.
Actually, as far as I can see from what have been said, the issue is mainly related to the use of a time base other than Systick (tim1 for example).
To explain briefly the situation, starting from the firmware version STM32Cube_FW_F4_V1.25.0, The time base has been reworked in order to change dynamically the Timebase tick frequency (10, 100 and 1000 Hz) following the system frequency. To achieve this change the following functions have been already added in the stm32ynxx_hal.c:
- HAL_StatusTypeDef HAL_SetTickFreq(HAL_TickFreqTypeDef Freq)
- HAL_TickFreqTypeDef HAL_GetTickFreq(void)
In addition to the following exportable variables
- uint32_t uwTickPrio = (1UL << __NVIC_PRIO_BITS); /* Invalid PRIO */
- HAL_TickFreqTypeDef uwTickFreq = HAL_TICK_FREQ_DEFAULT; /* 1KHz */
When using only the default time base i.e. the systick, HAL_Init calls the first time HAL_InitTick(). Upon system clock change, the RCC_ClockConfig calls HAL_InitTick().
However, when using another time base, the HAL_InitTick is not correct: The priority is not stored:
HAL_Init calls the first time HAL_InitTick(), then the frequency of the time base will be changed by calling HAL_SetTickFreq(), and upon system clock change, the RCC_ClockConfig calls HAL_InitTick().
Focusing on the generated stm32f4xx_hal_timebase_tim.c file, the HAL_InitTick is not correct:
HAL_StatusTypeDef HAL_InitTick(uint32_t TickPriority)
{
//....
/*Configure the TIM1 IRQ priority */
HAL_NVIC_SetPriority(TIM1_UP_TIM10_IRQn, TickPriority ,0);
/* Enable the TIM1 global Interrupt */
HAL_NVIC_EnableIRQ(TIM1_UP_TIM10_IRQn);
//...
/* Return function status */
return HAL_ERROR;
}
And thus when calling the HAL_SetTickFreq(); this later will rather use the default prio (defined in the stm32f4xx_hal.c:( uint32_t uwTickPrio = (1UL << __NVIC_PRIO_BITS); /* Invalid PRIO */
The HAL_SetTickFreq() use a wrong Priority and the HAL hangs.
Unfortunately, CubeMX code generation wasn't updated to match this rework. this issue was reported internally to be fixed as soon as possible. I'll keep you posted with the updates.
Sorry for any inconvenience that this may cause.
To overcome this problem, please check stm32f4xx_hal_timebase_tim_template.c file delivered in the latest STM32Cube_FW_F4_V1.26 and edit HAL_StatusTypeDef HAL_InitTick (uint32_t TickPriority) function accordingly.
Hoping that I've answered your question.
Khouloud.
