I have been using VM + ESP-PROG + ESP32 for uploading and debugging sketches.  Suddenly, for no obvious reason, the debug start process fails with the attached output showing error messages.  I have changed cables, USB ports, re-run Zadig on the correct interface but nothing fixes the problem.  Any ideas most welcome - thanks.

Bit more info - I was getting a message about a missing bin file in C:\Users\Steven\AppData\Local\Temp\VMBuilds\ESP32S3_test\esp32_esp32\Release which was true there was not a single bin file.  So I changed the programmer to none and started debugging after uploading via the COM port, this time it worked and looking in the \Release folder now several bin files were listed, then changing the programmer back to esp-prog again everything worked - does this make any kind of sense to you?

Spoke too soon, debug problem has returned.  Error messages attached - unable to start debugging and frame not in module.  I created a new project with a different name using a simple blink sketch and could debug using esp-prog but when I replaced the blink sketch with a more complex program I got the attached error messages again. Seems I can only upload 2 files at any one time so the 3 files mentioned are in the zip.

I removed VM extension from VS and reinstalled it. The breakpoints are set for simple delay() lines. Attached zipped spreadsheet shows success/failures for two projects by method and the text file is the debug output. The failing VM project can be downloaded from https://github.com/BenthamSoftwareServices/Visual_Micro/tree/main/ESP32/6E5C_Mag...

I just created a new project and copied the code from an earlier working project and this time serial debug does not work, and I noticed that the line number at the breakpoint does not turn from grey to white and the continue button does not appear (the little white one) but the square stop debugging does and if I stop debugging the last time of the output states that it has stopped at the line where the breakpoint is located. However the hardware debugging via esp-prog does work both with serial and JTAG uploads - the errors all seem somewhat random?

Since I performed hardware debug, via ESP-PROG using both serial and JTAG upload, now the serial debug works and I can't get it to fail again.  If it happens again I'll try and grab the output.  Are the various outputs stored anywhere in a log file as I notice that some output disappears from the console on completion of the build/upload e.g. the library building process?