Debugger won't connect.

JeffreyEWright
Posts: 2
Joined: Fri May 27, 2022 3:53 pm

Debugger won't connect.

Postby JeffreyEWright » Fri May 27, 2022 4:09 pm

Hello;
Im using VScode with the ESP extention.
I can successfully program and monitor the ESP32-C3-DevKitM-1, but I cannot get the debugger to work.
I can run openOCD from the terminal, and it sees the uC...but when I try to launch a debug session, it exits with an error.
I've reinstalled the USB driver several times in an attempt to get to work - but without success.

I'm at a loss and need help getting this to work!
Thanks in advance for any help!

PS C:\Users\Jeff\Desktop\blespp\ble_spp_server> openocd -f board/esp32c3-builtin.cfg
Open On-Chip Debugger v0.11.0-esp32-20211220 (2021-12-20-15:43)
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
Warn : Transport "jtag" was already selected
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 : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
Info : clock speed 40000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : Examined RISC-V core; found 1 harts
Info : hart 0: XLEN=32, misa=0x40101104
Info : starting gdb server for esp32c3 on 3333
Info : Listening on port 3333 for gdb connections

===> Here I press F5 to start debugging..this is the Terminal output
PS C:\Users\Jeff\Desktop\blespp\ble_spp_server> & 'c:\Users\Jeff\.vscode\extensions\ms-vscode.cpptools-1.9.8-win32-x64\debugAdapters\bin\WindowsDebugLauncher.exe' '--stdin=Microsoft-MIEngine-In-0whq1ybw.5ip' '--stdout=Microsoft-MIEngine-Out-m1zqzm0a.vuq' '--stderr=Microsoft-MIEngine-Error-rze52qar.lg5' '--pid=Microsoft-MIEngine-Pid-nxz2wggz.rb2' '--dbgExe=C:\mingw\bin\gdb.exe' '--interpreter=mi'


===> This is the Debug window output
=thread-group-added,id="i1"
GNU gdb (GDB) 7.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Warning: Debuggee TargetArchitecture not detected, assuming x86_64.
=cmd-param-changed,param="pagination",value="off"
=cmd-param-changed,param="args",value="2>CON 1>CON <CON"
ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". Error creating process C:\Users\Jeff\Desktop\blespp\ble_spp_server\build\ble_spp_server_demo.elf, (error 193).
The program 'C:\Users\Jeff\Desktop\blespp\ble_spp_server\build\ble_spp_server_demo.elf' has exited with code 42 (0x0000002a).

NZ Gangsta
Posts: 16
Joined: Wed Jul 20, 2022 8:32 am

Re: Debugger won't connect.

Postby NZ Gangsta » Wed Jul 20, 2022 8:35 am

I also have the same problem trying to debug using visual studio code. I'm trying to debug on the ESP32-S3-EYE.

Who is online

Users browsing this forum: awegel, Barkonet and 116 guests