Signed-off-by: Frederic Pillon <frederic.pillon@st.com>

Signed-off-by: Frederic Pillon <frederic.pillon@st.com>

See #28

Signed-off-by: Frederic Pillon <frederic.pillon@st.com>

* CMSIS_device_header must be defined.
* Some Includes define must be set

Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

Signed-off-by: Frederic Pillon <frederic.pillon@st.com>

SysTick_Handler() from stm32duino core is calling weak osSystickHandler().
Both CMSIS-RTOSv2 and CMSIS-RTOS override osSystickHandler()
which is calling xPortSysTickHandler(), defined in respective CortexM-x port

Note: It is necessary to go through this function
(osSystickHandler()) that checks whether scheduler is started
otherwise there are issue when systick interrupt fires before FreeRTOS is started

Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

…duler()

On Cortex-M0 and Cortex-M0+, all IT are disabled between xTaskCreate() and
vTaskStartScheduler().
So it is not possible to use IT inbetween, like Serial.print() ...
This is the reason why, in example "frLiyLayland", between xTaskCreate()
and vTaskStartScheduler(),
we use direct printf(), which will access directly USART without interrupt

Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

Update to Freertos 10.3.1 Add CortexM33 support

Fixes #44

Signed-off-by: Frederic Pillon <frederic.pillon@st.com>

It happens on STM32WL that case 4 fails.
And it seems to be linked to LiuLayland theoritical bound value,
which is based on ideal system.
It doesn't take into account things like RTOS task swap, ...
So take more margin for case 4 by decreasing the cpu load of one task,
so that global CPU moves away from theoretical bound.

Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>

feat: support STM32WL family