Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

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.