FreeRTOS + STM32 , Systick interrupt priority issue

[HansUweRempler]

Issue by BoykoKazakov Tuesday Dec 10, 2019 at 09:10 GMT Originally opened as https://github.com/Bosch-AE-SW/cddk-oss/issues/422

---

ST HAL SysTick must be at the highest priority, as there are Hal layers using timouts and etc. RTOS forces the SysTick priority to be lowest. So for now best workaround will be to maybe introduce a second timer.

[HansUweRempler]

Comment by HansUweRempler Wednesday Dec 11, 2019 at 12:34 GMT

---

STMCube issue --> incorrect for all used RTOS (FreeRTOS, mbed, etc.) Future feature request: tickless option for lowest energy consumption (Kiso USP: power optimized for extended battery life should be shown in "example\c- power_optim") @BoykoKazakov please add some tasks here like

• [ ] Screen how Amazon FreeRTOS is doing this
• [ ] After the above, decide is proposal is reasonable: introducing a second timer
• [ ] Implement/fix

[HansUweRempler]

Comment by amushatov Wednesday Dec 11, 2019 at 14:15 GMT

---

Amazon doesn't integrate STMCube and doesn't deal with specific problems. STM is integrating Amazon solutions. However, STM doesn't fully agree this is a bug, still providing an advice to use another timer if any RTOS is used. https://community.st.com/s/question/0D50X00009XkhEpSAJ/cubemx-freertos-using-systick

Tickless option can be discussed when we start its implementation.