[Debug] Fail to configure openocd - esp32DevKitC - ARM-USB-OCD-H

Arkaik
Posts: 13
Joined: Mon Jun 12, 2017 12:36 pm

[Debug] Fail to configure openocd - esp32DevKitC - ARM-USB-OCD-H

Postby Arkaik » Wed Jun 14, 2017 1:42 pm

Hi guys,

I'm currently trying to implement debug for my esp32DevKitC.
I followed this link http://esp-idf.readthedocs.io/en/latest ... enocd.html to do it.

At the step Configuring the ESP32 target in OpenOCD I have many errors when starting openocd.

I'm using Olimex ARM-USB-OCD-H probe so I added "source [find interface/ftdi/olimex-arm-usb-ocd-h.cfg]" to esp32.cfg.

Here is the trace.

Code: Select all

$ sudo ./src/openocd -s ./tcl -f ./esp32.cfg
Open On-Chip Debugger 0.10.0-dev-gde545d1 (2017-06-14-11:18)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 200 kHz
force hard breakpoints
Info : clock speed 200 kHz
Info : TAP esp32.cpu0 does not have IDCODE
Info : TAP esp32.cpu1 does not have IDCODE
Info : TAP auto0.tap does not have IDCODE
Info : TAP auto1.tap does not have IDCODE
Info : TAP auto2.tap does not have IDCODE
Info : TAP auto3.tap does not have IDCODE
Info : TAP auto4.tap does not have IDCODE
Info : TAP auto5.tap does not have IDCODE
Info : TAP auto6.tap does not have IDCODE
Info : TAP auto7.tap does not have IDCODE
Info : TAP auto8.tap does not have IDCODE
Info : TAP auto9.tap does not have IDCODE
Info : TAP auto10.tap does not have IDCODE
Info : TAP auto11.tap does not have IDCODE
Info : TAP auto12.tap does not have IDCODE
Info : TAP auto13.tap does not have IDCODE
Info : TAP auto14.tap does not have IDCODE
Info : TAP auto15.tap does not have IDCODE
Info : TAP auto16.tap does not have IDCODE
Info : TAP auto17.tap does not have IDCODE
Info : TAP auto18.tap does not have IDCODE
Warn : Unexpected idcode after end of chain: 21 0x0023ffff
Warn : Unexpected idcode after end of chain: 53 0x00000a80
Warn : Unexpected idcode after end of chain: 85 0x0002a800
Warn : Unexpected idcode after end of chain: 117 0x14000000
Warn : Unexpected idcode after end of chain: 149 0x000000a8
Warn : Unexpected idcode after end of chain: 181 0x203ffff5
Warn : Unexpected idcode after end of chain: 213 0x00002a00
Warn : Unexpected idcode after end of chain: 245 0xffda0000
Warn : Unexpected idcode after end of chain: 277 0x540003ff
Warn : Unexpected idcode after end of chain: 309 0x1fffe800
Warn : Unexpected idcode after end of chain: 341 0x00000000
Warn : Unexpected idcode after end of chain: 373 0x00005020
Warn : Unexpected idcode after end of chain: 405 0x2fc00000
Warn : Unexpected idcode after end of chain: 437 0x80000000
Warn : Unexpected idcode after end of chain: 469 0x0027ffff
Warn : Unexpected idcode after end of chain: 501 0x01bffe80
Warn : Unexpected idcode after end of chain: 533 0x00014000
Warn : Unexpected idcode after end of chain: 565 0xfe800000
Warn : Unexpected idcode after end of chain: 597 0x8000002f
Warn : Unexpected idcode after end of chain: 629 0x1001fffa
Error: double-check your JTAG setup (interface, speed, ...)
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.cpu0: Debug controller was reset (pwrstat=0xFF, after clear 0xFE).
Info : esp32.cpu0: Core was reset (pwrstat=0xFF, after clear 0xFE).
Info : esp32.cpu1: Debug controller was reset (pwrstat=0xFF, after clear 0x00).
Info : esp32.cpu1: Core was reset (pwrstat=0xFF, after clear 0x00).
Info : esp32.cpu1: Debug controller was reset (pwrstat=0xFF, after clear 0xA0).
Info : esp32.cpu1: Core was reset (pwrstat=0xFF, after clear 0xA0).
Info : esp32.cpu0: Debug controller was reset (pwrstat=0xFF, after clear 0x00).
Info : esp32.cpu0: Core was reset (pwrstat=0xFF, after clear 0x00).
Error: esp32.cpu0: esp108_fetch_all_regs (line 470): DSR (00000154) indicates target still busy!
Error: esp32.cpu0: esp108_fetch_all_regs (line 494): DSR (8100001F) indicates target still busy!
Error: esp32.cpu0: esp108_fetch_all_regs (line 494): DSR (8100001F) indicates DIR instruction generated an exception!
Error: esp32.cpu0: esp108_fetch_all_regs (line 494): DSR (8100001F) indicates DIR instruction generated an overrun!
Error: Exception reading windowbase!

