EVK-NINA-W10 JTAG Debugger issue

Dmytro_Medvid
Posts: 5
Joined: Tue Sep 04, 2018 6:39 am

EVK-NINA-W10 JTAG Debugger issue

Postby Dmytro_Medvid » Wed Sep 12, 2018 6:36 am

I`m trying to launch debug session in Eclipse with OpenOCD. Error log is the next:

OpenOCD log:

Code: Select all

Open On-Chip Debugger 0.10.0-dev (2018-07-24-09:39)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 100 kHz
esp32 interrupt mask on
Started by GNU ARM Eclipse
Info : clock speed 100 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 225): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 225): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 225): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: cpu0: esp32_fetch_all_regs (line 255): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 255): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 255): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : Target halted. PRO_CPU: PC=0x00000000 (active)    APP_CPU: PC=0x00000000 
Error: cpu0: xtensa_write_memory (line 759): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 759): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 759): 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 'esp_smp_break_config' 
in procedure 'esp32' called at file "OpenOCD_CFG\esp32.cfg", line 54
in procedure 'ocd_bouncer' 
in procedure 'esp_core_halt' 
in procedure 'esp32' called at file "OpenOCD_CFG\esp32.cfg", line 44
in procedure 'ocd_bouncer' 
at file "embedded:startup.tcl", line 21

Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : cpu0: Failed reading 4 bytes at address 0x3FF00030
Error: Failed to read target memory (-4)!
cpu0: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
cpu1: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
Info : accepting 'gdb' connection on tcp/3333
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : cpu0: Failed reading 5880 bytes at address 0x40090000
Error: no working area available, can't alloc space for stub code!
Error: Failed to load stub (-308)!
Error: Algorithm run faied (-308)!
Error: Faied to run flasher stub (-308)!
Error: Failed to get flash mappings (-308)!
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Eclipse log:

Code: Select all

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
Remote communication error.  Target disconnected.: No error.
Jumpers position:
Image

Any ideas?

ESP_Sprite
Posts: 8926
Joined: Thu Nov 26, 2015 4:08 am

Re: EVK-NINA-W10 JTAG Debugger issue

Postby ESP_Sprite » Wed Sep 12, 2018 8:10 am

Code: Select all

Error: JTAG scan chain interrogation failed: all ones
This usually indicates a connection problem between the jtag-interface and the ESP32. It can also occur if you reconfigure the GPIOs used for JTAG for something else in your program.

Dmytro_Medvid
Posts: 5
Joined: Tue Sep 04, 2018 6:39 am

Re: EVK-NINA-W10 JTAG Debugger issue

Postby Dmytro_Medvid » Wed Sep 12, 2018 12:54 pm

The problem was in .cfg file for OpenOCD module. I`ve added next lines:

Code: Select all

ftdi_layout_init 0x0008 0x000b
reset_config none
And all works now)

Who is online

Users browsing this forum: No registered users and 68 guests