ESP-Prog board + Eclipse openocd for ESP32WROOM not working

[mikeBohm]

Hello
trying to get esp debugging started. Im working on win 10. Ive installed the winusb driver using zadig.
I followed this guide to set up the esp idf environment for eclipse:
https://www.beyondlogic.org/debugging-with-jtag/
But I get various error when i try to debug:

this is my debugger conf:
https://pasteboard.co/JX9DeXF.png
startup menu:
https://pasteboard.co/JX9DBuv.png

These errors I get on the first run, after starting eclipse with a power cycled esp board:
Open On-Chip Debugger v0.10.0-esp32-20210401 (2021-04-01-15:46)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 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 : esp32: Debug controller was reset.
Info : esp32: Core was reset.
Info : Listening on port 3334 for gdb connections
Info : accepting 'gdb' connection on tcp/3334
Warn : No symbols for FreeRTOS!
Info : esp32: Target halted, PC=0x4018CC36, debug_reason=00000000
Error: esp32: DSR (FFFFFFFF) indicates target still busy!
Error: esp32: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 512 bytes at address 0x40091600
Error: Failed to write stub section!
Error: esp32: DSR (FFFFFFFF) indicates target still busy!
Error: esp32: DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: esp32: DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 7188 bytes at address 0x40090000
Error: failed to restore 7188 bytes of working area at address 0x40090000
Error: Failed to load stub (-4)!
Error: Algorithm run failed (-4)!
Info : Flash mapping 0: 0x0 -> 0x2d8e860, 0 KB
Info : Flash mapping 1: 0x20 -> 0x2d609b4, 46517 KB
Info : Flash mapping 2: 0xc9a778 -> 0x0, 0 KB
Info : Flash mapping 3: 0x2d7b588 -> 0x2d735e8, 46540 KB
Info : Flash mapping 4: 0x97fcac -> 0x42e989, 46573 KB
Info : Flash mapping 5: 0x13 -> 0x1490f40, 46711 KB
Info : Flash mapping 6: 0x2d735e8 -> 0x2d730c0, 0 KB
Info : Flash mapping 7: 0x97fca8 -> 0x2d6fba0, 6486 KB
Info : Flash mapping 8: 0x1 -> 0x2b, 46541 KB
.
.
.
.


and after a while I get a time out.
restarting the debug session gives the following print:
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3334 for gdb connections
Info : accepting 'gdb' connection on tcp/3334
Warn : No symbols for FreeRTOS!
Error: Target not examined yet
Error executing event gdb-attach on target esp32:

Error: Target not halted
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected

does the
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
have anything to do with it? Ive tried what I know to get rid of that error, reinstalling WinUsb drivers back and forth with Zadig and device manager but no success, any ideas?
I can program the chip using idf.py so the chip is not bricked..

[mikeBohm]

Didnt finish the post:D

This is really blocking my work! Anyone has an idea on whats going on here?
thank you in advance!