The
user-friendly &
flexible embedded toolkit
that works

Run the following, or follow the instructions for different installation methods:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/probe-rs/probe-rs/releases/latest/download/probe-rs-tools-installer.sh | sh

Embedded programming made easy

Run a program on your microchip with the ease of a native application.

Easily print to STDOUT via RTT and defmt encoding when using probe-rs run.

cargo-flash can be used to just flash a target and cargo-embed can be used to get a full RTT terminal to also send commands to the target and view multiple channels at one.

Run a program on your microchip with the ease of a native application.

Easily print to STDOUT via RTT and defmt encoding when using probe-rs run.

cargo-flash can be used to just flash a target and cargo-embed can be used to get a full RTT terminal to also send commands to the target and view multiple channels at one.

Rust: $ cargo run --release

$ cargo run --release
  Compiling microbit v0.1.0 (/microbit/)
    Finished release [optimized + debuginfo] target(s) in 0.17s
    Running `probe-rs run --chip nRF51822_xxAA target/thumbv6m-none-eabi/release/microbit`
    Erasing sectors ✔ [00:00:00] [############] 5.00 KiB/5.00 KiB @ 8.09 KiB/s (eta 0s )
Programming pages   ✔ [00:00:00] [############] 5.00 KiB/5.00 KiB @ 5.29 KiB/s (eta 0s )

Hello from the microbit!
Going to udf to print a stacktrace on the host ...

Frame 0: exp_u128 @ 0x00000fa2
Frame 1: __udf @ 0x000000f2 inline
      /.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/../asm/inline.rs:181:5
Frame 2: udf @ 0x00000000000000f2 inline
      /.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/call_asm.rs:11:43
Frame 3: panic @ 0x00000000000000f2
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:36:9
Frame 4: exp_u128 @ 0x000006be
      /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/ptr/const_ptr.rs:921:18
Frame 5: exp_u128 @ 0x000006ec
      /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/num/bignum.rs:299:60
Frame 6: b @ 0x0000015e inline
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:45:5
Frame 7: a @ 0x0000000000000154 inline
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:41:5
Frame 8: __cortex_m_rt_main @ 0x0000000000000154
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:16:5
Frame 9: __cortex_m_rt_main_trampoline @ 0x00000104
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:10:1
Frame 10: <unknown function @ 0x000000ce> @ 0x000000ce inline
Frame 11: <unknown function @ 0x20004000> @ 0x20004000

C: $ make release && probe-rs run

$ make release
$ probe-rs run --chip nRF51822_xxAA build/microbit.elf
    Erasing sectors ✔ [00:00:00] [############] 5.00 KiB/5.00 KiB @ 8.09 KiB/s (eta 0s )
Programming pages   ✔ [00:00:00] [############] 5.00 KiB/5.00 KiB @ 5.29 KiB/s (eta 0s )

Hello from the microbit!
Going to udf to print a stacktrace on the host ...

Frame 0: exp_u128 @ 0x00000fa2
Frame 1: __udf @ 0x000000f2 inline
      /.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/../asm/inline.rs:181:5
Frame 2: udf @ 0x00000000000000f2 inline
      /.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/call_asm.rs:11:43
Frame 3: panic @ 0x00000000000000f2
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:36:9
Frame 4: exp_u128 @ 0x000006be
      /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/ptr/const_ptr.rs:921:18
Frame 5: exp_u128 @ 0x000006ec
      /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/num/bignum.rs:299:60
Frame 6: b @ 0x0000015e inline
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:45:5
Frame 7: a @ 0x0000000000000154 inline
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:41:5
Frame 8: __cortex_m_rt_main @ 0x0000000000000154
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:16:5
Frame 9: __cortex_m_rt_main_trampoline @ 0x00000104
      /repos/microbit/examples/gpio-hal-blinky/src/main.rs:10:1
Frame 10: <unknown function @ 0x000000ce> @ 0x000000ce inline
Frame 11: <unknown function @ 0x20004000> @ 0x20004000

Easy debugging in VSCode

Use VSCode’s awesome debug capabilities with our native debug plugin.

Run the target, set breakpoints, halt on break point, inspect the stackframe and manipulate variables.

RTT is fully integrated and GDB-like expressions can be evaluated in the built in REPL.

VSCode not your cup of tea? No problem! probe-rs implements the Debug Adapter Protocol, so you can use other editors, IDEs, and visual debuggers, such as Vimspector…

A clean and intuitive API

Manipulate your target from the host - read and write memory, set breakpoints, run, halt.

Build production utilities or awesome HITL setups. The sky is the limit!

use probe_rs::{MemoryInterface, Permissions, Session};

// Attach to the first connected probe.
let session = Session::auto_attach("nrf52", Permissions::default())?;

// Select the first core found.
let mut core = session.core(0);

// Read a block of 50 32 bit words.
let mut data = [0u32;50];
core.read_32(0x2000_0000, &mut data)?;

// Read a single 32 bit word.
let word = core.read_word_32(0x2000_0000)?;

// Writing is just as simple.
let data = [0u32;50];
core.write_32(0x2000_0000, &data)?;

// of course we can also write 8bit words.
let data = [0u8;50];
core.write_8(0x2000_0000, &data)?;