[Solved] Examine this FreeRTOS code snippet: taskENTER_CRITICAL(); sharedCount++; // No taskEXIT_CRITICAL() called What issue does this cause? | FreeRTOS

FreeRTOS - Interrupt Management

Examine this FreeRTOS code snippet:

taskENTER_CRITICAL();
sharedCount++;
// No taskEXIT_CRITICAL() called

What issue does this cause?

ATask scheduler is suspended indefinitely

BsharedCount is not incremented correctly

CInterrupts remain disabled, causing system unresponsiveness

DNo issue; code is safe

Step-by-Step Solution

Solution:

Step 1: Understand taskENTER_CRITICAL()
This function disables interrupts to protect critical sections.
Step 2: Missing taskEXIT_CRITICAL()
Without taskEXIT_CRITICAL(), interrupts remain disabled indefinitely.
Step 3: Consequences
System becomes unresponsive as interrupts are blocked, affecting real-time behavior.
Final Answer:
Interrupts remain disabled, causing system unresponsiveness -> Option C
Quick Check:
Always pair taskENTER_CRITICAL() with taskEXIT_CRITICAL() [OK]

Quick Trick: Always match taskENTER_CRITICAL() with taskEXIT_CRITICAL() [OK]

Common Mistakes:

Master "Interrupt Management" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

More FreeRTOS Quizzes

Examine this FreeRTOS code snippet: