Not able to launch GDB in IDF v4.4

[sch0bert]

Hello,

I recently updated my IDF and .espressif folder to the latest stable configuration, IDF v4.4 but when I try to run the source level debugging enviroment is not possible. When I execute it in VS code, is able to launch the OpenOCD stage but seems is not able to launch GDB, this is what I get:

imagen_2022-02-03_144126.png (38.73 KiB) Viewed 10206 times

when normally it continues up to having the GDB enviroment. After some investigation, I noticed that from IDF v4.3.2 to v4.4 the xtensa version changed to esp-2021r2-patch2-8.4.0 and doesn't include a "xtensa-esp32-elf-gdb" folder as the previews version. I'm wondering that this could be the reason as the application is not finding it but any comment will be appreciated.

sch0bert

[sch0bert]

Hello community,

Any idea where could this folder be or what's going on?

Really appreciate your comments.

Regards,
sch0bert

[ESP_Sprite]

Moving this to the IDE subforum as I suspect it's a thing with the VSCode integration.

[Samuele]

Hi
seem like a my problem ... but i use esp-idf 4.3 ... and afther the end of dicember everything worked perfectl ...
now the log is

Code: Select all

Open On-Chip Debugger  v0.10.0-esp32-20210401 (2021-04-01-15:46)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 2

adapter speed: 20000 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 : 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 : 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 : Listening on port 3333 for gdb connections
Info : accepting 'tcl' connection on tcp/6666
Info : dropped 'tcl' connection

[Time-is-life]

Are you using ESP-IDF VSCode Extension v1.3 ?
(VSCode's default behavior is to automatically update.)

1. Does using F1 "ESP-IDF: Flash (with JTag)" succeed in programming the ESP32?
2. Does reverting the ESP-IDF VSCode Extension from v1.3 to v1.2, then launching the debugger, succeed?

The following thread may be related.
https://www.esp32.com/viewtopic.php?f=40&t=25838#p91227

[Samuele]

Yes mi problem was realtive to Espressif IDF version 1.3, it's not works with jtag and the 1.2 instead yes.

I sudgest to downgrade the version of the Espressif IDF on VS code.

[sch0bert]

In my case I don't think this is related to the VS ESP extension as it used to work with IDF v4.3.2 and extension v1.3, it stopped working since I updated to IDF v4.4 as the xtensa version changed to esp-2021r2-patch2-8.4.0 and doesn't include a "xtensa-esp32-elf-gdb" folder as the previews version.

[Time-is-life]

Schobert, I'm using ESP-IDF v4.4 with ESP-IDF VSCode Extension 1.3,
and despite your nice observation of the lack of the "xtensa-esp32-elf-gdb" folder,
it starts debugging fine, so that doesn't seem to be a cause.

With your present setup ( ESP-IDF v4.4 with ESP-IDF VSCode Extension 1.3),
does using
F1 "ESP-IDF: Flash (with JTag)"
succeed in programming the ESP32?

VSCode makes it easy to revert to v1.2 of the ESP-IDF VSCode Extension.
Does reverting the Extension from v1.3 to v1.2 (still using ESP-IDF v4.4),
then launching the debugger,
succeed?
Does F1 "ESP-IDF: Flash (with JTag)"
succeed in programming the ESP32?

[Time-is-life]

See https://github.com/espressif/vscode-esp ... issues/623 for more info and fixes.