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

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

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

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 ...

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 ...

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

Here's what the Build command in VSCode ESP-IDF extension v1.3
reports using ESP-IDF v4.4

Today I've found that using the older version (v1.2) of the ESP-IDF VSCode Extension,
instead of the latest (v1.3),
fixes this.

Has anyone else tried "ESP-IDF Flash (with JTag)" with v1.3 of the VSCode extension?
How did it work for you?

Hardware: (ESP-PROG with ESP32 DEVKITV1 ((ESP-WROOM-32). This hardware I've previously verified to compile, flash and debug as guided by the popular Yuri R Youtube videos. Then I noticed that there was an the official tool (VSCode ESP-IDF extension), Quick User Guide for the ESP-IDF VS Code Extensio...