Info : esp32.cpu0: Target halted, pc=0x00000000
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (007FFE95) indicates target still busy!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3FF60064
embedded:startup.tcl:21: Error: 
in procedure 'init' 
in procedure 'ocd_bouncer' 
in procedure 'pld' 
in procedure 'ocd_bouncer' 
in procedure 'esp_core_halt' 
in procedure 'esp32.cpu0' called at file "./tcl/target/esp32.cfg", line 40
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21

Error: esp32.cpu1: esp108_fetch_all_regs (line 494): DSR (8000001F) indicates target still busy!
Error: esp32.cpu1: esp108_fetch_all_regs (line 494): DSR (8000001F) indicates DIR instruction generated an exception!
Error: esp32.cpu1: esp108_fetch_all_regs (line 494): DSR (8000001F) indicates DIR instruction generated an overrun!
Error: Exception reading sar!

Info : esp32.cpu1: Target halted, pc=0x00000000
esp32.cpu1: target state: halted
Error: Exception reading pc!

Info : esp32.cpu1: Target halted, pc=0x00000000
esp32.cpu1: target state: halted
Error: Exception reading lend!

Info : esp32.cpu0: Target halted, pc=0x00000000
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (000027FF) indicates target still busy!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (000027FF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (000027FF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3FF60064
embedded:startup.tcl:21: Error: 
in procedure 'esp_core_halt' 
in procedure 'esp32.cpu0' called at file "./tcl/target/esp32.cfg", line 40
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21

esp32.cpu0: target state: halted
Info : esp32.cpu1: Core was reset (pwrstat=0x3F, after clear 0x00).
Error: esp32.cpu0: esp108_fetch_all_regs (line 494): DSR (8000015F) indicates target still busy!
Error: esp32.cpu0: esp108_fetch_all_regs (line 494): DSR (8000015F) indicates DIR instruction generated an exception!
Error: esp32.cpu0: esp108_fetch_all_regs (line 494): DSR (8000015F) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : esp32.cpu0: Target halted, pc=0x00000000
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (00003FFF) indicates target still busy!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (00003FFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (00003FFF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3FF5F064
embedded:startup.tcl:21: Error: 
in procedure 'esp_core_halt' 
in procedure 'esp32.cpu0' called at file "./tcl/target/esp32.cfg", line 37
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21

esp32.cpu0: target state: halted
Info : esp32.cpu0: Debug controller was reset (pwrstat=0xF0, after clear 0x00).
Info : esp32.cpu0: Core was reset (pwrstat=0xF0, after clear 0x00).
Error: Exception reading configid0!

Info : esp32.cpu1: Target halted, pc=0x00000000
esp32.cpu1: target state: halted
Info : esp32.cpu0: Debug controller was reset (pwrstat=0x5F, after clear 0x00).
Info : esp32.cpu0: Core was reset (pwrstat=0x5F, after clear 0x00).
Info : esp32.cpu0: Debug controller was reset (pwrstat=0xF4, after clear 0x00).
Info : esp32.cpu0: Core was reset (pwrstat=0xF4, after clear 0x00).
Info : esp32.cpu0: Debug controller was reset (pwrstat=0x50, after clear 0x00).
Info : esp32.cpu0: Core was reset (pwrstat=0x50, after clear 0x00).
Error: esp32.cpu0: esp108_fetch_all_regs (line 470): DSR (A800053F) indicates target still busy!
Error: esp32.cpu0: esp108_fetch_all_regs (line 470): DSR (A800053F) indicates DIR instruction generated an exception!
Error: esp32.cpu0: esp108_fetch_all_regs (line 470): DSR (A800053F) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : esp32.cpu0: Target halted, pc=0x00000000
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (0000FFFF) indicates target still busy!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (0000FFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (0000FFFF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3FF5F048
embedded:startup.tcl:21: Error: 
in procedure 'esp_core_halt' 
in procedure 'esp32.cpu0' called at file "./tcl/target/esp32.cfg", line 38
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21

esp32.cpu0: target state: halted
Error: Exception reading lcount!

Info : esp32.cpu1: Target halted, pc=0x00000000
esp32.cpu1: target state: halted
Info : esp32.cpu0: Core was reset (pwrstat=0xFE, after clear 0x00).
^CError: Exception reading pc!

Info : esp32.cpu0: Target halted, pc=0x00000000
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (016FFFFF) indicates target still busy!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (016FFFFF) indicates DIR instruction generated an exception!
Error: esp32.cpu0: xtensa_write_memory (line 845): DSR (016FFFFF) indicates DIR instruction generated an overrun!
Warn : esp32.cpu0: Failed writing 4 bytes at address 0x3FF5F048
embedded:startup.tcl:21: Error: 
in procedure 'esp_core_halt' 
in procedure 'esp32.cpu0' called at file "./tcl/target/esp32.cfg", line 38
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21

esp32.cpu0: target state: halted


Who is online

Users browsing this forum: Google [Bot] and 80 guests