Wrover kit: problem running OpenOCD [solved]

[ed_mack]

Hello,

I’m working to setup jtag debugging capability on ESP Wrover Kit. I’m following Jtag debugging introduction guide
https://docs.espressif.com/projects/esp ... troduction
I get to the point were I try to run openOCD on command line, and run into the following error. Any help in detemining the cause of error is appreciated. See command line output below.

Thanks
Ed

~project/esp/openocd-esp32 $ bin/openocd -f share/openocd/scripts/interface/ftdi/esp32_devkitj_v1.cfg -f share/openocd/scripts/board/esp32-wrover.cfg

Open On-Chip Debugger 0.10.0-dev (2018-11-05-04:03)
Licensed under GNU GPL v2
For bug reports, read
http://openococd/doc/doxygen/bugs.html
none separate
adapter speed: 20000 Khz (I’ve tried slowing down to 20 Khz)
esp32 interrupt mask on
Info: ftdi: if you experience problems at higher adapter clocks, try the command “ftdi_tdo_sample_edge falling”
Info : clock speed 20000 KHz
Error: JTAG scan chain interrogation fails: all ones
Error Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain any way …
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn: Bypasing JTAG setup events due to errors

Some notes on Setup
a: ESP-IDF 3.1.2
b: ESP-WROVER_KIT_V4.1, with ESP32-WROVER module installed
c: I’ve tried running OpenOCD with three different application flashed (hello world, ble_ibeacon and gate_multi_connect). All three applications run, AND same errors when trying to run OpenOCD with them.
d: I have 4 jumpers on JP2 installed, to Enable JTAG functionality
e: $ I believe i have permission delegation setup correctly
~project/esp/openocd-esp32 $ ls -l /dev/ttyUSB*
crw-rw-r-- 1 root plugdev 188, 0 Feb 1 14:03 /dev/ttyUSB0
crw-rw-r-- 1 root plugdev 188, 1 Feb 1 14:03 /dev/ttyUSB1

[ESP_igrr]

Given that you have installed the jumpers, it could be a bad connection (bad solder joint, or jumper not making contact with pin header). Also check that you don't have other FTDI devices connected to the same computer — OpenOCD might be trying to use one of them instead.

To check if the connection between FTDI chip and the pin header is okay, try connecting TDI pin to ground — you should get "saw 0x00 not 0x01" message. If you still get "saw 0x01" then the connection from FTDI chip to the pin header is broken. If you have an oscilloscope or logic analyzer, you can also use it to check other pins (TMS/TCK/TDO should be changing their state while OpenOCD interrogates the target).

[ed_mack]

Thank-you for feedback. Will review and attach logic analyzer tomorrow. Ed

[ed_mack]

Found a short on board, between MTCK and MTDO. Cleared short and OpenOCD ran as expected. Thanks for the help. Ed