Static vs dynamic allocation (configSUPPORT_STATIC_ALLOCATION) in FreeRTOS - Hands-On Comparison

Static vs Dynamic Allocation in FreeRTOS

📖 Scenario: You are working on a small embedded system project using FreeRTOS. You need to create a task that blinks an LED. You want to understand how to create this task using both static and dynamic memory allocation methods.

🎯 Goal: Build a FreeRTOS program that creates a task to blink an LED using static allocation first, then add a configuration variable to switch between static and dynamic allocation, and finally implement the task creation logic accordingly. You will print a message to confirm which allocation method is used.

📋 What You'll Learn

Create a task control block and stack for static allocation

Add a configuration variable configSUPPORT_STATIC_ALLOCATION to enable or disable static allocation

Use xTaskCreateStatic when static allocation is enabled and xTaskCreate when disabled

Print the allocation method used

💡 Why This Matters

🌍 Real World

Embedded systems often have limited memory. Choosing static or dynamic allocation affects memory usage and system stability.

💼 Career

Understanding FreeRTOS task creation and memory allocation is essential for embedded software developers working on real-time applications.

1

Create static task control block and stack

Create a static task control block called xTaskBuffer and a static stack array called xStack with size 128 for the task.

FreeRTOS

# Create a static task control block and stack array
// Your code here

Hint

Use StaticTask_t for the task control block and StackType_t array for the stack.

2

Add configSUPPORT_STATIC_ALLOCATION variable

Create a constant integer variable called configSUPPORT_STATIC_ALLOCATION and set it to 1 to enable static allocation.

FreeRTOS

StaticTask_t xTaskBuffer;
StackType_t xStack[128];
// Define configSUPPORT_STATIC_ALLOCATION variable
// Your code here

Hint

Use const int to define the configuration variable.

3

Create the task using static or dynamic allocation

Write code to create a task called vBlinkTask with priority 1 and stack size 128. Use xTaskCreateStatic if configSUPPORT_STATIC_ALLOCATION is 1, otherwise use xTaskCreate. Use xTaskBuffer and xStack for static allocation parameters.

FreeRTOS

StaticTask_t xTaskBuffer;
StackType_t xStack[128];
const int configSUPPORT_STATIC_ALLOCATION = 1;

// Create the task using static or dynamic allocation
// Your code here

Hint

Use an if statement to choose between xTaskCreateStatic and xTaskCreate.

4

Print which allocation method is used

Print "Using static allocation" if configSUPPORT_STATIC_ALLOCATION is 1, otherwise print "Using dynamic allocation".

FreeRTOS

StaticTask_t xTaskBuffer;
StackType_t xStack[128];
const int configSUPPORT_STATIC_ALLOCATION = 1;

void vBlinkTask(void *pvParameters) {
    for(;;) {
        // Toggle LED code here
        vTaskDelay(pdMS_TO_TICKS(500));
    }
}

TaskHandle_t xHandle = NULL;
if (configSUPPORT_STATIC_ALLOCATION == 1) {
    xHandle = xTaskCreateStatic(
        vBlinkTask,
        "Blink",
        128,
        NULL,
        1,
        xStack,
        &xTaskBuffer
    );
} else {
    xTaskCreate(
        vBlinkTask,
        "Blink",
        128,
        NULL,
        1,
        &xHandle
    );
}

// Print allocation method
// Your code here

Hint

Use printf inside the if and else blocks to print the messages.

Practice

1. What does enabling configSUPPORT_STATIC_ALLOCATION in FreeRTOS do?

easy

A. Disables task creation completely.

B. Forces all tasks to use dynamic memory allocation.

C. Automatically increases heap size at runtime.

D. Allows tasks to be created using user-provided fixed memory buffers.

Solution

1. Step 1: Understand configSUPPORT_STATIC_ALLOCATION purpose

   This option enables static allocation, meaning the user provides memory buffers for tasks instead of using heap.

2. Step 2: Compare with other options

   The other options describe disabling tasks, heap size changes, or forcing dynamic allocation, which are incorrect.

3. Final Answer:

   Allows tasks to be created using user-provided fixed memory buffers. -> Option D

4. Quick Check:

   Static allocation = user buffers [OK]

Hint: Static allocation means you provide memory buffers [OK]

Common Mistakes:

• Confusing static with dynamic allocation
• Thinking it disables task creation
• Assuming it changes heap size automatically

2. Which of the following is the correct way to declare a task using static allocation in FreeRTOS?

easy

A. xTaskCreateStatic(TaskFunction, "Task", 100, NULL, 1, stackBuffer, &taskBuffer);

B. xTaskCreate(TaskFunction, "Task", 100, NULL, 1, NULL);

