Resource manager task pattern in FreeRTOS - Step-by-Step Execution

Concept Flow - Resource manager task pattern

Start Resource Manager Task

↓

Wait for Request Queue

↓

Receive Request

↓

Process Request

↓

Send Response

↓

Loop Back to Wait

The resource manager task waits for requests, processes them one by one, sends responses, and loops back to wait for more.

Execution Sample

FreeRTOS

void ResourceManagerTask(void *pvParameters) {
  Request_t req;
  for (;;) {
    if (xQueueReceive(requestQueue, &req, portMAX_DELAY) == pdTRUE) {
      ProcessRequest(&req);
      xQueueSend(responseQueue, &req.response, 0);
    }
  }
}

This task waits for requests on a queue, processes each request, then sends a response back.

Execution Table

Step	Action	Queue Receive Result	Request Data	Process Request	Send Response	Loop Back
1	Wait for request	No data yet	-	-	-	Waiting
2	Receive request	Success	Request 1	Process Request 1	Send Response 1	Loop back
3	Wait for request	No data yet	-	-	-	Waiting
4	Receive request	Success	Request 2	Process Request 2	Send Response 2	Loop back
5	Wait for request	No data yet	-	-	-	Waiting
Exit	No exit in infinite loop	-	-	-	-	Task runs forever

💡 The task runs in an infinite loop, always waiting for new requests.

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
req	empty	Request 1 data	Request 2 data	Request 2 data
requestQueue	contains requests	Request 2 remains	empty or new requests	varies
responseQueue	empty	Response 1 added	Response 2 added	contains responses

Key Moments - 3 Insights

Why does the task use an infinite loop with xQueueReceive?

Because the task must keep running to handle all incoming requests, as shown in execution_table rows 2 and 4 where it loops back to wait again.

What happens if no request is available in the queue?

The task blocks on xQueueReceive (portMAX_DELAY), waiting without using CPU, as seen in execution_table rows 1, 3, and 5.

How does the task send a response after processing?

It uses xQueueSend to put the response in the responseQueue immediately after processing, as shown in execution_table steps 2 and 4.

Visual Quiz - 3 Questions

Look at the execution_table at step 2. What is the value of 'req' after receiving the request?

A empty

B Request 1 data

C Response 1 data

D Request 2 data

💡 Hint

Check the 'Request Data' column at step 2 in the execution_table.

At which step does the task send the response for Request 2?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'Send Response' column for Request 2 in the execution_table.

If the requestQueue is empty, what does the task do according to the execution_table?

A Blocks and waits for a request

B Exits the loop

C Processes a default request

D Sends an empty response

💡 Hint

See the 'Queue Receive Result' and 'Loop Back' columns in steps 1, 3, and 5.

Concept Snapshot

Resource Manager Task Pattern in FreeRTOS:
- Runs an infinite loop waiting on a request queue
- Uses xQueueReceive with portMAX_DELAY to block until a request arrives
- Processes each request sequentially
- Sends response via a response queue
- Ensures safe, serialized access to shared resources

Full Transcript

The Resource Manager Task pattern in FreeRTOS uses a dedicated task that runs forever in a loop. It waits for requests by blocking on a queue receive call. When a request arrives, the task processes it and sends a response back through another queue. This pattern ensures only one task accesses the shared resource at a time, avoiding conflicts. The task blocks when no requests are available, saving CPU time. After handling each request, it loops back to wait for the next one, running continuously.

Practice

1. What is the main purpose of the Resource Manager Task Pattern in FreeRTOS?

easy

A. To centralize control of shared resources and prevent conflicts

B. To create multiple tasks accessing resources directly

C. To increase CPU usage by running more tasks simultaneously

D. To eliminate the need for task synchronization mechanisms

Solution

1. Step 1: Understand resource sharing challenges

   When multiple tasks access shared resources directly, conflicts and data corruption can occur.

2. Step 2: Role of Resource Manager Task

   The Resource Manager Task centralizes access, so tasks send requests to it instead of accessing resources directly, preventing conflicts.

3. Final Answer:

   To centralize control of shared resources and prevent conflicts -> Option A

4. Quick Check:

   Centralized control = Prevent conflicts [OK]

Hint: Resource manager centralizes resource access to avoid conflicts [OK]

Common Mistakes:

• Thinking tasks access resources directly
• Assuming it increases CPU usage
• Believing it removes synchronization needs

