taskYIELD() in a loop as best strategy?

[RAc]

@Rik001

Hi,
I have a loop inside which a flag is constantly monitored. Because the tick is 1ms and I am ok checking for that flag every few ms, I don’t want the execution to waste time for the rest of that tick period inside that loop when other taks could do more productive/important work.

Is taskYIELD() the best strategy? like this:

while (flag == 1)
{
    taskYIELD();
}
... rest of code

or perhaps putting a vTaskDelay of few ticks or maybe some other option?

well, it mostly depends on what “rest of code” does. If that’s a predictably bound computation, you can simply create a FreeRTOS timer that checks the flag and executes “rest of code” if flags is != 1. If that is a lengthy computation, however, you can employ a variation of your scheme, namely, a task that is normally suspended and woken via vTaskResume() by your timer routine if the flag is != 1. That’s fairly off-the-shelf-code.