probe-rs
probe-rs copied to clipboard
probe-rs
A debugging toolset and library for debugging embedded ARM and RISC-V targets on a separate host
the issue is this logic here https://github.com/probe-rs/probe-rs/blob/master/probe-rs/src/probe/arm_debug_interface.rs#L448-L449 Currently we assume for AP writes the result comes back in the next transfer for all errors. However this is not the case...
By default in Windows 10, FTDI devices get a proprietary driver installed. This allows you to access MPSSE mode via the "D2XX" interface. The libftd2xx crate provides a safe abstraction...
This PR adds support for the ORBTrace probe. Currently only SWO-based tracing is supported. I'm not sure if it's a good way to implement a CMSIS-DAP based device with overrides...
Not much to add, but IMO cargo embed should not default to any protocol if the connected probe only supports a single one.
**Describe the bug** `probe-rs run ~/esp-idf-test-elf --chip esp32c3` produces the following error ```shell ERROR probe_rs::flashing::flasher: Failed to verify flash algorithm. Data mismatch at address 0x4038fff8 ERROR probe_rs::flashing::flasher: Original instruction: 0x100073...
The protocol selection is inconsistent right now, some implementations will switch protocol when e.g. `try_get_riscv_interface` is called. For example J-Link: https://github.com/probe-rs/probe-rs/blob/8d3eb3bedf94bb1d0244b11f6b273b93d3800fc0/probe-rs/src/probe/jlink/mod.rs#L811 This makes something like this: ```rust probe.select_protocol(WireProtocol::Swd)?; probe.try_into_riscv_interface()?; ```...
First of all; Thank you for developing and providing on this project, it's been of great help building custom MCU programming tools! :) This PR is a interest check/proposal to...
For RISCV and Xtensa, it is possible to debug multiple cores (unsure about how ARM works, if anyone can fill this information in that would be great), however, they work...
