Choosing the right heap scheme in FreeRTOS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Heap_1 scheme behavior on free() calls

What happens when you call vPortFree() on a pointer allocated with the heap_1 scheme in FreeRTOS?

FreeRTOS

void *ptr = pvPortMalloc(100);
vPortFree(ptr);

A The <code>vPortFree()</code> call does nothing; memory is not freed.

B The memory is freed and available for future allocations.

C A runtime error occurs because <code>heap_1</code> does not support <code>vPortFree()</code>.

D The system crashes immediately.

💡 Hint

Remember that heap_1 is the simplest heap scheme in FreeRTOS.

The heap_1 scheme in FreeRTOS provides a very simple allocator that does not support freeing memory. The vPortFree() function is implemented as a no-op, so memory is never reclaimed.

❓ Predict Output

intermediate

Behavior of heap_4 with fragmentation

Given the heap_4 scheme in FreeRTOS, what is the expected behavior when many small allocations and frees cause fragmentation?

FreeRTOS

void *a = pvPortMalloc(10);
void *b = pvPortMalloc(20);
vPortFree(a);
void *c = pvPortMalloc(15);

A The allocator merges adjacent free blocks to reduce fragmentation.

B The allocator never reuses freed blocks, causing fragmentation to grow.

C The allocator can reuse freed blocks and avoid fragmentation effectively.

D The allocator crashes when fragmentation occurs.

💡 Hint

Think about how heap_4 manages free blocks.

heap_4 merges adjacent free blocks to reduce fragmentation and supports both allocation and freeing of memory.

🧠 Conceptual

advanced

Choosing heap scheme for real-time constraints

Which FreeRTOS heap scheme is best suited for applications with strict real-time constraints and minimal memory management overhead?

A heap_2

B heap_5

C heap_1

D heap_3

💡 Hint

Consider which scheme avoids complex operations during allocation.

heap_1 is the simplest scheme with no support for freeing memory, making it very predictable and fast, suitable for strict real-time systems.

❓ Predict Output

advanced

Effect of using heap_3 on memory fragmentation

What is the effect of using heap_3 scheme in FreeRTOS on memory fragmentation?

FreeRTOS

void *p1 = pvPortMalloc(50);
void *p2 = pvPortMalloc(100);
vPortFree(p1);
void *p3 = pvPortMalloc(40);

A Fragmentation is minimized by merging free blocks internally.

B Fragmentation behavior depends on the standard C library allocator.

C Fragmentation is worse because <code>heap_3</code> does not support freeing memory.

D The system crashes due to incompatible memory management.

💡 Hint

Recall what heap_3 uses internally for allocation.

heap_3 simply wraps the standard C library malloc and free, so fragmentation behavior depends on the C library implementation.

🧠 Conceptual

expert

Selecting heap scheme for multi-core FreeRTOS system

In a multi-core FreeRTOS system where multiple tasks on different cores allocate and free memory concurrently, which heap scheme is most appropriate to avoid race conditions and ensure thread safety?

A heap_4

B heap_2

C heap_1

D heap_5

💡 Hint

Consider which heap scheme supports multiple heaps and thread safety.

heap_5 supports multiple heaps and is designed for thread-safe allocation in complex systems like multi-core processors.