ESP32 Forum

Posted: **Mon May 04, 2020 12:59 pm**

Hello,

I've installed the IDF V4 on Windows10 and was suprised how fine that works, but now I've some trouble
calling a c232hm ftdi with openocd:

Code: Select all

d:\Source\esp32\esp-idf>openocd -f interface\ftdi\c232hm.cfg
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
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
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6014, description '*', serial '*' at bus location '*'

The ftdi driver seem installed fine and got the maching id's:

Code: Select all

FTDIBUS\COMPORT&VID_0403&PID6014

Any Ideas why openocd cannot find the Interface?

Posted: **Mon May 04, 2020 6:49 pm**

it's like google shown and I didn't got (pretty stupid)

google points me to that openocd can't access the 64Bit COM but a USB device, so I have to change the driver.
There are several ways to do that and all my attempts failed this afternoon before I wrote this post.

Right now I tried the zadig tool (https://zadig.akeo.ie/) and changed to winusb which works fine.

Code: Select all

D:\Source\esp32\esp-idf>openocd -f interface\ftdi\c232hm.cfg -f board\esp-wroom-32.cfg
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
adapter speed: 20000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
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 (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 : Detected debug stubs @ 3ffb3b00 on core0 of target 'esp32'
Info : Listening on port 3333 for gdb connections

ESP32 Forum

[solved] Windows10 unable to open ftdi (IDF V4)

[solved] Windows10 unable to open ftdi (IDF V4)

Re: Windows10 unable to open ftdi (IDF V4)