Bird
0
0

After switching from heap_1 to heap_2, your FreeRTOS application fails to link. What is the most probable reason?

medium📝 Debug Q7 of 15
FreeRTOS - Memory Management
After switching from heap_1 to heap_2, your FreeRTOS application fails to link. What is the most probable reason?
Aheap_2.c file was not added to the project source files
BconfigFRTOS_MEMORY_SCHEME was not changed to 2
Cheap_1.c is still included causing conflicts
DvPortMalloc() prototype changed between heap schemes
Step-by-Step Solution
Solution:

  1. Step 1: Understand linking errors

    Link errors usually happen if required source files are missing from the build.

  2. Step 2: Check heap_2 requirements

    heap_2.c must be added to the project source files; forgetting this causes link failure.

  3. Final Answer:

    heap_2.c file missing from project -> Option A

  4. Quick Check:

    Missing heap_2.c causes link failure = heap_2.c file was not added to the project source files [OK]
Quick Trick: Add heap_2.c source file when switching heap schemes [OK]
Common Mistakes:
  • Not changing config macro
  • Leaving heap_1.c included
  • Assuming function prototypes differ

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More FreeRTOS Quizzes
Debugging and Monitoring - Trace hooks and FreeRTOS+Trace - Quiz 14medium Debugging and Monitoring - Stack high water mark monitoring - Quiz 12easy Debugging and Monitoring - Stack high water mark monitoring - Quiz 3easy Interrupt Management - Nested interrupt handling - Quiz 11easy Interrupt Management - ISR-safe API functions (FromISR suffix) - Quiz 10hard Interrupt Management - Deferred interrupt processing architecture - Quiz 12easy Task Notifications - xTaskNotifyGive() as lightweight semaphore - Quiz 13medium Task Notifications - xTaskNotify() with value - Quiz 12easy Task Notifications - Task notification vs queue performance - Quiz 15hard Task Notifications - Why task notifications are lightweight - Quiz 1easy