Thanks for the report.

Channel 0 needs to have the WinUSB Driver installed to allow the software to communicate with it:
https://www.visualmicro.com/page/Zadig-Driver-Installation-Guide.aspx

Once installed, please perform the upload to the ESP via USB (not through the programmer).

Then enable vMicro > Upload > Verbose. Then try and run Debug > Attach to Process.

If this fails a log file will be generated in the build folder, which you can find using the instructions here, which will show more information:
https://www.visualmicro.com/page/Troubleshooter-for-Debugging-an-Arduino-Sketch-...

I tried to set up USB (non-serial port) programming (on ESP-Prog JTAG cable) but failed.
The system always searches for a serial port for programming / uploading.

safi

I'm so sorry I can start debugging so hard!
I'm not setting something right, it could be a mistake.

I tried to program ESP with a USB-TTL converter.
It did not go with ESP-Prog channel 1 (COMxxx).
By connecting a CH340 USB-TTL converter to the serial connectors instead of ESP-Prog, programming was successful.

Programming does not work with ESP-Prog channel 1 (COMxxx).
I don't have a log file for this, I can attach the output.

Thank you so much for your help so far!
I'm pausing the hardware debug now. (Until I calm down.)
I'm trying to get a feel for success with software debugging.
If the software debug succeeds, I will return to the hardware debug.

Software debug:
I communicate with the board via the USB port on the ESP32 wroom32D panel.
Programming was done with the "Build and Upload" menu item.

COM: Silicon Labs CP210x USB to UART Bridge (COM6)
Additional settings and the result of the debug are in the attached image.
Everything seems to be successful, but program execution doesn’t stop at breakpoints.
Stepping doesn't go.
The Output screen shows that the program is running, but debugging does not work.

What did I watch? What didn't I set up?

safi

Thanks for the update, and just to confirm the Serial debugger does not support stepping Over/In/Out, but does allow a large number of breakpoints.

For the ESP-PROG, we should be able to get the information we need as below:

If you run the below command in cmd.exe, after you have connected the ESP-PROG to your board, and the USB cables to the PC:

C:\ProgramData\vmicro\tools\openocd-espressif-esp32-10.0.1\bin\openocd.exe -d2 -s s/" -f "interface/ftdi/minimodule-lowcost.cfg" -f "board/esp-wroom-32.cfg" -c "init" 

And send us the output from this, it should show further detail.

I tried the hardware debug again.
Charging was performed on a serial port independent of ESP-Prog while the ESP-Prog JTAG connector (and also the Prog connector) was not connected.
Build and Upload was successful (or not?). but the debug did not start.
Clicking the Step Into button started a new upload, which resulted in an error message.

I attached the images and outputs.

What else do I need to set up?

(Unfortunately, I was only able to attach 2 files, the rest will be attached in my next mail.)

safi

Thanks for the information.  Is this the same if you use Debug > Attach to Process?

Also check the Project Property for Micro Debug is set back to none.

Do you have a log file in the below location? (please attach if it is present):

e_OK.ino_DebugOpenOCD.log 

Is there any information in the Output Window > Debug?

Thanks for the information, we will have to setup an environment to try to replicate this on.

We will update when we have further information around this.

Thanks again for your effort!
Would providing TeamViewer access to my computer make it easier to identify the error?
If so, I can solve it next week, Monday, at a time when it's right for you.
If you go for a hardware debug, we will try out the features and maybe buy it.
Hi: safi

We are currently investigating this on our system and we will update when we have an update with the fix in.