vTaskDelay() for periodic tasks in FreeRTOS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Understanding vTaskDelay() behavior

What will be the output timing behavior of the following FreeRTOS task code snippet?

void vTaskFunction(void *pvParameters) {
    for (;;) {
        // Task code here
        vTaskDelay(pdMS_TO_TICKS(1000));
        // Print or toggle an LED
    }
}

Assuming the tick rate is 1ms, how often does the task unblock?

FreeRTOS

void vTaskFunction(void *pvParameters) {
    for (;;) {
        vTaskDelay(pdMS_TO_TICKS(1000));
        // action
    }
}

A The task unblocks every 1000 milliseconds (1 second) after the delay.

B The task unblocks immediately without any delay.

C The task unblocks every 1 millisecond.

D The task never unblocks because vTaskDelay blocks indefinitely.

💡 Hint

Remember that vTaskDelay() delays the task for the specified tick count.

The function vTaskDelay(pdMS_TO_TICKS(1000)) causes the task to enter the Blocked state for 1000 ticks. Since the tick rate is 1ms, this equals 1000 milliseconds or 1 second. After this delay, the task unblocks and runs again.

❓ Predict Output

intermediate

Effect of vTaskDelay on task periodicity

Consider a FreeRTOS task that performs some work taking 200ms and then calls vTaskDelay(pdMS_TO_TICKS(1000)). How often will the task run?

FreeRTOS

void vTaskFunction(void *pvParameters) {
    for (;;) {
        // Work taking 200ms
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

A The task runs every 1200 milliseconds (200ms work + 1000ms delay).

B The task runs every 1000 milliseconds exactly.

C The task runs every 200 milliseconds.

D The task runs continuously without delay.

💡 Hint

Think about how vTaskDelay() affects the task after the work is done.

The task does 200ms of work, then calls vTaskDelay() for 1000ms. So the total cycle time is 200ms + 1000ms = 1200ms.

🔧 Debug

advanced

Why does the task drift in timing?

A developer writes this FreeRTOS task to run every 1000ms:

void vTaskFunction(void *pvParameters) {
    for (;;) {
        vTaskDelay(pdMS_TO_TICKS(1000));
        // Do work
    }
}

But the task execution drifts over time, running later and later. Why?

A Because vTaskDelay blocks the task forever.

B Because the tick rate is too fast causing timing errors.

C Because vTaskDelay delays from the time it is called, so work time adds to the period causing drift.

D Because the task priority is too low to run on time.

💡 Hint

Consider when the delay starts counting relative to the work done.

vTaskDelay() delays the task for a fixed time starting from when it is called. Since the work is done before the delay, the total period is work time + delay time. This causes the task to drift later each cycle.

🚀 Application

advanced

Implementing a fixed periodic task with vTaskDelayUntil

Which code snippet correctly implements a task that runs exactly every 1000ms without drift?

A

TickType_t xLastWakeTime = xTaskGetTickCount();
for (;;) {
    vTaskDelay(pdMS_TO_TICKS(1000));
    // work
}

B

TickType_t xLastWakeTime = xTaskGetTickCount();
for (;;) {
    vTaskDelayUntil(&xLastWakeTime, pdMS_TO_TICKS(1000));
    // work
}

C

for (;;) {
    vTaskDelayUntil(NULL, pdMS_TO_TICKS(1000));
    // work
}

D

for (;;) {
    vTaskDelay(1000);
    // work
}

💡 Hint

Use the function designed for fixed periodic delays.

vTaskDelayUntil() uses a reference time to ensure the task runs at fixed intervals, preventing drift. Option B correctly initializes xLastWakeTime and uses vTaskDelayUntil().

🧠 Conceptual

expert

Why is vTaskDelay not ideal for precise periodic tasks?

Why might vTaskDelay() be unsuitable for tasks that require precise periodic execution?

A Because it disables interrupts during the delay period.

B Because it blocks the task indefinitely without timeout.

C Because it requires the task to have the highest priority to work.

D Because it delays relative to when it is called, causing cumulative timing errors if task execution time varies.

💡 Hint

Think about how the delay start time relates to task execution time.

vTaskDelay() delays the task for a fixed time starting from the call moment. If the task execution time varies, the delay accumulates causing drift. For precise periodic timing, vTaskDelayUntil() is preferred.