ESP32-S3 & USB JTAG debugging

A week ago, when I tested ‘USB JTAG’ debugging it seemed to work fine, but now it doesn’t work at all.

The message given is 'Failed to Launch GDB: .pioinit:11 Error in sourced command file: Remote communication error. Target Disconnected.: Success. (from interpreter-exec console “source.pioinit”)

The complete log is
undefinedC:\Users\markv.platformio\packages\toolchain-xtensa-esp32s3@8.4.0+2021r2-patch5\bin\xtensa-esp32s3-elf-gdb.exe: warning: Couldn’t determine a path for the index cache directory.

Reading symbols from c:\Users\markv\Documents\PlatformIO\Projects\TFT_pixelTest.pio\build\makerfabs_43ct\firmware.elf…

PlatformIO Unified Debugger → Redirecting...

PlatformIO: debug_tool = esp-builtin

PlatformIO: Initializing remote target…

Open On-Chip Debugger v0.11.0-esp32-20220706 (2022-07-06-15:48)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

Info : only one transport option; autoselect ‘jtag’

Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001

Info : esp_usb_jtag: capabilities descriptor set to 0x2000

adapter speed: 40000 kHz

Warn : Transport “jtag” was already selected

adapter speed: 5000 kHz

Info : tcl server disabled

Info : telnet server disabled

Info : esp_usb_jtag: serial (34:85:18:99:93:08)

Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255

Info : clock speed 5000 kHz

Info : JTAG tap: esp32s3.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)

Info : JTAG tap: esp32s3.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)

Info : [esp32s3.cpu0] Debug controller was reset.

Info : [esp32s3.cpu0] Core was reset.

Info : [esp32s3.cpu1] Debug controller was reset.

Info : [esp32s3.cpu1] Core was reset.

Info : starting gdb server for esp32s3.cpu0 on pipe

Info : accepting ‘gdb’ connection from pipe

Info : [esp32s3.cpu0] Target halted, PC=0x42026F26, debug_reason=00000000

Info : Set GDB target to ‘esp32s3.cpu0’

Info : [esp32s3.cpu1] Target halted, PC=0x420047AB, debug_reason=00000000

Warn : No symbols for FreeRTOS!

Ignoring packet error, continuing…

warning: unrecognized item “timeout” in “qSupported” response

Error: timed out while waiting for target halted

Info : [esp32s3.cpu0] Target halted, PC=0x403B20A8, debug_reason=00000000

Error: xtensa_wait_algorithm: not halted 0, pc 0x403b20a8, ps 0x60e25

Error: Failed to wait algorithm (-302)!

Error: Algorithm run failed (-302)!

Error: Too many flash mappings 1919973477! Must be 2.

Warn : Failed to get flash mappings (-4)!

Error: Target is already running an algorithm

Error: Failed to start algorithm (-4)!

Error: Failed to get flash size!

Error: Target is already running an algorithm

Error: Failed to start algorithm (-4)!

Error: Failed to get flash size!

Error: Failed to probe flash, size 0 KB

Error: auto_probe failed

Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use ‘gdb_memory_map disable’.

Error: attempted ‘gdb’ connection rejected

Error: error during select: Unknown error

.pioinit:11: Error in sourced command file:

Remote communication error. Target disconnected.: Success.

Rebooting seems to change nothing, a colleague had it working, but then ran into issues after a reboot
Any ideas?
Platform is Windows

can you, via serial (i.e. remove debug_protocol) upload a minimal, empty sketch and retry?

Hi,

I’m getting the same issue with my setup. I’m not able to see debug_protocol in PlatformIO docs but I can see debug_tool. I assume this is what you mean.

I am using the default configuration with no debug_tool specified. This seems to default to esp-builtin when nothing is specified.

@mvandere - Hi, I ran into the very same Problem now. I will be helpful to me if you could share the solution on the post. Thank you.

1 Like