agentleFS
Sign inStart free
wedsamuel1230wedsamuel1230/embedded-engineering-skills/skills/probe-debugging/SKILL.md

probe-debugging

Skill28 starsChanged 28 days agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the shared embedded contract and keep source/build, device and physical evidence separate.

    line 9
  2. Distinctive:

    Read probe session boundaries.

    line 12
  3. Distinctive:

    Use named hypothesis checks: PC/backtrace and threads.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Probe Debugging

Read the shared embedded contract and keep source/build, device and physical evidence separate.

Read probe session boundaries. 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 for the exact tested combination. A source procedure is not a claim that every target was tested.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free