Unable to debug using ESP-PROG

teodorocolombo
Posts: 1
Joined: Thu Jan 19, 2023 6:32 pm

Unable to debug using ESP-PROG

Postby teodorocolombo » 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
  1. $ openocd -f board/esp32-wrover-kit-3.3v.cfg
  2. Open On-Chip Debugger v0.11.0-esp32-20221026-85-g0718fffd (2023-01-19-13:08)
  3. Licensed under GNU GPL v2
  4. For bug reports, read
  5.     http://openocd.org/doc/doxygen/bugs.html
  6. Info : Listening on port 6666 for tcl connections
  7. Info : Listening on port 4444 for telnet connections
  8. Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi tdo_sample_edge falling"
  9. Info : clock speed 20000 kHz
  10. Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  11. Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  12. Info : starting gdb server for esp32.cpu0 on 3333
  13. Info : Listening on port 3333 for gdb connections
  14. Info : [esp32.cpu0] Debug controller was reset.
  15. Info : [esp32.cpu0] Core was reset.
  16. Info : [esp32.cpu1] Debug controller was reset.
  17. Info : [esp32.cpu1] Core was reset.
  18. Info : [esp32.cpu0] Target halted, PC=0x400E46C2, debug_reason=00000000
  19. Info : [esp32.cpu0] Reset cause (1) - (Power on reset)
  20. Info : [esp32.cpu1] Target halted, PC=0x400E46C2, debug_reason=00000000
  21. Info : [esp32.cpu1] Reset cause (14) - (CPU1 reset by CPU0)
  22. Info : accepting 'gdb' connection on tcp/3333
  23. Error: Target not examined yet
  24. Error executing event gdb-attach on target esp32.cpu0:
  25.  
  26. Warn : No symbols for FreeRTOS!
  27. Error: Target not halted
  28. Error: auto_probe failed
  29. 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'.
  30. Error: attempted 'gdb' connection rejected
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.

Who is online

Users browsing this forum: No registered users and 138 guests