Dániel Buga

The specific issue (not being able to flash) was fixed by #1174. The more generic issue is, how do we describe devices that have "variable" flash sizes (i.e. external flash...

"FTDI devices" is impossible because SWD support needs external hardware. We don't currently have configuration options for probe drivers (e.g. we can't tell the driver which pin is SWD direction...

The resistor method may work but is not universal. For example, https://github.com/probe-rs/probe-rs/issues/2403 has an external hardware that uses something else built into the probe itself. I would like to avoid...

Whichever reports a unique VID/PID pair, so we can detect it unambiguously. Alternatively, we need a way to configure the probe driver somehow. We currently only allow selecting a device...

Unfortunately this brings in another issue, with the esp-idf OTA mechanism: If you flash the application to the inactive OTA partition, I don't think probe-rs ensures it gets activated. So...

Very well, let's come back to this once we figure out why the flash algo refuses to work.

I believe https://github.com/probe-rs/probe-rs/pull/2925 fixed the flash algo, though I didn't explicitly target your use case.

I'm slightly biased here so I'd like @Yatekii to chime in - are we fine with more vendor-specific CLI options? Unfortunately my factoring out of vendor-specific additions has stalled a...

> If you plan to remove all the esp idf options Not at all, I just don't want them to be so hard-coded :)

I'd like to clarify the exact issue, because `write-bin` does not convert the elf in any way. Is the issue that `espflash save-image` converts the image incorrectly, that `espflash flash`...