Skip to main content
Embedder uses probe-rs for bridge flashing when the target has a known MCU, and for the bridge’s bounded RTT capture workflow. The installed probe-rs version must support the exact chip and debug probe. A board’s presence in the hardware catalog does not establish that support.

​
Prepare the hardware host

  1. Set up and select a remote hardware bridge.
  2. Install probe-rs on that host and make it available to the bridge service. The service must also have permission to access the USB probe.
  3. Connect the probe, target reference voltage, ground, and the board’s required SWD or JTAG signals. Power the target as its board documentation requires.
  4. Identify the exact chip and probe. If several probes are present, ask Embedder to list them and select the intended one by its full probe identifier.
  5. Build an ELF for that target and confirm its path in the project.
Run embedder bridge doctor to check the selected bridge, then ask:

​
Program and start the target

Replace the artifact path with your build output. Embedder downloads the artifact with probe-rs, then requests a reset to start the firmware. Programming replaces firmware and changes execution state. A successful download can still be followed by a reset failure; check the result before assuming the application is running. If no target can be identified automatically, supply the exact chip name. Do not substitute a similar MCU to bypass an unsupported-chip error.

​
Capture RTT after programming

Firmware must include RTT output. For this bridge workflow, flash the matching ELF through Embedder in the current session first, then request a bounded capture:
This path uses the artifact from that flash and does not offer a configurable probe frequency. If the current fault or RAM contents must be preserved, do not flash just to enable this workflow. Use an already prepared RTT connection or review the debugger attachment precautions.

​
Choose debugging separately

For breakpoints, stepping, and memory inspection, use the applicable J-Link or OpenOCD guide. The bridge’s use of probe-rs for flashing does not select it as Embedder’s GDB backend.

​
Troubleshoot

  • Command unavailable: install probe-rs on the hardware host and check the bridge service’s executable permissions and environment.
  • Chip unsupported: check the exact chip name against the installed probe-rs target list.
  • Multiple probes: choose the full identifier returned for the intended probe, including its serial component when present.
  • Download succeeded but no boot: check the reset result, target power, and firmware output transport.
  • RTT requires a flashed ELF: this session has no suitable prior bridge flash. Preserve fault evidence before deciding to program.
See Flashing firmware for checking boot results and Hardware scripts for repeatable checks.
Last modified on September 12, 2026