Unable to debug using ESP-PROG
Posted: Thu Jan 19, 2023 6:40 pm
Hi guys. I'm running into problems when I try to debug the ESP-WROOM-32 using ESP-PROG.
Every time I start OpenOCD and xtensa-esp32-elf-gdb I get the same error messagem when trying to target remote :3333
I already tried into two differents ESP32, checked the wiring multiple times and still get this error message. When I try to connect on the port :6666 it accepts normally.
Every time I start OpenOCD and xtensa-esp32-elf-gdb I get the same error messagem when trying to target remote :3333
- $ openocd -f board/esp32-wrover-kit-3.3v.cfg
- Open On-Chip Debugger v0.11.0-esp32-20221026-85-g0718fffd (2023-01-19-13:08)
- Licensed under GNU GPL v2
- For bug reports, read
- http://openocd.org/doc/doxygen/bugs.html
- Info : Listening on port 6666 for tcl connections
- Info : Listening on port 4444 for telnet connections
- Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi tdo_sample_edge falling"
- Info : clock speed 20000 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 : starting gdb server for esp32.cpu0 on 3333
- Info : Listening on port 3333 for gdb connections
- 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] Target halted, PC=0x400E46C2, debug_reason=00000000
- Info : [esp32.cpu0] Reset cause (1) - (Power on reset)
- Info : [esp32.cpu1] Target halted, PC=0x400E46C2, debug_reason=00000000
- Info : [esp32.cpu1] Reset cause (14) - (CPU1 reset by CPU0)
- Info : accepting 'gdb' connection on tcp/3333
- Error: Target not examined yet
- Error executing event gdb-attach on target esp32.cpu0:
- Warn : No symbols for FreeRTOS!
- Error: Target not halted
- 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