freertos-kernel-debug

# FreeRTOS Kernel Debug ## Overview Use this skill to debug FreeRTOS by proving tick, scheduler state, task stacks, heap, ISR boundaries, and synchronization ownership. Many FreeRTOS failures are contract violations around interrupt priority or blocking context. ## When To Use Use this skill when: - The user is debugging FreeRTOS tasks, queues, semaphores, mutexes, timers, event groups, streams, or task notifications. - The issue involves hard faults, hangs, missed ticks, watchdog resets, stack overflow, heap exhaustion, priority inversion, or ISR API misuse. - The target uses vendor HAL callbacks, Cortex-M interrupt priorities, trace tools, or multiple heap implementations. Do not use this skill for RTOS-agnostic firmware architecture questions. Use `rtos-debug` for broader RTOS triage. ## First Questions Ask for: - FreeRTOS version, port, MCU, tick rate, heap implementation, and config file. - Task list with priorities, stack sizes, states, and high-water marks. - Interrupt priorities, `configMAX_SYSCALL_INTERRUPT_PRIORITY`, and ISR APIs. - Current symptom, fault dump, watchdog reason, trace, or scheduler snapshot. - Whether assertions, stack overflow hook, malloc failed hook, and trace are on. ## Debug Workflow 1. Enable kernel evidence. Turn on `configASSERT`, stack overflow checks, malloc failed hook, and trace-friendly task names where possible. 1. Prove the tick and scheduler. Confirm SysTick/timer setup, interrupt priority, scheduler start, ...