OpenOCD can't detect ESP32 devKit C on Windows
Posted: Fri Jun 15, 2018 5:36 pm
I used this guide to set up OpenOCD and JTAG on windows:
https://esp-idf.readthedocs.io/en/lates ... debugging/
Right now I'm using a J-link edu mini, using an SWD cable and this SWD break-out:
https://www.adafruit.com/product/2743
Using this image https://www.segger.com/fileadmin/images ... dapter.png
this is how I hooked it up (format is j-link - SWD Breakout - Devkit C):
VTref - Vref - 3V3
GND - GND - GND
TMS - SWIO - IO14
TCK - CLK - IO13
TDO - SWO - IO15
TDI - NC - IO12
I installed the j-link drivers, and I can see the j-link in Device Manager.
When I get to the part where I need to run:
I get this:
What might be causing this? Is everything connected correctly? What can I do to troubleshoot?
Also, I've tried both using a battery connection as well as plugging the devkit c in using usb. Which is the "proper" way to debug?
Thanks in advance!
https://esp-idf.readthedocs.io/en/lates ... debugging/
Right now I'm using a J-link edu mini, using an SWD cable and this SWD break-out:
https://www.adafruit.com/product/2743
Using this image https://www.segger.com/fileadmin/images ... dapter.png
this is how I hooked it up (format is j-link - SWD Breakout - Devkit C):
VTref - Vref - 3V3
GND - GND - GND
TMS - SWIO - IO14
TCK - CLK - IO13
TDO - SWO - IO15
TDI - NC - IO12
I installed the j-link drivers, and I can see the j-link in Device Manager.
When I get to the part where I need to run:
Code: Select all
bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg
Code: Select all
$ 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 (2018-06-04-09:51)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
esp32 interrupt mask on
force hard breakpoints
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
Also, I've tried both using a battery connection as well as plugging the devkit c in using usb. Which is the "proper" way to debug?
Thanks in advance!