Skip to content
Skills Library
Programming · Analysis

probe-debugging

/probe-debugging

Plan and conduct target-specific GDB, SWD/JTAG and OpenOCD or vendor-probe debugging. Use when requests involve attaching a probe, breakpoints, reset/halt, inaccessible targets or live register inspection; not flashing by default.

Licence
MIT
Last repository change
15.10.2026

Assessment and security

81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content16 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Plan and conduct target-specific GDB, SWD/JTAG and OpenOCD or vendor-probe debugging. Use when requests involve attaching a probe, breakpoints, reset/halt, inaccessible targets or live register inspection; not flashing by default.

Original author description

Plan and conduct target-specific GDB, SWD/JTAG and OpenOCD or vendor-probe debugging. Use when requests involve attaching a probe, breakpoints, reset/halt, inaccessible targets or live register inspection; not flashing by default.

How it works

SKILL.md has no level-two headings · 30 lines, 212 words

SKILL.md preview
---
name: probe-debugging
description: Plan and conduct target-specific GDB, SWD/JTAG and OpenOCD or vendor-probe debugging. Use when requests involve attaching a probe, breakpoints, reset/halt, inaccessible targets or live register inspection; not flashing by default.
metadata: {triggers: "Probe Debugging, embedded diagnosis"}
---

# Probe Debugging

Read [the shared embedded contract](../../docs/arduino-skill-contract.md) and
keep source/build, device and physical evidence separate.

Read [probe session boundaries](references/workflow.md). Confirm MCU/core,
board/probe revision, target reference voltage, SWD/JTAG wiring, probe serial,
server/runner version and the exact ELF/build. Begin with offline ELF inspection.

Inspect the existing launch config or runner instead of guessing an OpenOCD
board file. Binding a debug server to loopback and selecting a probe explicitly
avoids attaching to the wrong board. `target remote`/attach, reset, breakpoint
and register writes can halt or change the target; stop/disable actuators with
the target owner before that session. A debugger connection is not read-only.

Use named hypothesis checks: PC/backtrace and threads; disassembly at the fault;
registers and stack bounds; watchpoint for a suspected overwrite. Optimized
code can inline or eliminate variables; retain the failing binary before
trying a separate debug build. Do not assume stepping reproduces race timing.

`load`, `monitor program`, erase and unprotect operations are separate writes;
never include them in an attach-only recipe. For locked targets distinguish
readout protection, electrical/reset faults and wrong-server configuration.
Unprotect may mass-erase; stop rather than silently recommending it. Return
the selected probe/ELF/server, commands actually run and their effect.

See [platform coverage](../../docs/platform-support.md) for the exact tested
combination. A source procedure is not a claim that every target was tested.
Files in this package (2)
  • SKILL.md 2 KB
  • references/workflow.md 1 KB

Versions

The database has no other skills named probe-debugging.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version ba0c363a2223 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100openocd-jtag
    Use when configuring OpenOCD for a JTAG or SWD target, flashing through it, attaching GDB to a bare-metal MCU, or setting hardware breakpoints and watchpoints. Not for probe-rs: use embedded-rust.
  • 100openocd-jtag
    OpenOCD skill for embedded hardware debugging. Use when configuring OpenOCD for JTAG or SWD targets, flashing firmware, connecting GDB to bare-metal targets, setting hardware watchpoints, or using J-Link with OpenOCD. Activates on queries about OpenOCD, JTAG, SWD, GDB remote…
  • 100openocd-jlink-stlink-debug
    Use when debugging OpenOCD, J-Link, ST-Link, CMSIS-DAP, probe connection, reset scripts, flash algorithms, GDB attach, semihosting, RTT, or SWD/JTAG failures
  • 95testbench-debug
    Remote GDB debugging of ESP32 devices via the testbench. Covers USB JTAG (C3/S3), dual-USB (S3 two-port), and ESP-Prog (FT2232H) approaches. Use when setting up JTAG debugging, connecting GDB, configuring OpenOCD, or troubleshooting debug connections. Triggers on "GDB", "JTAG",…
  • 100freertos
    Use when creating FreeRTOS tasks, queues, semaphores, or mutexes, catching stack overflow, writing FreeRTOSConfig.h, or debugging tasks over OpenOCD and GDB. Not for probe setup: use openocd-jtag.
  • 100cortex-m-debug
    Use when debugging Cortex-M microcontrollers, firmware bring-up, SWD/JTAG sessions, faults, startup code, or flashing failures

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.