Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32


HAL_IncTick() Called From Two Places

As recommended by a pop up message box in STM32CubeMX I set it to use a timer (I used TIM6) for the ticker instead of the system timer. Now I see in the STM32CubeMX generated code there is a call to HAL_IncTick() in both the callback function HAL_TIM_PeriodElapsedCallback() in stm32f3xx_hal_timebase_TIM.c and SysTick_Handler() in stm32f3xx_it.c.

Is it really necessary to call HAL_IncTick() from both these functions? Is the call from SysTick_Handler() a bug?

I am using STM32CubeMX Version 4.14.

Tunisia

Hello Stephen,

Thank you for reporting the issue.

Unfortunately we cannot not reproduce the issue.
So could please attach an the *.ioc, stm32f3xx_hal_timebase_TIM.c and stm32f3xx_it.c to investigate the problem.

Tarek BOUCHKATI
STMicroelectronics


I am sorry, I failed to notice earlier that the call to HAL_IncTick() in SysTick_Handler() was inside the user code block. This was not put there by STM32CubeMX.