embedded-debug-entry

# Embedded Debug Entry ## Overview Use this skill as the first stop for embedded debugging. The agent should classify the target, failure phase, access method, toolchain, and risk level, then route to the narrowest specialized skill instead of guessing from incomplete context. ## When To Use Use this skill when: - The user reports an embedded device, MCU, board, firmware, RTOS, bootloader, or peripheral issue. - The architecture or debugging path is unclear. - The task might involve flashing, serial logs, SWD/JTAG, UART, ADB, bootloaders, low power, or hardware signals. Do not use this skill when the user already named a more specific skill path, such as Cortex-M HardFault, 8051 timer, RISC-V trap, or embedded Linux SSH login. ## First Questions Ask only what is needed to route: - Target type: MCU, embedded Linux device, mixed SoC, module, or unknown board. - Architecture or chip family: Cortex-M, Cortex-R, RISC-V, 8051, Linux-capable ARM, or unknown. - Failure phase: cannot connect, cannot flash, no boot, crash/fault, no logs, peripheral failure, RTOS issue, bootloader issue, low-power issue. - Available access: SWD/JTAG, serial UART, SSH, ADB, Telnet, local console, logic analyzer, oscilloscope, or vendor tool. - Toolchain and artifacts: ELF/HEX/MAP, firmware log, programmer output, schematic, boot log, or fault dump. ## Routing Guide Use the most specific path: | Symptom or target | Prefer | | --- | --- | | Cortex-M MCU, SWD/JTAG, HardFault, startup | `cortex-m...