← Browse

@a5c-ai/jtag-swd-debug

A

Deep integration with JTAG/SWD debug probes for hardware-level debugging and flash programming

skillclaude

Install

agr install @a5c-ai/jtag-swd-debug --target claude

Writes 2 files into .claude/skills/, pinned to git-1489e72f.

  • .claude/skills/jtag-swd-debug/README.md
  • .claude/skills/jtag-swd-debug/SKILL.md

Document


name: jtag-swd-debug description: Deep integration with JTAG/SWD debug probes for hardware-level debugging and flash programming category: Hardware Debugging allowed-tools:

  • Bash
  • Read
  • Write
  • Edit
  • Glob
  • Grep graph: domains: [domain:embedded-systems] specializations: [specialization:embedded-systems] skillAreas: [skill-area:rtos-programming, skill-area:firmware-development] roles: [role:embedded-engineer]

JTAG/SWD Debug Skill

Overview

This skill provides deep integration with JTAG/SWD debug probes for hardware-level debugging, flash programming, and real-time firmware analysis. It enables direct hardware interaction through industry-standard debug interfaces.

Capabilities

Debug Probe Operations

  • Execute OpenOCD, J-Link, and ST-LINK commands
  • Configure debug probe connections and interfaces
  • Manage multiple debug probe types and adapters
  • Handle transport protocols (JTAG, SWD, cJTAG)

Memory Operations

  • Read/write memory-mapped registers
  • Direct memory inspection and modification
  • Real-time memory watch and modification
  • Flash programming and verification
  • Memory dump and analysis

Debugging Features

  • Set hardware breakpoints and watchpoints
  • Core state inspection (registers, stack, PC)
  • Single-step execution control
  • Fault handler analysis and debugging
  • Call stack unwinding

Trace and Output

  • Semihosting input/output support
  • SWO trace output configuration
  • ITM stimulus port configuration
  • Real-time trace buffer analysis

Target Processes

  • hardware-bring-up.js - Initial board validation and debug setup
  • bootloader-implementation.js - Bootloader debugging and flash operations
  • device-driver-development.js - Driver debugging with hardware access
  • field-diagnostics.js - Field debugging and analysis

Dependencies

  • OpenOCD (Open On-Chip Debugger)
  • J-Link software (Segger)
  • ST-LINK utilities (STMicroelectronics)
  • Debug probe hardware (J-Link, ST-LINK, CMSIS-DAP)

Usage Context

This skill is invoked when tasks require:

  • Direct hardware debugging through JTAG/SWD
  • Flash memory programming operations
  • Low-level register and memory inspection
  • Fault analysis and crash debugging
  • Hardware breakpoint management

Configuration

debug_probe:
  type: jlink | stlink | openocd | cmsis-dap
  interface: swd | jtag
  speed: 4000  # kHz
  target: cortex-m4 | cortex-m7 | etc.

Example Operations

Flash Programming

openocd -f interface/stlink.cfg -f target/stm32f4x.cfg \
  -c "program firmware.elf verify reset exit"

Memory Read

JLinkExe -device STM32F407VG -if SWD -speed 4000 \
  -CommanderScript read_memory.jlink

Register Inspection

openocd -f board/stm32f4discovery.cfg \
  -c "init; halt; reg; resume; exit"

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-1489e72fbe192026-07-31