Dániel Buga

@juliankrieger I believe #2365 may have made a difference here, can you please retest your issue?

~My guess is that this is a duplicate of #1374. Maybe not, but while playing with #2340 I did not run into this issue.~ I'm not sure if I'm seeing...

> features = ["stm32f107", "rt"] Are you sure your project is properly set up? I'm not sure what the difference is between the 105 and the 107 but that's a...

In general, the team is hesitant to add target-specific flags. If you can write a flash algorithm that implements 2) we can add `atsamdXXXX-with-bootloader` targets that execute the modified flash...

@noppej just FYI this PR has merge conflicts now that should be resolved. Other than that, are the TODOs in the PR description still unresolved?

I'm not entirely sure I understand what you're trying to do. We pass `--message-format=json(-and-some-extras)` to cargo, does it even output anything to stderr, or do we receive `cargo_metadata::Message` objects? Take...

Thanks! Some of this may be related to https://github.com/probe-rs/probe-rs/issues/2180 or at least some of the symptoms may change depending on that issue's resolution.

`ERROR probe_rs::probe::arm_debug_interface: Unexpected DAP response: 5` is just some BS from the ARM interface detection, not relevant to ESP32

Hmm I was hoping github would transfer the comments, the relevan one is https://github.com/probe-rs/probe-rs/discussions/2272#discussioncomment-8737255

There are a few separate issues here: - `probe-rs erase` does not work - We don't document which USB interface is the JTAG one. I'm not sure we have to,...