OpenOCD not working with wrover-kit using OS X 10.12.6

clarkster
Posts: 47
Joined: Sat Sep 23, 2017 12:36 pm

OpenOCD not working with wrover-kit using OS X 10.12.6

Postby clarkster » Thu Nov 16, 2017 8:06 pm

I am attempting to get JTAG working with my wrover-kit. I am using OS X 10.12.6.

I first performed a clean install of ESP-IDF, the toolchain, and OpenOCD per your setup instructions. The only change I make is to install the esp folder in ~/Documents rather than ~/. I have adjusted my toolchain and IDF path accordingly.

Then I perform the JTAG procedure on https://esp-idf.readthedocs.io/en/lates ... rover.html. In the Configure USB Drivers section, under MacOS, I have a problem at step 4 where I am to run this command:

Code: Select all

bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg
I get this response:

Code: Select all

 Clarks-iMac-2:openocd-esp32 clark$ bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board
/esp32-wrover.cfg
Open On-Chip Debugger 0.10.0-dev-ga859564 (2017-07-25-00:19)
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
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 failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : esp32: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32: Core was reset (pwrstat=0xFF, after clear 0xFF).
Error: cpu0: esp32_fetch_all_regs (line 163): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 163): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 163): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: cpu0: esp32_fetch_all_regs (line 190): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 190): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 190): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : Target halted. PRO_CPU: PC=0x00000000             APP_CPU: PC=0x00000000 (active)
Error: cpu0: xtensa_write_memory (line 696): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 696): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 696): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 4 bytes at address 0x3FF5F064, data - a1, 3a, d8, 50, a1, 3a, d8, 50
embedded:startup.tcl:21: Error: 
in procedure 'init' 
in procedure 'ocd_bouncer' 
in procedure 'flash' 
in procedure 'ocd_bouncer' 
in procedure 'esp_core_halt' 
in procedure 'esp32' called at file "share/openocd/scripts/target/esp32.cfg", line 44
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21
The same error happens if I change the command to:

Code: Select all

bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp32-wrover.cfg
Possibly the error is caused by the fact that there are no drivers installed for the serial ports to the wrover-kit. If that is the case, possibly the procedure is incorrect because the procedure had me uninstall the driver in step 3.

Can anyone help me get JTAG working with the rover-kit?

clarkster
Posts: 47
Joined: Sat Sep 23, 2017 12:36 pm

Re: OpenOCD not working with wrover-kit using OS X 10.12.6

Postby clarkster » Fri Nov 17, 2017 4:04 am

I found my problem. I was using some of the GPIO that are needed for JTAG. Once I reconfigured to use other GPIO, my errors went away.

Who is online

Users browsing this forum: No registered users and 239 guests