ESP32 Forum

Hello,
I have a problem with an matter example in VSCode.
After building the program in VSCode, I get the following warning:
- Can't proceed with flashing since project .elf file is missing from the build dir.

I have followed some helpful youtube videos and they don't have the warning.
So I am wondering how to fix this so that I can flash my programme to my esp32c6.
Besides, I found that my programme took a long time to build.

Those videos were very helpful for me. Are there any helpful videos where they explain me how to change the product and values for the app (without zerocode)? I saw that they explained it in the matter SDK manual. But it's much easier to see what effect it has. Thank you in advance for your efforts.

Hi,

- check the .elf is really built and existing
- check that your flash tool configuration uses the right file name and path

What I find a little bit tricky as beginner, are the several methods to define the environment variables, paths etc. I had some problems at the beginning related to that. So check, that you built for the right target and the flash tool also want to flash for the right target.

I am missing a little bit of high-level / low level split of the documentation, which made it hard for me to find the necessary things in the big amount of information avoiding an information overflow. Doc is good, but you have to search and read carefully.
I had also strange effects due to outdated OS with VScode and Eclipse, important seems not to deviate from the proven versions in documentation. Otherwise you might get a bunch of problems due to changes/incompatibilities of the tools, preventing success.

Good luck, Rainer

Thanks for alll your replies
I solved te problem. I did just need to give the usb port the permission.
Just solved it with the chmod 666 /dev/ttyUSB0

I am having the same problems too, even building hello_world. Looks like a bug in the tooling I will share with updates as I debug

I am having the same problems too, even building hello_world. Looks like a bug in the tooling I will share with updates as I debug

Try to apply the OSI-mathod for debugging.
- Can your PC see the USB port? Is the cable defect?
- Linux: ls /dev/tty* or ls /dev
- Windows: device manager
- Search the log file and search for a posible fault/error.
In my application was it that I didn't gave my USB the good right.
I solved it the with a 'sudo chmod 666 /dev/ttyUSB0'