ESP32 Forum

Hello,

I installed ESP-IDF through VS Code on Linux (OpenSuSE 15.4).
I installed the github master branch from March 3rd and configured python3.10.
I created an example project from the Hello World template, compiled it, all fine.

I have an ESP32-S3 Wroom-1 on /dev/ttyACM0 (access rights set to 666).
The board is only connected via USB (right connector), nothing else.

I flashed the example project and can see the expected output on the "monitor"
in VS Code.

I'd like to do source level debugging via USB-JTAG (This is the correct choice, right?)

For testing I typed in a /bin/bash:

source ~/exp/master/esp-idf/export.sh

openocd -f board/esp32s3-builtin.cfg
Open On-Chip Debugger v0.12.0-esp32-20230921 (2023-09-21-13:41)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselecting 'jtag'
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: esp_usb_jtag: could not find or open device!

I don't have the mentioned USB VID:PID device in my system, the board
rather identifies in "lsusb" like this:

Bus 001 Device 002: ID 1a86:55d3 QinHeng Electronics USB Single Serial

I wonder what do I do wrong? My connection on the ESP32-S3-Wroom-1 is USB-JTAG,
means D+ and D- directly go to the chip. I don't use the external JTAG.

Don't I need to tell openocd to use /dev/ttyACM0 ?

Is the procedure above correct to test USB-JTAG (means the right connector
on the ESP32-S3-Wroom-1) ?


Thanks for any hints,
Torsten

tomohr wrote: ↑

Mon Mar 04, 2024 10:33 pm

I have an ESP32-S3 Wroom-1 on /dev/ttyACM0 (access rights set to 666).

Note that 'ESP32-S3 Wroom-1' identifies the module, not the type of devboard.

I don't have the mentioned USB VID:PID device in my system, the board
rather identifies in "lsusb" like this:

Bus 001 Device 002: ID 1a86:55d3 QinHeng Electronics USB Single Serial

That is not an internal USB serial-JTAG device. That's likely a CH340 USB-to-serial chip.

Fwiw, an ESP would show up as

I wonder what do I do wrong? My connection on the ESP32-S3-Wroom-1 is USB-JTAG,
means D+ and D- directly go to the chip. I don't use the external JTAG.

Don't I need to tell openocd to use /dev/ttyACM0 ?

Is the procedure above correct to test USB-JTAG (means the right connector
on the ESP32-S3-Wroom-1) ?

I suspect you're using a 3rd-party devboard rather than an official Devkit-C. Could very well be that you need to use the other USB port in that case. You'd know you have a successful connection because the 303a:1001 device would show up.

Thanks! That was exactly the problem, I had to use the other port.
I was not aware as flashing and monitoring worked fine, that gave me the impression I was using the correct USB port.