ESP32 Forum

I was going to try the debugging using the Visual Code Espressif extension, but I'm getting a message similar to this one for all extension commands:

Command 'ESP-IDF: Configure ESP-IDF extension' resulted in an error (command 'espIdf.setup.start' not found)

How can I fix this?
Thank you

Did you follow these steps?

https://github.com/espressif/vscode-esp ... ource-code

Could you provide some troubleshoot information ?

https://github.com/espressif/vscode-esp ... leshooting

Just to report that the all of a sudden the extension is not giving me any error messages and it appears to be running OK.
It is very confusing as I haven't tried to do anything to it. I was busy trying to set up debugging using C/C++ extension and just noticed that the I got the IDF extension back.
Whatever it is, I'm happy to have it back. Now I have to find out how to debug using this extension.

The same way I got the IDF extension back - just by itself, I lost something much more important - I can't build the project. I'm getting this output:

Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 --warn-uninitialized -DIDF_TARGET=esp32 -DCCACHE_ENABLE=0 c:\users\ndjur\desktop\esp\eimctrl"...
Warn about uninitialized values.
CMake Error: Error: generator : Ninja
Does not match the generator used previously: NMake Makefiles
Either remove the CMakeCache.txt file and CMakeFiles directory or choose a different binary directory.
cmake failed with exit code 1

Can you please tell me why this happened, and more importantly, how to fix it?
Thanks a lot

Deleting CMakeCache.txt file and CMakeFiles directory helped me to build the project again.
Can you please tell me what is the reason for this problem and why the deletion helped?
Thank you.

I had a similar issue (command not found) and it was resolved by running

<code> npm install --legacy-peer-deps </code>

in the vscode dependency folder (~/.vscode/extensions/espressif.esp-idf-extension-1.x.x>). I am not sure how the node_modules folder got deleted in the first place, but this resolved the issue.

I opened visual studio code in run as administrator and after that installed the extension and then there was no error