Page 1 of 1

Esp32 wroom debugging

Posted: Mon Nov 02, 2020 7:18 am
by AdityaS09
Hello

We are planning to use esp32-wroom in one of our projects, and for the start we acquired few ESP32_devkitC_v4 which comes with ESP32-wroom. To get the debugging started we ordered few ESP-PROG kits as the dev-kits do not come with on board debugger. The end goal is to get everything working with Eclipse IDE.

To get the idea of how to get started with debugging, I followed the following links.
https://docs.espressif.com/projects/esp ... un-openocd
https://docs.espressif.com/projects/esp ... -jtag.html

I am getting the following errors whenever I try to run the OpenOCD command in ESP-IDF command prompt.

openocd -f interface/ftdi/esp32_devkitj_v1.cfg -f target/esp_common.cfg

Open On-Chip Debugger v0.10.0-esp32-20191114 (2019-11-14-14:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'.

After searching online for similar issues, I found that zadig software from http://zadig.akeo.ie/ can be used to resolve this issue. After installing WinUSB drivers using that software, the COM Ports opened by the debugger vanishes and I am getting a different a different error "Error: failed to reset FTDI device: LIBUSB_ERROR_PIPE".

For lot of such posts I couldn't find an actual working solution. Can someone please tell how to resolve this issue?

OpenOCD version: v0.10.0-esp32-20191114 (2019-11-14-14:19)

Thanks