Idle task and idle hook in FreeRTOS - Step-by-Step Execution

Concept Flow - Idle task and idle hook

System starts FreeRTOS scheduler

↓

All tasks blocked or suspended?

No→Run highest priority ready task

Yes↓

Run Idle Task

↓

Idle Hook called?

Yes→Execute user Idle Hook function

No↓

Idle Task loops back waiting for tasks

The FreeRTOS scheduler runs tasks by priority. When no tasks are ready, the Idle Task runs. If an Idle Hook is defined, it runs inside the Idle Task loop.

Execution Sample

FreeRTOS

void vApplicationIdleHook(void) {
    // User code here
    // e.g., enter low power mode
}

// FreeRTOS runs idle task when no other task is ready

This code shows the Idle Hook function that runs inside the Idle Task when the system is idle.

Execution Table

Step	Condition	Action	Output
1	Scheduler started	Run highest priority ready task	Task1 runs
2	Task1 blocked or suspended	Check other tasks	No ready tasks
3	No ready tasks	Run Idle Task	Idle Task runs
4	Idle Hook defined?	Yes	Idle Hook function called
5	Idle Hook executes user code	User code runs	e.g., low power mode entered
6	Idle Hook ends	Idle Task loops	Wait for tasks to become ready
7	New task ready	Scheduler switches to new task	New task runs

💡 Idle Task runs continuously when no other tasks are ready; Idle Hook runs inside Idle Task if defined

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 7
Ready Tasks	Task1 ready	No ready tasks	No ready tasks	No ready tasks	New task ready
Idle Task State	Not running	Not running	Running	Running	Not running
Idle Hook State	Not running	Not running	Not running	Running	Not running

Key Moments - 3 Insights

Why does the Idle Task run only when no other tasks are ready?

Because FreeRTOS always runs the highest priority ready task. The Idle Task has the lowest priority and runs only when no other tasks are ready, as shown in execution_table row 3.

What happens if the Idle Hook is not defined?

The Idle Task runs an empty loop doing nothing. The Idle Hook function is only called if defined, as shown in execution_table row 4.

Can the Idle Hook be used to save power?

Yes, the Idle Hook is a good place to put code to enter low power mode, as shown in execution_table row 5.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the Idle Hook function run?

A Step 7

B Step 2

C Step 4

D Step 1

💡 Hint

Check the 'Action' column in execution_table row 4 where Idle Hook is called.

According to variable_tracker, what is the state of 'Ready Tasks' after Step 3?

A No ready tasks

B New task ready

C Task1 ready

D Idle Task running

💡 Hint

Look at the 'Ready Tasks' row and the 'After Step 3' column in variable_tracker.

If a new task becomes ready at Step 7, what happens to the Idle Task?

A Idle Task continues running

B Idle Task suspends and new task runs

C Idle Hook runs again

D System resets

💡 Hint

See execution_table row 7 describing scheduler switching to new task.

Concept Snapshot

Idle Task runs when no other tasks are ready.
It has the lowest priority.
Idle Hook is a user function called inside Idle Task loop.
Use Idle Hook for low power or background work.
If no Idle Hook, Idle Task loops doing nothing.

Full Transcript

FreeRTOS runs tasks based on priority. When no tasks are ready, the Idle Task runs. The Idle Task has the lowest priority and runs continuously until a task becomes ready. If the user defines an Idle Hook function, FreeRTOS calls it inside the Idle Task loop. This hook is useful for running background code or entering low power mode. The execution table shows the scheduler starting, running tasks, then running the Idle Task and Idle Hook when no tasks are ready. Variables track which tasks are ready and the state of the Idle Task and Idle Hook. Key moments clarify why the Idle Task runs only when no other tasks are ready, what happens if the Idle Hook is not defined, and how the Idle Hook can save power. The visual quiz tests understanding of when the Idle Hook runs, the state of ready tasks, and what happens when a new task becomes ready.

Practice

1.

What is the main purpose of the FreeRTOS idle task?

easy

A. It runs when no other tasks are ready to run

B. It handles all interrupts in the system

C. It manages memory allocation for tasks

D. It schedules tasks based on priority

Solution

1. Step 1: Understand the role of the idle task

   The idle task runs only when no other higher priority tasks are ready to execute.

