mcu-debug-control

Controls Cortex-Debug sessions and manages source-line or function breakpoints in VS Code.

5|1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/BakeSheep/EmberProbe-MCU-Flash-Debug --skill mcu-debug-control-bakesheep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcu-debug-control
Source: https://github.com/BakeSheep/EmberProbe-MCU-Flash-Debug/tree/main/skills/mcu-debug-control
Command: npx skills add https://github.com/BakeSheep/EmberProbe-MCU-Flash-Debug --skill mcu-debug-control-bakesheep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Embedded developers need to start, stop, and step through Cortex-Debug sessions and manage breakpoints without manually clicking through the VS Code UI, especially when driving debugging from an AI agent or automation workflow. ## Core Features & Use Cases - Session Control: Start, stop, pause, continue, step over/in/out, and restart the workspace Cortex-Debug session through EmberProbe's Agent Bridge, with completion confirmed by DAP state events. - Breakpoint Management: Add, remove, enable, disable, and list source-line or function breakpoints, with optional conditions, hit conditions, and log messages. - Safe Concurrency Handling: Enforces one control action at a time, reports structured errors like DEBUG_CONTROL_BUSY and DEBUG_CONTROL_TIMEOUT, and never auto-retries timed-out commands. - Use Case: While investigating a firmware hang, ask the agent to start a debug session, set a breakpoint at src/main.c line 42, pause the target, and inspect the debug state — all without touching launch.json. ## Quick Start Use the mcu-debug-control skill to start a Cortex-Debug session in this workspace and add a breakpoint at main.c line 42.

Frequently Asked Questions about mcu-debug-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control a Cortex-Debug session from the command line?▼

Run scripts/debug.js with a single action flag such as --start, --pause, --continue, --step-over, or --stop, plus --workspace pointing at your project. The script routes the request through EmberProbe's Agent Bridge and confirms completion from DAP state events.

How do I add breakpoints in VS Code programmatically?▼

Use --add-breakpoint with either --source <file> --line <number> or --function <name>. Optional --condition, --hit-condition, and --log-message flags are supported, and breakpoints can be created before a debug session starts.

Does this tool modify launch.json configurations?▼

No. It uses VS Code's debugger APIs and never reads or edits launch.json. The --start action reuses EmberProbe's configured ELF, probe, target, OpenOCD, and SVD settings.

Why does a debug command return DEBUG_CONTROL_BUSY?▼

DEBUG_CONTROL_BUSY means another control action is already in flight, since only one may run at a time. Instead of issuing concurrent commands, run --status to read the current debug state and wait for the pending action to finish.

What should I do when a debug command times out?▼

On DEBUG_CONTROL_TIMEOUT, run --status to check the actual target state and never auto-resend the command. If the target is still running and explicit --pause or --restart also time out, Cortex-Debug may be stuck; ask before using --stop followed by --start to rebuild the session.