Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
zhinkgit avatar

Probe Rs

  • 391 installs
  • 534 repo stars
  • Updated June 29, 2026
  • zhinkgit/embeddedskills

Probe-rs is an agent skill that orchestrates probe-rs CLI flash, memory, GDB, and RTT operations with embeddedskills JSON workflows.

About

Probe-rs is an agent skill that wraps the official probe-rs CLI for embedded developers who already use the embeddedskills workflow stack alongside J-Link and OpenOCD. It exposes list, info, flash, erase, reset, read-mem, write-mem, one-shot GDB, and RTT helpers with JSON outputs and timing metadata so agents can script repeatable bring-up without relearning each debugger’s flags. Solo builders on STM32 and similar targets configure chip, protocol, probe, and speed in .embeddedskills/config.json while accepting that probe-rs itself must be installed externally and that Windows J-Link users may need WinUSB tradeoffs against SEGGER tools. Workflow integration limits probe-rs to one-shot debug rather than long-lived DAP sessions, which keeps orchestration predictable for CI and local agent runs. Use it when you are integrating firmware builds with automated flash-and-test loops rather than only editing application code on a host OS.

  • Probe discovery, target info, flash, erase, and reset via list/info/flash/erase/reset
  • Memory read/write helpers for scripted bring-up checks
  • One-shot GDB debugging through probe_rs_gdb.py with shared JSON result shape
  • RTT observation via probe_rs_rtt.py for log streaming without extra UART wiring
  • Project-level .embeddedskills/config.json for chip, SWD/JTAG, probe, and speed

Probe Rs by the numbers

  • 391 all-time installs (skills.sh)
  • +22 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #110 of 596 Debugging skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/zhinkgit/embeddedskills --skill probe-rs

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs391
repo stars534
Security audit3 / 3 scanners passed
Last updatedJune 29, 2026
Repositoryzhinkgit/embeddedskills

What it does

Flash, debug, and inspect embedded targets with probe-rs using the same JSON workflow shape as J-Link and OpenOCD in embeddedskills.

Who is it for?

Best when you're standardizing on embeddedskills and want probe-rs as a peer backend with scripted flash-and-debug steps.

Skip if: Pure host-only web or mobile projects with no on-chip debugging, or teams that require interactive DAP sessions this skill deliberately does not expose.

When should I use this skill?

You need to list probes, flash or erase firmware, reset the target, run one-shot GDB, or stream RTT via probe-rs inside embeddedskills workflows.

What you get

Your agent runs probe-rs commands through shared wrappers and returns structured JSON for flash, debug, and RTT steps inside the same workflow as J-Link and OpenOCD.

  • JSON command results with timing for flash, debug, and RTT operations
  • Repeatable workflow steps matching jlink/openocd orchestration

By the numbers

  • Third debug backend alongside jlink and openocd
  • Default DAP port 50000 and GDB port 3333 in bundled runtime example

Files

SKILL.mdMarkdownGitHub ↗

probe-rs 下载与调试

本 skill 提供 probe-rs CLI 的结构化包装,覆盖探针发现、目标信息、烧录、复位、内存读写、one-shot GDB 调试和 RTT 日志读取。

Windows 下优先使用 py -3 调用脚本;若 arm-none-eabi-gdb 已在 PATH 中,gdb 子命令可自动发现,不强依赖 skill config.json

配置

环境级配置(skill/config.json)

首次使用前建议在 skill 目录下创建 config.json

{
  "exe": "probe-rs",
  "gdb_exe": "C:\\Program Files\\Arm\\GNU Toolchain mingw-w64-x86_64-arm-none-eabi\\bin\\arm-none-eabi-gdb.exe",
  "gdb_port": 3333,
  "dap_port": 50000,
  "operation_mode": 1
}
  • exeprobe-rs 可执行文件路径或命令名
  • gdb_exearm-none-eabi-gdb 路径,gdb 子命令需要
  • gdb_port:默认 GDB 端口
  • dap_port:预留给交互式 DAP 会话
  • operation_mode1 直接执行 / 2 输出风险摘要但不阻塞 / 3 执行前确认

工程级配置(.embeddedskills/config.json)

{
  "probe-rs": {
    "chip": "STM32F407VGTx",
    "protocol": "swd",
    "probe": "",
    "speed": 4000,
    "connect_under_reset": false
  }
}
  • chip:芯片型号,probe-rs 主后端必填
  • protocolswdjtag
  • probe:探针选择器,格式 VID:PID[:Serial]
  • speed:调试速率 kHz
  • connect_under_reset:连接时是否保持 reset

参数优先级:CLI 参数 > 工程配置(.embeddedskills/config.json)> state.json > skill 配置(config.json)> 默认值

各层职责:skill config.json 提供工具路径与端口等环境级常量;.embeddedskills/config.json 提供芯片、协议等工程级参数;CLI 参数在单次调用中覆盖一切。

子命令

子命令用途风险
list枚举可用探针
info查看探针与目标信息
flash烧录固件(elf/hex/bin/uf2)
erase擦除芯片非易失存储
reset复位目标芯片
read-mem读取内存
write-mem写内存
attach / run包装 probe-rs attach/run
gdb启动 GDB Server 并执行 one-shot 调试
rtt读取 RTT 日志

典型调用

# 列出探针
py -3 <skill-dir>/scripts/probe_rs_exec.py list --json

# 烧录 ELF
py -3 <skill-dir>/scripts/probe_rs_exec.py flash --chip STM32F407VGTx --file build/app.elf --json

# 烧录 BIN(必须提供地址)
py -3 <skill-dir>/scripts/probe_rs_exec.py flash --chip STM32F407VGTx --file build/app.bin --address 0x08000000 --json

# 读取内存
py -3 <skill-dir>/scripts/probe_rs_exec.py read-mem --chip STM32F407VGTx --address 0x20000000 --length 16 --width b32 --json

# one-shot backtrace
py -3 <skill-dir>/scripts/probe_rs_gdb.py backtrace --chip STM32F407VGTx --elf build/app.elf --json

# RTT
py -3 <skill-dir>/scripts/probe_rs_rtt.py --chip STM32F407VGTx --json

核心规则

  • 不自动猜测 chip,缺失时直接报错
  • 多探针场景建议显式提供 --probe;若未检测到任何探针,应提示用户检查 USB 连接并重试;若探针配置错误(如 VID:PID 不匹配),应报告具体错误信息并建议运行 list 子命令确认可用探针
  • .bin 烧录必须显式提供地址
  • workflow build-debug 只走 one-shot 诊断包装,不启动需要人工接管的长期 DAP 会话
  • Windows 下若要用 probe-rs 驱动 J-Link,通常需要切换到 WinUSB,这会影响 SEGGER 官方工具继续使用;若仍依赖 J-Link 官方工具链,优先继续用现有 jlink skill

Related skills

How it compares

Skill-packaged workflow wrapper around the probe-rs CLI—not a replacement for SEGGER J-Link GUI workflows or a cloud flash service.

FAQ

Who is probe-rs for?

firmware developers using embeddedskills who need probe-rs for SWD flashing, GDB one-shots, and RTT logs with JSON-friendly automation.

When should I use probe-rs?

During Build integrations work when bringing up a board, automating flash-after-build, or validating memory and reset behavior before ship-stage hardware QA.

Is probe-rs safe to install?

Check the Security Audits panel on this page; flashing and memory writes can brick or corrupt devices, so review scripts and probe driver changes (including WinUSB) before running on production hardware.

Debuggingintegrationsdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.