Hi.
I have had the ESP32-Prog running for a week on a new design. So cables and stuff should be fine.
But now this morning after receiving an update to vMicro I can't upload program.
Here is the output below.

The line: 
****[vMicro]**** Uploading App :Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
has been there since day one, and it seemed to work anyway. 

Output:
Uploading 'XXX' to 'ESP32 Dev Module' using 'ESP32 PROG'
Uploader started for board ESP32 Dev Module
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 ls/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program ls/sdk/bin/bootloader_qio_80m.bin} 0x1000" -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program {C:\Users\NUC-W7\AppData\Local\Temp\VMBuilds\XXX\esp32_esp32\Debug/XXX.ino.bin} 0x10000" -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program tions.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 :Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 2000 kHz
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=0x40090633 (active)    APP_CPU: PC=0x40000400 
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 : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x5000004B (active)    APP_CPU: PC=0x00000000 
Info : esp32: Core 0 was reset (pwrstat=0x1F, 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 : Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400 
** Programming Started **
auto erase enabled
Error: timed out while waiting for target halted / 4 - 2
Info : Target halted. PRO_CPU: PC=0x40090627 (active)    APP_CPU: PC=0x40000400 
Error: xtensa_wait_algorithm: not halted 0, pc 0x40090627, ps 0x60025
Error: Failed to wait algorithm (-302)!
Error: Algorithm run failed (-302)!
Error: Failed to run flasher stub (-302)!
Warn : Failed to get flash mappings (-302)!
Error: Target is already running an algorithm
Error: Failed to start algorithm (-4)!
Error: Algorithm run failed (-4)!
Error: Failed to run flasher stub (-4)!
Error: Target is already running an algorithm
Error: Failed to start algorithm (-4)!
Error: Algorithm run failed (-4)!
Error during upload using programmer
The uploader process failed

The uploader process failed
Error: Failed to run flasher stub (-4)!
The uploader returned an error
Error: Failed to probe flash, size 0 KB
Error: auto_probe failed
embedded:startup.tcl:480: Error: ** Programming Failed **
in procedure 'program' 
in procedure 'program_error' called at file "embedded:startup.tcl", line 539
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()

Hi.
Resetting just before uploading actually allow for upload.
If I switch to serial upload there is no problem.

I did:
    Enabled vMicro > Compiler > Show Build Properties and Verbose
    Re-Compile your program with these settings enabled
Is that what you mean by yellow box?

But I am not sure were I can find the logs?

I think you are onto something. Now I tried to stop the debugger, and then just build, then build&upload, and there was no problem.
Okay so now I know how to get out of that situation.

I do believe I actually restarted VS at least twize before reporting this, as well as rebuilding. That did nothing.

Also while we are at it. When I single-step it is talking around 20 seconds so move from one line to the next. A long time. Is that to be expected? Or is that noise on wires or something else? (10 cm long)

Have uploaded many times during today, and only had the upload problem once, and the resetting just before fixes the situation.

Thank you for the youtube vid.
Then there is clearly something wrong here. My times are very long.
I am working on a finished PCB and the ESP32-Prog is going through a pogo pin connector on fixture that has serial and debug together on 2 rows of pins.
And there is 10cm wires between the programmer and the board.
I shall follow your instructions and return tomorrow with more.

The warning shown is from the debugger itself, as it only allows 2 concurrent hardware breakpoints.  If more than two are set it has to swap them around in the background, which adds to the slow down.

We have published a video going over this on You Tube, and how to identify the issue.

The solutions available are:-
1) Only set 2 x breakpoints at any one time, and use step tools to navigate once reached (and move them around as needed when stopped)
2) Use a different hardware debugger, though the maximums rarely exceed 6 breakpoints
3) Use the Visual Micro Serial debugger instead, which supports more concurrent breaks

The differences between GDB and the Visual Micro Debugger are outlined here for clarity.