probe-rs

Automate probe discovery, flashing, memory access, and RTT/GDB debugging via the probe-rs CLI.

551|66|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/zhinkgit/embeddedskills --skill probe-rs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: probe-rs
Source: https://github.com/zhinkgit/embeddedskills/tree/main/probe-rs
Command: npx skills add https://github.com/zhinkgit/embeddedskills --skill probe-rs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Embedded developers often juggle multiple tools to discover probes, flash firmware, inspect memory, and debug with RTT or GDB. This skill wraps the probe-rs CLI to automate these steps, enabling AI-assisted workflows that coordinate discovery, flashing, memory access, and live debugging.

Core Features & Use Cases

  • Probe discovery: list connected probes and read target information.
  • Flashing and memory access: flash firmware, erase, reset, and read/write memory.
  • One-shot debugging: start RTT and GDB sessions for rapid validation and iteration.

Quick Start

Run a simple command to discover probes, flash firmware, read or write memory, and start RTT/GDB debugging in one cohesive workflow.

Frequently Asked Questions about probe-rs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate probe discovery and firmware flashing for embedded development?

Automate probe discovery and firmware flashing by wrapping the probe-rs CLI to list connected probes, read target information, and flash firmware in one cohesive AI-driven workflow. It enforces explicit chip and protocol configuration to ensure reproducible builds.

Can I start RTT and GDB debugging sessions automatically without manual CLI configuration?

You can start RTT and GDB debugging sessions automatically through one-shot commands. The skill wraps the probe-rs CLI to initiate live debugging for rapid validation and iteration, applying across embedded projects and toolchains.

How do I read and write memory on an embedded chip during debugging?

Read and write memory on an embedded chip during debugging using the probe-rs CLI wrapper. The skill automates memory access alongside flashing, erasing, and resetting, while tracking stateful artifacts to ensure reproducible operations.

Do I need to specify the chip, protocol, and speed manually for probe-rs flashing?

You must specify the chip, protocol, and speed manually, as the skill enforces explicit configuration for these parameters. This requirement ensures robust error reporting and reproducible builds across different embedded projects and toolchains.

What is the best way to coordinate embedded workflows involving probe discovery, flashing, and live debugging?

The best way to coordinate embedded workflows is using an automated wrapper around the probe-rs CLI. It handles probe discovery, flashing verification, memory access, and live RTT or GDB debugging, replacing the need to juggle multiple separate tools.

Why does my probe-rs automated flashing workflow fail to reproduce builds across different embedded toolchains?

Automated flashing workflows fail to reproduce builds when explicit chip, protocol, and speed configurations are missing. The skill addresses this by enforcing explicit configuration and providing robust error reporting alongside stateful artifact tracking.