2. Step 2: Compare options with the idle task role

   Options A, B, and C describe other system functions, not the idle task's main role.

3. Final Answer:

   It runs when no other tasks are ready to run -> Option A

4. Quick Check:

   Idle task runs when system is idle = D [OK]

Hint: Idle task runs only when CPU is free from other tasks [OK]

Common Mistakes:

• Confusing idle task with interrupt handler
• Thinking idle task manages memory
• Assuming idle task schedules other tasks

2.

Which of the following is the correct way to enable the idle hook in FreeRTOS?

#define configUSE_IDLE_HOOK  ???

easy

A. NULL

B. 0

C. TRUE

D. 1

Solution

1. Step 1: Identify the config macro for idle hook

   The macro configUSE_IDLE_HOOK enables or disables the idle hook feature.

2. Step 2: Determine the correct value to enable it

   Setting configUSE_IDLE_HOOK to 1 enables the idle hook; 0 disables it.

3. Final Answer:

   1 -> Option D

4. Quick Check:

   Enable idle hook = 1 [OK]

Hint: Enable idle hook by setting configUSE_IDLE_HOOK to 1 [OK]

Common Mistakes:

• Using 0 disables the idle hook
• Using NULL or TRUE are invalid for this macro
• Confusing with other config macros

3.

Given the following code snippet, what will be printed?

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

Assuming the idle hook is enabled and the system is idle for 5 cycles, what is the output?

medium

A. No output

B. Idle hook called 5 times

C. Idle hook called 3 times

D. Idle hook called 1 time

Solution

1. Step 1: Analyze the idle hook function behavior

   The function increments count each time it runs and prints only when count == 3.

2. Step 2: Determine output after 5 idle cycles

   On the 3rd call, it prints the message once. On calls 4 and 5, no print occurs because the condition is only for count == 3.

3. Final Answer:

   Idle hook called 3 times -> Option C

4. Quick Check:

   Print only at count 3 = A [OK]

Hint: Print triggers only once when count equals 3 [OK]

Common Mistakes:

• Assuming print happens every call
• Confusing count with number of prints
• Expecting output for all 5 cycles

4.

Identify the error in this FreeRTOS idle hook implementation:

void vApplicationIdleHook(void) {
    int count = 0;
    count++;
    if (count == 5) {
        // Do something
    }
}

medium

A. Idle hook function must return an int

B. count should be declared static to retain its value

C. count variable should be global

D. Idle hook cannot use if statements

Solution

1. Step 1: Understand variable lifetime in idle hook

   The variable count is declared inside the function, so it resets to 0 every call.

2. Step 2: Fix variable to retain value across calls

   Declaring count as static keeps its value between calls, allowing counting.

3. Final Answer:

   count should be declared static to retain its value -> Option B

4. Quick Check:

   Use static for persistent variables in idle hook [OK]

Hint: Use static variables to keep count across idle hook calls [OK]

Common Mistakes:

• Declaring count as local resets it every call
• Expecting idle hook to return a value
• Thinking global variable is required

5.

You want to perform a low-priority background task every time the system is idle, but only after 10 idle cycles. Which is the best way to implement this using the idle hook?

hard

A. Use a static counter in vApplicationIdleHook and run the task when counter reaches 10, then reset it

B. Create a high priority task that waits for 10 ticks before running

C. Run the background task directly in the main function loop

D. Disable the idle hook and run the task in the timer interrupt

Solution

1. Step 1: Understand the requirement for background task timing

   The task should run during idle time, specifically after 10 idle cycles.

2. Step 2: Use idle hook with a static counter

   Using a static counter inside vApplicationIdleHook allows counting idle cycles and running the task at the right time.

3. Step 3: Evaluate other options

   High priority task or timer interrupt are not suitable for low-priority background work during idle. Running in main loop is not reliable in FreeRTOS.

4. Final Answer:

   Use a static counter in vApplicationIdleHook and run the task when counter reaches 10, then reset it -> Option A

5. Quick Check:

   Idle hook + static counter for delayed background task [OK]

Hint: Count idle calls with static variable, run task at target count [OK]

Common Mistakes:

• Using high priority task defeats idle purpose
• Running task in main loop ignores FreeRTOS scheduling
• Disabling idle hook loses idle time execution