vscode-esp-idf-extension: ESP32-C3-DevKitC-02 flash using Internal JTAG but debug fails (OCD-401) (VSC-740)

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "espidf",
      "name": "Launch",
      "request": "launch",
      "skipVerifyAppBinBeforeDebug": true
    }
  ]
}

The "skipVerifyAppBinBeforeDebug": true fix was reported a few days ago https://esp32.com/viewtopic.php?t=23190

Big thanks bro, I followed your tips, it works smoothly. it also resolved the invalid issue when restart the debug, the details are as below:

@brianignacio5 Bro, I think you need to do some modifies about debugging to clarifying the debug issue when using the following configuration:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "espidf",
      "name": "Launch",
      "request": "launch",
      "debugPort": 9998,
      "logLevel": 2,
      "mode": "manual",
      "skipVerifyAppBinBeforeDebug": false,
      "initGdbCommands": [
        "target remote :3333",
        "symbol-file F:/Project/blink/build/blink.elf",
        "mon reset halt",
        "flushregs",
        "thb app_main"
      ],
      "env": {
        "CUSTOM_ENV_VAR": "SOME_VALUE"
      }
    }
  ]
}

@NicolSpies Bro, regarding the monitor you mentioned, it is not mandatory when debugging, you can close it here as below:

Upgrading to latest ESP-IDF (Master branch, version 4.4) fixed the debugging problem using internal JTAG problem as reported. Debugging works as expected except the problem previously reported regarding the serial monitoring of ESP32c3 via the JTAG UART while debugging or running without debugging.

Upgrade was done by deleting the .espressif and esp-idf folders and reconfiguring the ESP-IDF extension in VS Code.

Appended more information here, I tried to return back from v0.10.0-esp32-20210721 to v0.10.0-esp32-20210401and type in the same commands you mentioned above with git(bash), not powershell(windows 10), it works well and can stop at app_main() , the details as follows:

1. OpenOCD

PS F:\BLE_WIFI\Espressif\SDK\blink\blink> F:\Tools\Espressif\IDF_Tools\.espressif\tools\openocd-esp32\v0.10.0-esp32-20210401\openocd-esp32\bin\openocd.exe -f board/esp32c3-builtin.cfg -d3 -l oocd.log
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
User : 13 4 options.c:57 configuration_output_handler(): debug_level: 3
User : 14 10 options.c:57 configuration_output_handler():
Debug: 15 17 command.c:143 script_debug(): command - log_output log_output oocd.log

1. GDB

$ F:\\Tools\\Espressif\\IDF_Tools\\.espressif\\tools\\riscv32-esp-elf\\1.24.0.123_64eb9ff-8.4.0\\riscv32-esp-elf\\bin\\riscv32-esp-elf-gdb.exe -x gdbinit build/blink.elf
GNU gdb (crosstool-NG 1.24.0.123_64eb9ff) 8.3.1.20191211-git

Copyright (C) 2019 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 "--host=x86_64-host_w64-mingw32 --target=riscv32-esp-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/blink.elf...
app_main () at ../main/blink.c:74
74          configure_led();
JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Hardware assisted breakpoint 1 at 0x420059fc: file ../main/blink.c, line 74.

Thread 2 hit Temporary breakpoint 1, app_main () at ../main/blink.c:74
74          configure_led();
(gdb)

However, it still cannot work when using the esp-idf-extension even if using the v0.10.0-esp32-20210401, also it is the same as I mentioned above when typing in the same commands in the powershell(windows 10) that is nothing happens.

so based on lots of test results above, my summaries as follows:

1. there is one bug for debugging when using v0.10.0-esp32-20210726, but it can be used for flashing with JTAG, while v0.10.0-esp32-20210401 can be used for debugging , but not flashing
2. v0.10.0-esp32-20210401 plus GDB are only available in git(bash) or other terminals (similar with linux) not powershell(windows10)
3. v0.10.0-esp32-20210401 plus vscode plus esp-idf-extension, it cannot work:
   • mode: auto
   • mode: manual
