[SOLVED] ESP32 OPENOCD DEBUG Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

[chris007]

I am trying to use the debuger with OpenOcd via command line on a WROOM32 Devkit C which is connected to an ESP PROG. I followed this tutorial: https://www.programmersought.com/article/74374884616/

Yet, even after replacing the firmware of the ESP Prog using Zadic i still get this error when I launch openocd -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg :

"Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" in the following

Code: Select all

Open On-Chip Debugger  v0.10.0-esp32-20200709 (2020-07-09-08:54)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

WARNING: boards/esp-wroom-32.cfg is deprecated, and may be removed in a future release.
Info : Configured 2 cores
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
[b]Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED[/b]
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 0 was reset.
Info : esp32: Core 0 was reset.
Info : esp32: Debug controller 1 was reset.
Info : esp32: Core 1 was reset.
Info : Listening on port 3333 for gdb connections

Any idea why ?

[chris007]

Problem solved. I was using a USB hub between esp prog and computer