I am using VSCODE 1.46.1 (User) with ESP-IDF VSCode Extension 0.3.0 (full install including ONBOARDING with all IDF downloads), ESP-IDF v.4.0.1, on Windows 10 Pro, latest updates. I can compile, build, flash, monitor, but I can not debug (get startet: blink.exe) with Wrover Kit V4.1.
I store the IDF config in Workspace context.
I can start openocd server.
With the original launch.json nothing happend with F5 (Start debugging).
As told in https://github.com/espressif/vscode-esp ... BUGGING.md I exchanged the launch.json to the sencond version (for C/C++-Debugging).
When I start F5, GDB seems to be launched, but there is an error message "xtensa-esp32-elf-gdb is not found in idf.customExtraPaths".
But the extra Paths in IDF extension settings are ok:
"C:\Users\user\espressif\tools\xtensa-esp32-elf\esp-2019r2-8.2.0\xtensa-esp32-elf\bin;C:\Users\user\espressif\tools\esp32ulp-elf\2.28.51.20170517\esp32ulp-elf-binutils\bin;C:\Users\user\espressif\tools\cmake\3.13.4\bin;C:\Users\user\espressif\tools\openocd-esp32\v0.10.0-esp32-20190313\openocd-esp32\bin;C:\Users\user\espressif\tools\mconf\v4.6.0.0-idf-20190628;C:\Users\user\espressif\tools\ninja\1.9.0;C:\Users\user\espressif\tools\idf-exe\1.0.1;C:\Users\user\espressif\tools\ccache\3.7"
The Extra Vars are set to:
{"OPENOCD_SCRIPTS":"C:\Users\user\espressif\tools\openocd-esp32\v0.10.0-esp32-20190313\openocd-esp32\share\openocd"}
I tried the unboarding again, everything is fine, but the error persists.
For some reason the ExtraPaths are not evaluated. Such debugging is impossible.
What can I do or try?
VSCODE-Extension: Debug not working, idf: custom extra paths not recognized
-
- Posts: 229
- Joined: Wed May 02, 2018 12:12 pm
Re: VSCODE-Extension: Debug not working, idf: custom extra paths not recognized
Hi there,
There is seems to be an issue that vscode stopped parsing values within env in launch.json.
We had a discussion in https://github.com/espressif/vscode-esp ... issues/132 basically replace "PYTHONPATH": "${command:espIdf.getExtensionPath}/esp_debug_adapter/debug_adapter" to "PYTHONPATH": "${ESP_IDF_EXTENSION_FOLDER}/esp_debug_adapter/debug_adapter" where ${ESP_IDF_EXTENSION_FOLDER} is the path to your esp-idf extension folder.
The issue is fixed in GitHub master with https://github.com/espressif/vscode-esp ... n/pull/134 and will be fixed on marketplace for v0.3.1 which doesn't require you to define PYTHONPATH in launch.json at all.
There is seems to be an issue that vscode stopped parsing values within env in launch.json.
We had a discussion in https://github.com/espressif/vscode-esp ... issues/132 basically replace "PYTHONPATH": "${command:espIdf.getExtensionPath}/esp_debug_adapter/debug_adapter" to "PYTHONPATH": "${ESP_IDF_EXTENSION_FOLDER}/esp_debug_adapter/debug_adapter" where ${ESP_IDF_EXTENSION_FOLDER} is the path to your esp-idf extension folder.
The issue is fixed in GitHub master with https://github.com/espressif/vscode-esp ... n/pull/134 and will be fixed on marketplace for v0.3.1 which doesn't require you to define PYTHONPATH in launch.json at all.
Who is online
Users browsing this forum: No registered users and 16 guests