https://github.com/espressif/esptool/releases/tag/v5.2.0 comes with the new fast-reflashing feature. We will prepare an article for https://developer.espressif.com/ soon after we finish the ESP-IDF integration (will be in ESP-IDF v6.1 but new esptool can be used as standalone tool for older ESP-IDF ...

I think what xutengl pointed out is exactly what https://github.com/espressif/idf-env/ does do. idf-env is used under the hood in both https://dl.espressif.com/dl/esp-idf/ and https://dl.espressif.com/dl/eim/ installers for adding Windows Defender exclusions.

We are excited to announce the availability of the ESP-IDF Build System v2 in Technical Preview state.

Please read the full text of the announcement at: https://github.com/espressif/esp-idf/issues/17833

These are the related trackers: https://github.com/espressif/idf-compon ... /issues/97, https://github.com/espressif/esp-idf/issues/17714

I think this command failed:

C:\Espressif\tools\idf-python\3.11.2\python.exe "C:\Espressif\frameworks\esp-idf-v5.5.1\tools\idf_tools.py" "--idf-path" "C:\Espressif\frameworks\esp-idf-v5.5.1" install --targets=esp32,esp32-c3,esp32-c6,esp32-s3,esp32-s2,esp32-p4


Could you try to run it manually ...

I don't see any error message in the logs. What did it print in the message box? "The installation process has encountered an error (which may not be critical). Exit code: -1"?

The error is coming from the build system which tries to detect the ESP-IDF version. If the git command is not found then it will fall back to alternative solutions, ie. version detection from files. I remember that Vscode didn't like the "fatal" or "error" words in the output but this has been ...

Do you know that Espressif provides docker images with ESP-IDF (https://hub.docker.com/r/espressif/idf/tags)? Here are the sources for v5.2: https://github.com/espressif/esp-idf/bl ... Dockerfile

Virtualenv installed by pip is not used. The Venv is an internal module of Python. For some reason Debian/Ubuntu and derivate operating systems divide them up and the Venv module is placed in the packages ending with "-venv".

So if your python3.8 is missing venv then I don't think you can fix it ...

Ok, I see. Python 3.10 would be better but I don't understand why it is not picked up. python3 is tested before python3.8.

Or your "python --version" is of 3.8?