Page 1 of 1

trouble with Open OCD

Posted: Fri Dec 08, 2017 10:17 pm
by fishmonger
While attempting to set up JTAG debugging for Eclipse and a WROVER-KIT, at the following page:

http://esp-idf.readthedocs.io/en/latest ... un-openocd

I ran into trouble with libusb_open() (see below)

bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg
Open On-Chip Debugger 0.10.0-dev-ga859564 (2017-07-24-16:18)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
force hard breakpoints
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 (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).

The last 2 lines above repeat ad infinatum

Also, there was no readme file in the OpenOCD folder.

Thoughts? suggestions? Condolances?

FM

Re: trouble with Open OCD

Posted: Sat Dec 09, 2017 4:01 am
by hassan789
Try these steps:

1. try plugging the USB directly into your computer (don't use a USB hub).
2. try a different USB port (that is directly connected to the computer)
3. Double check the Zadig setting
4. put the ESP in bootload mode (hold BOOT pin, and hit the EN pin), then start openOCD