the problem is, that the system is awake at least for the duration of one system tick - depends on the configTICK_RATE_HZ.
So my MCU is waken up every second to look for tasks to do and has to go to sleep (what most of it is) after wards.
I figured out, that this takes at least one System Tick which is not very energy efficient.
I’ve done some tests:
If I put a xTaskIncrementTick() after the vTaskStepTick(ulCompleteTickPeriods ), this aditional tick is marked as pending
and the system goes to sleep - almost immediately after wards as it should do.
Since I didn’t found a solution or explanation about that behaviour, is it OK to do it that way?
Or are there any other threads which I missed?
Thanks and Regards.