Hello all,
I’m trying to debug using the ESP-PROG board from Espressif in the platformIO environment.
My labtop is connected to the ESP-PROG by USB. Off course, I take care of zadig installation.
The ESP-PROG board is connected to an ESP32 by JTAG and provides power supply (3.3V).
I checked several times the wiring between both boards and seems ok.
Here is the debugger output from PlatformIO:
undefinedOpen On-Chip Debugger v0.10.0-esp32-20210721 (2021-07-21-13:35)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz
WARNING: boards/esp-wroom-32.cfg is deprecated, and may be removed in a future release.
adapter speed: 500 kHz
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 500 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : Listening on port 3333 for gdb connections
Reading symbols from c:\Users\pasca\Wooby\simple\.pio\build\Debug\firmware.elf...
done.
PlatformIO Unified Debugger -> https://bit.ly/pio-debug
PlatformIO: debug_tool = esp-prog
PlatformIO: Initializing remote target...
Error: esp32.cpu0: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Info : esp32.cpu0: Target halted, PC=0x00000000, debug_reason=00000000
Info : Set GDB target to 'esp32.cpu0'
Info : esp32.cpu1: Debug controller was reset.
Error: esp32.cpu1: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Info : esp32.cpu1: Target halted, PC=0x00000000, debug_reason=00000000
Error: esp32.cpu1: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu1: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu1: Failed writing 4 bytes at address 0x3ff480a4
Error: Failed to write ESP32_RTCWDT_PROTECT (-4)!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3ff5f064
Error: Failed to write ESP32_TIMG0WDT_PROTECT (-4)!
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Info : esp32.cpu1: Debug controller was reset.
Info : esp32.cpu1: Core was reset.
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Error: esp32.cpu0: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Info : esp32.cpu0: Target halted, PC=0xFFFFFFFF, debug_reason=00000000
Error: esp32.cpu0: DSR (FFFFFFFF) indicates target still busy!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3ff5f064
Error: Failed to write ESP32_TIMG0WDT_PROTECT (-4)!
Info : esp32.cpu0: Debug controller was reset.
Info : esp32.cpu0: Core was reset.
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
.pioinit:11: Error in sourced command file:
Bogus trace status reply from target: timeout
Here after is the platformio.ini file:
[env:Debug]
platform = espressif32
board = esp32dev
framework = arduino
lib_extra_dirs =
/lib
build_flags = -O0 -ggdb3 -g3 -Wl,-Map,output.map
check_tool = cppcheck, clangtidy
board_build.partitions = wooby.csv
monitor_speed = 115200
debug_port = COM9
upload_protocol = esp-prog
debug_tool = esp-prog
debug_speed = 500
debug_load_mode = always
debug_init_break = tbreak setup
Any idea?
Thanks.
