System Information
- OS info: OS: Windows 11 (26200) | Architecture: x86_64 | Kernel: 26200
- App Version: 0.13.0
Description
Please describe the issue you encountered:
ESP-IDF / VS Code / EIM Setup Issue Report
I attempted to set up ESP-IDF development for an ESP32-S3 board using Visual Studio Code, the Espressif ESP-IDF extension, and the ESP-IDF Installation Manager.
The installation itself appeared to complete successfully. EIM installed ESP-IDF v6.0.1 at:
C:\esp\v6.0.1\esp-idf
and installed the tools/Python environment under:
C:\Espressif\tools
The exported EIM configuration also confirms these paths and shows that ESP-IDF v6.0.1, Python, CMake, Ninja, OpenOCD, Xtensa/RISC-V toolchains, and IDE-related tools were selected.
However, after opening VS Code and attempting to create or configure an ESP-IDF project, the ESP-IDF extension repeatedly reported invalid or missing configuration. Errors included:
Current ESP-IDF setup is not found
and earlier:
File not found: C:\Users\bearf\esp\esp-idf\tools\idf_py_actions\constants.py
This path does not match the actual EIM installation path. The extension appeared to use or cache an old/default ESP-IDF path instead of the EIM-managed install.
The VS Code extension also produced configuration errors even after the correct ESP-IDF installation existed. The setup flow was unclear because commands referenced in some guidance, such as ESP-IDF: Configure ESP-IDF Extension, did not appear to exist in the installed extension version. Instead, the extension redirected toward the ESP-IDF Installation Manager, but it was not clear how to bind the existing EIM installation to the current VS Code workspace.
This created a confusing situation where:
ESP-IDF appeared to be installed correctly.
EIM showed a valid installation.
The project folder was open in VS Code.
The ESP-IDF extension still considered the configuration invalid.
The extension did not clearly identify which path, setup id, or workspace setting was wrong.
The issue seems to be with the integration between VS Code, the ESP-IDF extension, and EIM-managed installations, not necessarily with ESP-IDF itself.
A clearer workflow would be helpful, especially for new users:
Install EIM.
Install ESP-IDF version.
Open VS Code.
Select existing EIM install.
Create project.
Set target.
Build and flash.
Currently, the boundary between EIM configuration, VS Code extension configuration, project configuration, and ESP-IDF command-line configuration is not clear. This makes the setup feel fragile and difficult to recover from when something goes wrong.
Impact
This prevented a new user from easily creating and building a basic ESP32-S3 project in VS Code, despite having the required ESP-IDF installation and tools installed. The setup process consumed significant time before any actual firmware development could begin.
Steps to Reproduce
Expected Behavior
being able to write a program for the esp32
Actual Behavior
nothing but errors and things that did not work
Logs
Please attach logs from the app logs folder.
Additional Information
System Information
Description
Please describe the issue you encountered:
ESP-IDF / VS Code / EIM Setup Issue Report
I attempted to set up ESP-IDF development for an ESP32-S3 board using Visual Studio Code, the Espressif ESP-IDF extension, and the ESP-IDF Installation Manager.
The installation itself appeared to complete successfully. EIM installed ESP-IDF v6.0.1 at:
C:\esp\v6.0.1\esp-idf
and installed the tools/Python environment under:
C:\Espressif\tools
The exported EIM configuration also confirms these paths and shows that ESP-IDF v6.0.1, Python, CMake, Ninja, OpenOCD, Xtensa/RISC-V toolchains, and IDE-related tools were selected.
However, after opening VS Code and attempting to create or configure an ESP-IDF project, the ESP-IDF extension repeatedly reported invalid or missing configuration. Errors included:
Current ESP-IDF setup is not found
and earlier:
File not found: C:\Users\bearf\esp\esp-idf\tools\idf_py_actions\constants.py
This path does not match the actual EIM installation path. The extension appeared to use or cache an old/default ESP-IDF path instead of the EIM-managed install.
The VS Code extension also produced configuration errors even after the correct ESP-IDF installation existed. The setup flow was unclear because commands referenced in some guidance, such as ESP-IDF: Configure ESP-IDF Extension, did not appear to exist in the installed extension version. Instead, the extension redirected toward the ESP-IDF Installation Manager, but it was not clear how to bind the existing EIM installation to the current VS Code workspace.
This created a confusing situation where:
ESP-IDF appeared to be installed correctly.
EIM showed a valid installation.
The project folder was open in VS Code.
The ESP-IDF extension still considered the configuration invalid.
The extension did not clearly identify which path, setup id, or workspace setting was wrong.
The issue seems to be with the integration between VS Code, the ESP-IDF extension, and EIM-managed installations, not necessarily with ESP-IDF itself.
A clearer workflow would be helpful, especially for new users:
Install EIM.
Install ESP-IDF version.
Open VS Code.
Select existing EIM install.
Create project.
Set target.
Build and flash.
Currently, the boundary between EIM configuration, VS Code extension configuration, project configuration, and ESP-IDF command-line configuration is not clear. This makes the setup feel fragile and difficult to recover from when something goes wrong.
Impact
This prevented a new user from easily creating and building a basic ESP32-S3 project in VS Code, despite having the required ESP-IDF installation and tools installed. The setup process consumed significant time before any actual firmware development could begin.
Steps to Reproduce
Expected Behavior
being able to write a program for the esp32
Actual Behavior
nothing but errors and things that did not work
Logs
Please attach logs from the app logs folder.
Additional Information