Memory usage monitoring in FreeRTOS - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Interpreting FreeRTOS heap_4 memory usage output

Given the FreeRTOS heap_4 memory scheme, what does the following output from xPortGetFreeHeapSize() indicate?

FreeRTOS

size_t freeHeap = xPortGetFreeHeapSize();
printf("Free heap size: %u bytes\n", (unsigned int)freeHeap);

A It shows the total free heap memory available for allocation at runtime.

B It shows the total heap memory used by all tasks combined.

C It shows the maximum heap size configured in FreeRTOSConfig.h.

D It shows the stack size of the currently running task.

💡 Hint

Think about what 'free heap size' means in memory management.

The function xPortGetFreeHeapSize() returns the amount of heap memory currently free and available for allocation. It does not show used memory or stack sizes.

🧠 Conceptual

intermediate

Understanding stack overflow detection in FreeRTOS

Which FreeRTOS feature helps detect stack overflow in tasks during runtime?

A Enabling configUSE_IDLE_HOOK to check stack limits.

B Using xPortGetFreeHeapSize() to monitor stack usage.

C configCHECK_FOR_STACK_OVERFLOW set to 1 or 2 enables stack overflow checking.

D Setting configMAX_PRIORITIES to a higher value.

💡 Hint

Look for configuration options related to stack overflow.

FreeRTOS can detect stack overflow if configCHECK_FOR_STACK_OVERFLOW is set to 1 or 2. This enables runtime checks to catch stack overflows.

❓ Troubleshoot

advanced

Diagnosing unexpected heap exhaustion in FreeRTOS

A FreeRTOS system using heap_4 suddenly runs out of heap memory causing task creation failures. Which of the following is the most likely cause?

A configUSE_PREEMPTION set to 0.

B Memory fragmentation due to many small allocations and frees.

C Using xTaskGetTickCount() incorrectly.

D Stack overflow in the idle task.

💡 Hint

Think about how heap_4 manages memory blocks.

Heap_4 uses malloc and free with coalescing but can still suffer fragmentation if many small allocations and frees happen, leading to heap exhaustion.

🔀 Workflow

advanced

Steps to monitor FreeRTOS task stack usage at runtime

What is the correct sequence of steps to monitor the stack usage of a FreeRTOS task during runtime?

A 4,3,2,1

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about how to get data, interpret it, then act on it.

The function uxTaskGetStackHighWaterMark() returns the minimum amount of stack space that remained unused. Comparing it to the total stack size helps detect overflow risks.

✅ Best Practice

expert

Best practice for minimizing heap fragmentation in FreeRTOS

Which approach best minimizes heap fragmentation when using FreeRTOS heap_4 memory scheme in a long-running embedded system?

A Use fixed-size memory pools for dynamic allocations instead of malloc/free.

B Increase configTOTAL_HEAP_SIZE to maximum possible value.

C Disable stack overflow checking to reduce overhead.

D Use heap_1 scheme instead of heap_4.

💡 Hint

Think about avoiding fragmentation by controlling allocation sizes.

Using fixed-size memory pools avoids fragmentation because allocations and frees are uniform and predictable, unlike malloc/free which can fragment heap.