-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32-S3 erroneous "Error: 330 126 libusb_helper.c:190 jtag_libusb_open(): libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" (OCD-649) #255
Comments
Can anyone help on this, it's so annoying.. I CAN debug, but the vscode extension pops up this error every session. Others have reported since 2018... |
Hi @Panometric
This is ok for windows and the JTAG connection should work even with this. Looking at the above console log messages I don't see any other error. However, run https://visualgdb.com/UsbDriverTool/ instead of Zadig for installation of libusb and see if that helps to avoid the above error as well. |
@kolipakakondal Thanks for that tip. I tried the WinUSB driver on VID 303A DevID 1001 Interface 2. Got the same error. This is what I understood was the correct way, per "Please install the WinUSB driver only for the interface where there is no driver installed (probably it is Interface 2) and do not re-install the driver for the other interface." But then I noticed UsbDriverTool also shows the composite device that Zadig does not. So I installed libusb to the Composite Device and rebooted the device, and JTAG was fixed. BUT, there is no Serial port anymore, only JTAG. Note on interface 2, when debugging over JTAG and having the serial monitor on that I was also having unexpected DIR errors. I have set my clock speed down to 20000, as was suggested "In particular reduce frequency, if you get DSR/DIR errors " it has not gotten rid of the errors. So perhaps there is more to this problem than just an unwanted message. It seems to be related to having a composite device. Either way, there does not seem to be a solution that does not break something. Log showing unchanged error with UsbDriverTool on Interface 2.
|
Hi @Panometric I have updated libusb version to 1.0.26. Looks like the error disappeared in my windows machine. (Win10) Can you also test and verify with the attached package? |
|
@erhankur Just updating the driver didn't do it, but the package did. Where/ when will this be officially released? Thanks! |
Glad it worked for you, too. The official release date is not decided yet. Until release, you can just replace openocd-esp32 folder under |
Hello I found same issues. OS : Ubuntu `/home/sirapol/.espressif/tools/openocd-esp32/v0.12.0-esp32-20230419/openocd-esp32/bin/openocd Open On-Chip Debugger v0.12.0-esp32-20230419 (2023-04-18-22:02) /home/sirapol/.espressif/tools/openocd-esp32/v0.12.0-esp32-20230419/openocd-esp32/bin/openocd [OpenOCD] [OpenOCD] [OpenOCD] Debug: 62 2 command.c:152 script_debug(): command - esp32c3 configure -event examine-end Debug: 63 2 command.c:152 script_debug(): command - esp32c3 configure -event gdb-detach Debug: 64 2 command.c:152 script_debug(): command - esp32c3 configure -event gdb-attach Debug: 65 2 command.c:152 script_debug(): command - esp32c3 configure -work-area-phys 0x40380000 -work-area-virt 0x40380000 -work-area-size 0x4000 -work-area-backup 1 [OpenOCD] [OpenOCD] [OpenOCD] |
@sirapol > LIBUSB_ERROR_ACCESS is not the same error at all . Please delete to prevent complicating the issue. |
Thank you everyone |
Development Kit
esp32-box
Module or chip used
ESP32-S3
Debug Adapter
Built-in JTAG
OpenOCD version
v0.11.0-esp32-20220411 (2022-04-11-08:48)
Operating System
Windows
Using an IDE ?
no, bit in VScode IDE, this error generates an annoying popup every time openocd starts.
OpenOCD command line
openocd -d3 -f board/esp32-wrover-kit-3.3v.cfg 2>&1 | tee openocd.log
JTAG Clock Speed
default 40000
ESP-IDF version
4.4.2
Problem Description
Erroneous error on startup: "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED"
PS C:\DCI\spi_lcd\lcd> openocd -f board/esp32s3-builtin.cfg
Open On-Chip Debugger v0.11.0-esp32-20220411 (2022-04-11-08:48)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
Warn : Transport "jtag" was already selected
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 : esp_usb_jtag: serial (F4:12:FA:C1:A1:64)
Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
Info : clock speed 40000 kHz
Info : JTAG tap: esp32s3.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32s3.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : starting gdb server for esp32s3.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Debug Logs
Expected behavior
Do not report an Error if connection is OK.
Screenshots
No response
The text was updated successfully, but these errors were encountered: