There should be an "sdkconfig" file in your project's directory after running menuconfig. When you move your project then you need to move it as well with the project. More information about this topic: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/kconfig.html and also i...

The trace option can only be used when esptool is invoked directly. The command with all the necessary arguments can be copied from the error message, the part starting with "The terminal process ...", and the "--trace" option added after "esptool.py". But at this point I don't think it would reveal...

> I CAN connect to my board with Putty and Hterm and interract with the ESP32 at 115200 baud (on the desktop) Could you share the logs from there? There is a "--trace" command line argument for esptool. Could you use it and capture the log into a file? (it will be long) You can try to push the boot ...

Could you try to run the following and see if it helps? I would also recommend to check the output of "git status" and see if any files have been changed. Especially those two in "components/hal" for which the error is reported.

On the ESP-IDF side we already improved the warning message. It was "error" in it so I guess the Vscode plugin exited because of it. I'm not sure if this has been fixed with any of Vscode plugin bugfixes. But the warning itself can be avoided if the virtual environment is manually deleted (C:\\Espre...

What is your ESP-IDF version? You are reading the documentation for the latest master branch (upcoming v5.4).

You can ask here: https://www.espressif.com/en/contact-us/sales-questions

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...