OpenOCD and JTAG/SWD debugging: flash firmware, attach GDB, set hardware breakpoints
CMSIS-DAP/J-Link/ST-Link configs, GDB on extended-remote :3333, firmware flashing, hardware breakpoints and watchpoints, and a table of the most common OpenOCD errors with fixes
- What
- CMSIS-DAP/J-Link/ST-Link configs, GDB on extended-remote :3333, firmware flashing, hardware breakpoints and watchpoints, and a table of the most common OpenOCD errors with fixes
- Cost
- Free
- Needs
- an MCU board, a working debug probe (J-Link, ST-Link, CMSIS-DAP, or FTDI), and OpenOCD + arm-none-eabi-gdb installed — this skill drives real hardware
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @mohitmishra786's OpenOCD/JTAG skill: the complete agent workflow for embedded hardware debugging — JTAG vs SWD selection, OpenOCD interface configs for CMSIS-DAP, ST-Link, J-Link and FTDI adapters with target scripts (STM32, nRF52, ESP32, RP2040), connecting `arm-none-eabi-gdb` via extended-remote :3333 with reset-halt/load flows, firmware flashing via the ELF load path, the OpenOCD telnet program command, or script mode (`-c "program ... exit"`), hardware breakpoints (`hbreak`) and watchpoints (`watch`/`rwatch`/`awatch`) with their Cortex-M register limits, a monitor-command reference (reset, halt, mdw/mww, reg, disassemble), and a common-errors table with fixes (no JTAG device found, scan-chain failures, wrong flash driver, target-not-halted, memory-access errors) — plus the Segger JLinkGDBServer alternative. Honest caveats: it assumes physical access to the board, a working debug probe, and the correct `.cfg` for your exact MCU part number — it cannot fix a wrong target config for you; flashing real hardware is destructive by nature, double-check the image and address before running. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
OpenOCD and JTAG/SWD debugging is a free Muse skill for embedded hardware debugging. It covers JTAG versus SWD selection, OpenOCD interface configs for CMSIS-DAP, ST-Link, J-Link and FTDI adapters, connecting GDB over extended-remote, firmware flashing, hardware breakpoints and watchpoints, plus a table of common OpenOCD errors with fixes.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit bdc5847Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an MCU board, a working debug probe (J-Link, ST-Link, CMSIS-DAP, or FTDI), and OpenOCD + arm-none-eabi-gdb installed — this skill drives real hardware Install "OpenOCD and JTAG/SWD debugging: flash firmware, attach GDB, set hardware breakpoints" for me. It gives my agent @mohitmishra786's embedded-debugging workflow: JTAG vs SWD selection, OpenOCD configs for CMSIS-DAP/ST-Link/J-Link/FTDI adapters and common targets, GDB attach via extended-remote :3333 with reset-halt/load flows, firmware flashing (ELF, telnet, script mode), hardware breakpoints and watchpoints with Cortex-M limits, a monitor-command reference, and a common-errors table with fixes. MIT licensed. Repository: https://raw.githubusercontent.com/mohitmishra786/low-level-dev-skills/bdc58472fa9f309ed1b3f7d985a0d8e9bd8f4608/skills/embedded/openocd-jtag/SKILL.md Pinned version: install the code at commit bdc58472fa9f309ed1b3f7d985a0d8e9bd8f4608 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "openocd-jtag". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. connect the probe to my board, pick the .cfg matching my exact MCU part number, and double-check every firmware image and flash address before running — flashing real hardware is destructive; Segger JLinkGDBServer is a documented alternative). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- bdc5847 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.