FreeRTOS - Design Patterns for RTOSWhy might a watchdog task fail to reset the system even if a monitored task is stuck?AThe watchdog task has higher priority than the stuck taskBThe system has no idle taskCThe watchdog timer is disabled in FreeRTOSConfig.hDThe monitored task still sends notifications, preventing resetCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand watchdog reset conditionWatchdog resets system only if it detects no notifications from monitored tasks.Step 2: Analyze why reset might not happenIf the stuck task still sends notifications (e.g., from an interrupt), watchdog thinks it is alive.Final Answer:The monitored task still sends notifications, preventing reset -> Option DQuick Check:False notifications prevent watchdog reset [OK]Quick Trick: False notifications can fool the watchdog task [OK]Common Mistakes:Assuming priority affects resetThinking timer config disables resetBelieving idle task absence causes failure
Master "Design Patterns for RTOS" in FreeRTOS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More FreeRTOS Quizzes Debugging and Monitoring - Stack high water mark monitoring - Quiz 11easy Debugging and Monitoring - Stack high water mark monitoring - Quiz 15hard Design Patterns for RTOS - Producer-consumer pattern - Quiz 2easy Design Patterns for RTOS - Task pooling for dynamic workloads - Quiz 15hard Interrupt Management - Deferred interrupt processing architecture - Quiz 6medium Interrupt Management - Critical sections and interrupt disabling - Quiz 4medium Interrupt Management - Critical sections and interrupt disabling - Quiz 14medium Memory Management - Why memory management prevents runtime crashes - Quiz 6medium Task Notifications - Why task notifications are lightweight - Quiz 4medium Task Notifications - ulTaskNotifyTake() for binary/counting notification - Quiz 2easy