You should be running "idf.py build" from the project's directory "hello_world" instead of the "main" subdirectory.

I don't see you being use any external components. However, in your Kconfig.projbuild you have several "default" and "range" statements applying to certain IDF_TARGETs. You have these for those chips which are working for you. But you don't have them for ESP32-C6. If you have an integer-based Kconfi...

Hi Ildar Belkin, we are sorry for this issue. The error message is not clear and provide not enough information to pinpoint the issue. We already track this problem and will address it soon. In the meantime, we can try to find the root cause manually. Is this some project publicly available we can t...

Do you use pure Vscode without https://github.com/espressif/vscode-esp-idf-extension? This extension is built for convenience to achieve what you try to do yourself, and much more. See the features and setup guides in the linked page.

Suggestion poster here as well: https://github.com/espressif/esp-idf/issues/13839

Git is not required. It was only an optional dependency. Recently we've removed it from some parts of ESP-IDF but we forgot about this. This will be addressed soon. The issue you are facing is with your Python. Somehow it throws a different exception as we've anticipated. You can patch your version ...

Please try v5.1.4 which is currently the latest bugfix release of v5.1 and report back if the issue still exists. If my memories are correct then this has already been fixed.

At the end of the output of "idf.py build" you can see the flashing command using esptool.py. Running that command won't re-trigger build. This also means that you don't even need on the flashing machine to have ESP-IDF. You can set up just esptool.py there (https://docs.espressif.com/projects/espto...

Here you can find how we do it: https://github.com/espressif/esptool/bl ... sptool.yml

This will be supported from the upcoming v4.8 release of esptool.