4. the log information is as shown above

However, I tried to type in the same commands from powershell to git(bash), it seems that there is some difference, as below:

For OpenOCD

wireless_tech@LAPTOP-GUPHVV02 MINGW64 /f/BLE_WIFI/Espressif/SDK/blink/blink
$  F:\\Tools\\Espressif\\IDF_Tools\\.espressif\\tools\\openocd-esp32\\v0.10.0-esp32-20210721\\openocd-esp32\\bin\\openocd.exe -s tcl -f board/esp32c3-builtin.cfg
Open On-Chip Debugger  v0.10.0-esp32-20210721 (2021-07-21-13:35)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
Warn : Transport "jtag" was already selected
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
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 : datacount=2 progbufsize=16
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40101104
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Warn : No symbols for FreeRTOS!
Error: Algorithm timed out after 40001 ms.
Error: ra = 0x0
Error: sp = 0x3fc84890
Error: gp = 0x3fc89c00
Error: tp = 0x3fc8879c
Error: t0 = 0x80000000
Error: t1 = 0x0
Error: t2 = 0x0
Error: s0 = 0x600d0170
Error: s1 = 0x46a303
Error: a0 = 0x5
Error: a1 = 0xffffffff
Error: a2 = 0x3fc848ac
Error: a3 = 0x3fc8eb28
Error: a4 = 0x3fc8b470
Error: a5 = 0x600c4000
Error: a6 = 0x0
Error: a7 = 0x403816d6
Error: s2 = 0xbfe1c34c
Error: s3 = 0x0
Error: s4 = 0x0
Error: s5 = 0x0
Error: s6 = 0x0
Error: s7 = 0x0
Error: s8 = 0x0
Error: s9 = 0x0
Error: s10 = 0x0
Error: s11 = 0x0
Error: t3 = 0x0
Error: t4 = 0x0
Error: t5 = 0x0
Error: t6 = 0x0
Error: pc = 0x40380000
Error: mstatus = 0x1800
Error: mepc = 0x40380000
Error: mcause = 0x2
Error: Failed to wait algorithm (-302)!
Error: Algorithm run failed (-302)!
Error: Failed to run flasher stub (-302)!
Warn : Failed to get flash mappings (-302)!
Error: Target is already running an algorithm
Error: Failed to start algorithm (-4)!
Error: Failed to run flasher stub (-4)!
Warn : not enough working area available(requested 7640)
Error: no working area available, can't alloc space for stub code!
Error: Failed to run flasher stub (-308)!
Error: Failed to probe flash, size 0 KB
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

For GDB

wireless_tech@LAPTOP-GUPHVV02 MINGW64 /f/BLE_WIFI/Espressif/SDK/blink/blink
$ F:\\Tools\\Espressif\\IDF_Tools\\.espressif\\tools\\riscv32-esp-elf\\1.24.0.123_64eb9ff-8.4.0\\riscv32-esp-elf\\bin\\riscv32-esp-elf-gdb.exe -x gdbinit build/blink.elf
GNU gdb (crosstool-NG 1.24.0.123_64eb9ff) 8.3.1.20191211-git
Copyright (C) 2019 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 "--host=x86_64-host_w64-mingw32 --target=riscv32-esp-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/blink.elf...
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
gdbinit:1: Error in sourced command file:
Remote replied unexpectedly to 'vMustReplyEmpty': timeout
(gdb)

while nothing happens when using the powershell with the same commands.

@NicolSpies In manual mode you need to start both DebugAdapter script and OpenOCD yourself.

1. Run OpenOCD
2. Run DebugAdapter as python3 debug_adapter_main.py -e blink.elf -ip localhost -dn esp32c3 -d 5 -ln. debug_adapter_main.py should be somewhere in VsCode IDF plugin dir.
3. Start debug session in VsCode.

@brianignacio5 Please correct me.