More advice if device not found (error messages) about probe-rs HOT 4 OPEN

Don't confuse the chip version with the development board's version. You can see the chip's version info if you run espflash board-info (which is, indeed, a bit of a misleadingly named command).

The chip's USB hardware may indeed support JTAG, but if you look at the development board's schematics you can see that, by default, the USB port is not connected to the ESP32 chip.

from probe-rs.

probe-rs can not communicate over a USB serial port, you'll need to use espflash for that device I'm afraid. That being said, this is a common enough issue that we might provide some more useful feedback.

If you really want to use your C3 with probe-rs, you'll either need an external JTAG probe, or you'll need to modify the board itself according to this guide. This case, unfortunately, we won't be able to detect - we can't guess if the CP210x is indeed paired with a C3, and if that is indeed the same dev kit, etc.

from probe-rs.

Hi @bugadani

This is a bit confusing, and I'm hoping to clarify things for others in the process. Thanks for your help!

The page ESP32-C3 > JTAG Debugging (looks authoritative to me) mentions:

Debugging through the USB interface implemented in ESP32-C3 requires to have a chip with revision 0.3 or newer. Please use other debugging options (e.g., with ESP-Prog) for chip revisions 0.1 and 0.2. [...]

My board has "v.1.1" printed on the bottom side. If this is the "chip revision" I would.. expect the USB port to have JTAG functionality.

from probe-rs.

Thanks @bugadani

I was able to get "println" output yesterday, using espflash, not probe-rs. It will likely take me a while to get my head truly wrapped around these tools. That's fine. In case you are curious - the work is available at ESP32-Mac.

As to this ticket, let's keep it to the title, i.e. a request for an error message that provides some pointers instead of just saying "no connection".

from probe-rs.