Static vs dynamic allocation (configSUPPORT_STATIC_ALLOCATION) in FreeRTOS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable static allocation support in FreeRTOS.

FreeRTOS

#define configSUPPORT_STATIC_ALLOCATION [1]

Drag options to blanks, or click blank then click option'

A0

B-1

C2

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 disables static allocation.

Using 2 enables static-only mode (no dynamic allocation).

Setting configSUPPORT_STATIC_ALLOCATION to 1 enables static allocation support in FreeRTOS.

2fill in blank

medium

Complete the function prototype for creating a task with static allocation.

FreeRTOS

TaskHandle_t xTaskCreateStatic( TaskFunction_t pxTaskCode, const char * const pcName, const uint32_t ulStackDepth, void * const pvParameters, UBaseType_t uxPriority, StackType_t * const [1], StaticTask_t * const pxTaskBuffer );

Drag options to blanks, or click blank then click option'

ApvStack

BpxStack

CpuxStackBuffer

DpxStackPtr

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names causes compilation errors.

Confusing stack buffer with task buffer.

The parameter puxStackBuffer is the pointer to the stack buffer for the task.

3fill in blank

hard

Fix the error in the following code snippet for static task creation.

FreeRTOS

StaticTask_t xTaskBuffer;
StackType_t xStackBuffer[[1]];
xTaskCreateStatic( vTaskCode, "Task", 128, NULL, 2, xStackBuffer, &xTaskBuffer );

Drag options to blanks, or click blank then click option'

A128

B32

C256

D64

Attempts:

3 left

💡 Hint

Common Mistakes

Using a smaller stack buffer than the stack depth causes runtime errors.

Using a larger buffer wastes memory but is safer.

The stack buffer size must match the stack depth parameter (128) to avoid stack overflow or memory issues.

4fill in blank

hard

Fill both blanks to define a static task and its stack correctly.

FreeRTOS

StaticTask_t [1];
StackType_t [2][256];

Drag options to blanks, or click blank then click option'

AmyTaskBuffer

BtaskStack

CxTaskBuffer

DxStackBuffer

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the names causes confusion but not errors.

Using inconsistent names reduces code readability.

Common naming conventions use xTaskBuffer for the task control block and xStackBuffer for the stack array.

5fill in blank

hard

Fill all three blanks to create a static task with correct parameters.

FreeRTOS

TaskHandle_t [1] = xTaskCreateStatic( vTaskFunction, "StaticTask", [2], NULL, 1, [3], &xTaskBuffer );

Drag options to blanks, or click blank then click option'

AxHandle

B128

CxStackBuffer

DmyTask

E64

FpxStackBuffer

Attempts:

3 left

💡 Hint

Common Mistakes

Using mismatched stack sizes causes errors.

Incorrect variable names cause compilation failures.

xHandle stores the task handle, 128 is the stack depth, and xStackBuffer is the stack array pointer.

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