2. Which of the following is the correct way to send a request to a Resource Manager Task in FreeRTOS?

easy

A. Using a queue to send a request message to the manager task

B. Calling the resource manager function without synchronization

C. Directly accessing the shared resource variable

D. Using global variables without any task communication

Solution

1. Step 1: Identify communication method

   Resource Manager Tasks typically receive requests via queues to serialize access.

2. Step 2: Evaluate options

   Only Using a queue to send a request message to the manager task uses a queue to send requests, which is the correct and safe method.

3. Final Answer:

   Using a queue to send a request message to the manager task -> Option A

4. Quick Check:

   Queue communication = Correct request method [OK]

Hint: Use queues to send requests to resource manager task [OK]

Common Mistakes:

• Accessing shared variables directly
• Ignoring synchronization
• Using global variables without communication

3. Given the following FreeRTOS code snippet, what will be the output?

typedef struct {
  int command;
  int data;
} RequestMessage;

QueueHandle_t resourceQueue;

void ResourceManagerTask(void *params) {
  RequestMessage req;
  while (1) {
    if (xQueueReceive(resourceQueue, &req, portMAX_DELAY) == pdPASS) {
      if (req.command == 1) {
        printf("Processed data: %d\n", req.data * 2);
      }
    }
  }
}

void ClientTask(void *params) {
  RequestMessage msg = {1, 5};
  xQueueSend(resourceQueue, &msg, 0);
  vTaskDelete(NULL);
}

medium

A. Processed data: 5

B. Processed data: 10

C. No output, queue is empty

D. Runtime error due to invalid queue

Solution

1. Step 1: Analyze ClientTask sending message

   ClientTask sends a message with command=1 and data=5 to the resourceQueue.

2. Step 2: Analyze ResourceManagerTask processing

   ResourceManagerTask receives the message, checks command==1, then prints data*2 = 5*2 = 10.

3. Final Answer:

   Processed data: 10 -> Option B

4. Quick Check:

   Data 5 doubled = 10 output [OK]

Hint: Multiply data by 2 when command is 1 [OK]

Common Mistakes:

• Confusing data value with output
• Assuming no message received
• Ignoring the multiplication by 2

4. Identify the bug in this Resource Manager Task code snippet:

void ResourceManagerTask(void *params) {
  RequestMessage req;
  while (1) {
    if (xQueueReceive(resourceQueue, &req, 0) == pdPASS) {
      if (req.command == 1) {
        // Process command
      }
    }
  }
}

What is the problem?

medium

A. xQueueReceive should not be used in Resource Manager Task

B. RequestMessage struct is not defined

C. ResourceManagerTask should not use a while loop

D. Using zero block time causes missed messages if queue is empty

Solution

1. Step 1: Understand xQueueReceive block time

   Using 0 as block time means the call returns immediately if queue is empty, possibly missing messages.

2. Step 2: Effect on Resource Manager Task

   The task may spin without waiting, causing high CPU usage and missed processing.

3. Final Answer:

   Using zero block time causes missed messages if queue is empty -> Option D

4. Quick Check:

   Zero block time = possible missed messages [OK]

Hint: Use portMAX_DELAY to wait for messages in resource manager [OK]

Common Mistakes:

• Ignoring block time effect
• Thinking struct is undefined
• Believing while loop is wrong

5. You want to design a Resource Manager Task that handles multiple resource types (e.g., UART, SPI) with different commands. Which approach best applies the Resource Manager Task Pattern to handle this efficiently?

hard

A. Create separate manager tasks for each resource type and let clients send requests directly to each

B. Let clients access resources directly with mutexes protecting each resource

C. Use a single queue with a message struct containing resource type and command fields, then switch-case inside the manager task

D. Use global variables to store resource states and update them without task communication

Solution

1. Step 1: Consider centralized control for multiple resources

   A single Resource Manager Task can handle multiple resource types by differentiating requests.

2. Step 2: Use message struct with resource type and command

   This allows the manager task to use a switch-case to process requests efficiently and safely.

3. Final Answer:

   Use a single queue with a message struct containing resource type and command fields, then switch-case inside the manager task -> Option C

4. Quick Check:

   Single queue + message struct = efficient multi-resource management [OK]

Hint: Use message struct with resource type and switch-case in manager [OK]

Common Mistakes:

• Creating multiple manager tasks unnecessarily
• Allowing direct resource access with mutexes
• Using global variables without communication