C. xTaskCreateDynamic(TaskFunction, "Task", 100, NULL, 1, &taskHandle);

D. xTaskCreateStatic(TaskFunction, "Task", 100, NULL, 1, NULL, NULL);

Solution

1. Step 1: Identify static allocation function

   FreeRTOS provides xTaskCreateStatic for static allocation, requiring stack and task buffers.

2. Step 2: Check parameters

   xTaskCreateStatic(TaskFunction, "Task", 100, NULL, 1, stackBuffer, &taskBuffer); correctly passes stackBuffer and taskBuffer pointers. xTaskCreate uses dynamic allocation. There is no xTaskCreateDynamic function. Passing NULL buffers is incorrect.

3. Final Answer:

   xTaskCreateStatic(TaskFunction, "Task", 100, NULL, 1, stackBuffer, &taskBuffer); -> Option A

4. Quick Check:

   Static task creation needs buffers [OK]

Hint: Use xTaskCreateStatic with buffers for static tasks [OK]

Common Mistakes:

• Using xTaskCreate instead of xTaskCreateStatic
• Passing NULL for buffers in static allocation
• Confusing dynamic and static creation functions

3. Given the following code snippet with configSUPPORT_STATIC_ALLOCATION enabled, what will be the output?

StaticTask_t taskBuffer;
StackType_t stackBuffer[128];

void TaskFunction(void *params) {
  printf("Task running\n");
  vTaskDelete(NULL);
}

int main() {
  TaskHandle_t taskHandle = xTaskCreateStatic(TaskFunction, "MyTask", 128, NULL, 1, stackBuffer, &taskBuffer);
  vTaskStartScheduler();
  return 0;
}

medium

A. Compilation error due to missing heap

B. Task running

C. No output, scheduler never starts

D. Runtime error due to NULL stack

Solution

1. Step 1: Analyze static task creation

   The task is created statically with valid stack and task buffers, so it will run correctly.

2. Step 2: Check scheduler and task behavior

   The scheduler starts, runs the task which prints "Task running", then deletes itself. No errors expected.

3. Final Answer:

   Task running -> Option B

4. Quick Check:

   Static task runs and prints output [OK]

Hint: Static tasks run if buffers are valid and scheduler starts [OK]

Common Mistakes:

• Assuming heap is required for static tasks
• Thinking scheduler won't start without dynamic allocation
• Confusing NULL stack with valid buffer

4. Identify the error in this static task creation code snippet:

StaticTask_t taskBuffer;
StackType_t stackBuffer[100];

xTaskCreateStatic(TaskFunction, "Task", 100, NULL, 1, NULL, &taskBuffer);

medium

A. Function name is incorrect; should be xTaskCreate.

B. Task buffer pointer is NULL, causing invalid task control block.

C. Stack buffer pointer is NULL, causing invalid stack memory.

D. Task priority is invalid (should be zero).

Solution

1. Step 1: Check parameters passed to xTaskCreateStatic

   The stack buffer pointer is NULL, which means no memory is provided for the task's stack.

2. Step 2: Understand consequences of NULL stack buffer

   Without a valid stack buffer, the task cannot run properly and will cause errors.

3. Final Answer:

   Stack buffer pointer is NULL, causing invalid stack memory. -> Option C

4. Quick Check:

   Stack buffer must not be NULL [OK]

Hint: Stack buffer pointer must be valid, not NULL [OK]

Common Mistakes:

• Passing NULL for stack buffer
• Confusing task buffer with stack buffer
• Incorrect function name usage

5. You want to create a FreeRTOS task that must never fail due to memory fragmentation or heap exhaustion. Which approach is best and why?

hard

A. Use static allocation with user-provided buffers for predictability.

B. Mix static and dynamic allocation to balance memory usage.

C. Use dynamic allocation with a large heap to avoid failures.

D. Disable task deletion to prevent memory leaks.

Solution

1. Step 1: Understand memory failure causes in FreeRTOS

   Dynamic allocation can fail due to heap fragmentation or exhaustion, causing task creation failure.

2. Step 2: Evaluate static allocation benefits

   Static allocation uses fixed buffers provided by the user, ensuring memory is reserved and predictable, preventing allocation failures.

3. Step 3: Compare other options

   Using dynamic allocation with a large heap still risks fragmentation failures; mixing allocation methods adds unnecessary complexity; disabling task deletion is unrelated to allocation issues.

4. Final Answer:

   Use static allocation with user-provided buffers for predictability. -> Option A

5. Quick Check:

   Static allocation prevents heap failures [OK]

Hint: Static allocation avoids heap fragmentation failures [OK]

Common Mistakes:

• Assuming large heap solves all allocation issues
• Mixing allocation methods without clear reason
• Confusing task deletion with allocation safety