Good morning I am thinking of buying Olimex j-tag for debugging esp32. I have tried everything to use the EPS-PROG debug but have not succeeded. I will try to see if it works with Olimex VM. What do you recommend?

Hi Simon
Here my attch verbose output

Hi Simon
I have installed the FDTI driver and the outpu now is this

Debugger: ESP32 PROG
Compiling 'ESP32_WROOM_V1' for 'ESP32-WROOM-DA Module (esp32_esp32da)'
 
Program size: 240601 bytes (used 18% of a 1310720 byte maximum) (3,22 secs)
Minimum Memory Usage: 21976 bytes (7% of a 327680 byte maximum)
 
Uploading 'ESP32_WROOM_V1' to 'ESP32-WROOM-DA Module (esp32_esp32da)' using 'ESP32 PROG'
Uploader started for board ESP32-WROOM-DA Module (esp32_esp32da)
Uploader will use programmer name: esp32prog
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 "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program s/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program SP32_WROOM_V1.ino.bootloader.bin} 0x1000" -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program SP32_WROOM_V1.ino.bin} 0x10000" -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program SP32_WROOM_V1.ino.partitions.bin} 0x8000 reset; shutdown"
Open On-Chip Debugger  v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
     http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
adapter speed: 2000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
****[vMicro]**** Uploading App :Info : clock speed 2000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Error during upload using programmer
The uploader process failed

The uploader process failed
The uploader returned an error
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Listening on port 3333 for gdb connections
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : Target halted. PRO_CPU: PC=0x400F2E06 (active)    APP_CPU: PC=0x4000D02D 
Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 802): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 4 bytes at address 0x3ff48000, data - 00, 20, 49, 9c, 4c, 00, 00, 00
Error: xtensa_write_uint32_list: error writing to 3ff48000
Warn : esp32_soc_reset xtensa_write_uint32_list (reg_value_pairs_pre) err=-4
in procedure 'program'
embedded:startup.tcl:480: Error: ** Unable to reset target **
in procedure 'program' 
in procedure 'program_error' called at file "embedded:startup.tcl", line 505
at file "embedded:startup.tcl", line 480
Warn : Flash driver of esp32.flash does not support free_driver_priv()
Warn : Flash driver of irom does not support free_driver_priv()
Warn : Flash driver of drom does not support free_driver_priv()

Thanks for the output, please attach it as text files to make it easier to use.

Can you try adding a local board.txt to your project (vMicro > Add Code > Add Local Board.txt), and paste in the below lines:
tools.openocd.upload.path={runtime.tools.openocd-esp32-0.10.1-2021.11.11.path}
tools.openocd.program.path={runtime.tools.openocd-esp32-0.10.1-2021.11.11.path}

Then try the build and upload again?

NOTE: The upload can be done via USB (without the ESP-PROG), and the debugging can still be started using the ESP-PROG.  Simply set the vMicro > Uploader > Hardware Programmer: No Programmer (Default) before performing the build and upload.

Thanks for the update.

If you replace the content of your local board.txt with the attached it will set the adapter speed as required.

Thanks for the update, apologies I had put the wrong pattern name in.

If you paste in the below content into the local board.txt, and then restart Visual Studio, it should take effect for the next upload and debugging session.

Please set the uploader and the debugger to ESP32-PROG as this is the probe you are trying to use.

When sending output please ensure the complete output is attached as a text file, including the build and the upload outputs.

You can perform the upload via the normal USB route when debugging, by simply setting the vMicro > Uploader > Hardware Programmer to "No Programmer (Default)".  This may be simpler to begin with to get the debugging working which I believe is the main aim.

Also please confirm which board you are working on as it was the ESP32-WROOM-DA but the latest snippet seems to show an ESP32S2.

in attach the debug output

Sorry Simon
but I can't find the ESP32_WROOM_V1.ino_DebugOpenOCD.log

where can i find it?

ok 
the file is in attach