Idle task and idle hook in FreeRTOS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of the idle hook function?

Consider the following FreeRTOS idle hook function code snippet. What will be printed repeatedly when the system is idle?

FreeRTOS

void vApplicationIdleHook(void) {
    static int count = 0;
    count++;
    if (count % 1000 == 0) {
        printf("Idle hook called %d times\n", count);
    }
}

A Idle hook called 1000 times\nIdle hook called 2000 times\nIdle hook called 3000 times\n...

B Idle hook called 1 times\nIdle hook called 2 times\nIdle hook called 3 times\n...

C No output will be printed because idle hook is never called.

D Compilation error due to missing return statement.

💡 Hint

The idle hook runs repeatedly when no other tasks are ready. The count increments each call.

The idle hook function is called repeatedly by the FreeRTOS idle task. The static variable count increments each time. The printf runs every 1000 calls, so output appears at multiples of 1000.

🧠 Conceptual

intermediate

What is the main purpose of the FreeRTOS idle task?

In FreeRTOS, what is the primary role of the idle task?

A To manage memory allocation and deallocation automatically.

B To run user application code with highest priority.

C To execute when no other tasks are ready, keeping the CPU busy or in low power mode.

D To handle interrupts and hardware events.

💡 Hint

Think about what happens when no tasks are ready to run.

The idle task runs only when no other tasks are ready. It can keep the CPU busy or put it into a low power state to save energy.

🔧 Debug

advanced

Why does this idle hook cause a stack overflow?

Examine the following idle hook code. Why might it cause a stack overflow?

FreeRTOS

void vApplicationIdleHook(void) {
    char buffer[1024];
    memset(buffer, 0, sizeof(buffer));
    // Do some processing
}

A There is no stack overflow; code is safe.

B The memset function is not allowed in idle hook and causes error.

C Idle hook cannot declare local variables.

D The buffer is too large for the idle task stack, causing overflow.

💡 Hint

Consider the size of the idle task stack and local variables.

The idle task usually has a small stack size. Declaring a large local buffer (1024 bytes) can overflow the stack, causing crashes.

📝 Syntax

advanced

Which idle hook implementation is syntactically correct?

Choose the syntactically correct FreeRTOS idle hook function implementation.

A void vApplicationIdleHook(void) { /* empty */ }

B void vApplicationIdleHook(void) { return 0; }

C void vApplicationIdleHook(void) { int x =; }

D void vApplicationIdleHook() { while(1) {} }

💡 Hint

Check function signature and valid C syntax.

The idle hook must have the signature void vApplicationIdleHook(void) and return void. Option A matches this and is syntactically correct.

🚀 Application

expert

How to safely perform background cleanup in the idle hook?

You want to perform low priority cleanup tasks in the FreeRTOS idle hook without blocking other tasks. Which approach is best?

A Disable interrupts inside <code>vApplicationIdleHook</code> and run cleanup code.

B Set a flag in <code>vApplicationIdleHook</code> and perform cleanup in a low priority task.

C Perform all cleanup directly inside <code>vApplicationIdleHook</code> with long loops.

D Call <code>vTaskDelay</code> inside <code>vApplicationIdleHook</code> to wait during cleanup.

💡 Hint

Consider responsiveness and what the idle hook should do quickly.

The idle hook should run quickly and not block. Setting a flag and letting a low priority task do cleanup avoids blocking and keeps system responsive.