ESP 32 wrover kit Linux OpenOCD

[zamek42@gmail.com]

Hi All,

I have a brand new ESP32 WROVER kit maybe it is V3, because it has ST7789V LCD driver. The TFT display demo and all other demos work well on it, but I cannot use openocd.
I use Debian linux x64. I've downloaded the openocd source from the github, I could compile and install it successfully. When I plug the board it occupies the /dev/ttyUSB0 and /dev/ttyUSB1.
when I try to start openocd I get this message:

openocd /s /usr/share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -c 'set ESP32_ONLYCPU 1' -f board/esp32-wrover.cfg

Open On-Chip Debugger 0.10.0-dev-gcdaf22fd (2018-01-17-13:51)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
1
adapter speed: 20000 kHz
esp32 interrupt mask on
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 : active_cpu: 0, changed to 1, reson = 0xffffffff
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 "/usr/local/share/openocd/scripts/target/esp32.cfg", line 44
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21

Is there a different config file for v3? I found esp32_devkitj_v1.cfg only.

thx
Zamek

[ESP_igrr]

Perhaps some jumpers on JTAG lines missing? Please check that you have four jumpers connecting MTDI, MTDO, MTCK, and MTMS between the FTDI and the ESP32.

[zamek42@gmail.com]

Hi,

Thx that was the problem. The output is as the documetation said, and I can verify blink.bin.
I tried to set gdb step by step as in the doc.
Both command line and eclipse said:

Connection timed out

xtensa-esp32-elf-gdb -x gdbinit build/blink.elf
GNU gdb (crosstool-NG crosstool-ng-1.22.0-61-gab8375a) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/blink.elf...done.
gdbinit:1: Error in sourced command file:
:3333: Connection timed out.
(gdb)

The gdbinit contains:
target remote :3333
mon reset halt
thb app_main
x $a1=0
c

thx a lot
Zamek

[giomar]

Just "a little bit" late, but I hope it could be useful for newbies like me:
the following error

Code: Select all

gdbinit:1: Error in sourced command file:
:3333: Connection timed out.

was caused by the fact that an openocd session must opened before and leaved running.

So, in a terminal in the folder "openocd-esp32" you should run (link):

Code: Select all

bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp32-wrover.cfg

and in another terminal in the folder "blink" you should run (link):

Code: Select all

xtensa-esp32-elf-gdb -x gdbinit build/blink.elf