wrover windows JATG debug issues (wiring and schematics)

[snahmad75]

Hi,

I am using

Platform : Windows 7

Visual studio 2015.

Olimex ARM-UDB-OCD-H is attached to SD card for JTAG wrover.



using latest ESP32 master branch.


gdb on command line also not working. but Visual GDB works for simple project like hello world. where external RAM is not enabled.
Also we found we have to SD card to connect JTAG. then while application is running for debug. we cannot use SD card. kindly give us wiring and schematics.


C:\SysGCC\esp32\esp32-bsp\OpenOCD\bin\openocd.exe -c “gdb_port 51250” -c “telnet_port 51251” -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -c “adapter_khz 3000” -f target/esp32.cfg -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.9.0 (2018-10-12)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 3000 kHz
Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
esp32 interrupt mask on
VisualGDB_OpenOCD_Ready
Info : clock speed 3000 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 “target/esp32.cfg”, line 54
in procedure ‘ocd_bouncer’
in procedure ‘esp_core_halt’
in procedure ‘esp32’ called at file “target/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/51250
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

Thanks,
Naeem

[permal]

I tried so much to get that very same Olimex device to work, but gave up. I'm now using Wrover Kit v3 (+ a custom beak out board) for debugging and program loading. It just works.

[snahmad75]

Hi,

Kindly elaborate more with regard to wiring and schematics. Are using command line gdb or using visual GDB with visual studio?
Are you wrover with SD card mount as well. point to schematics diagram.


have you tried using ESP-WROVER-KIT 4.1

https://docs.espressif.com/projects/esp ... r-kit.html

[permal]

Espressif's own schematics show all that's needed. I'm using SD Card in SPI mode while debugging - MMC can't be used since it shares the pins with JTAG. Command line only (I build and test most code on Linux to avoid debugging on target).

I have not tried the Wrover kit v4.

[snahmad75]

ok, my hardware is using MMC SD card. so it shares pins with JTAG. I can debug without mouting SD card in my code.. still does not debug using olimex arm-usb-ocd-h openocd

Can you share command line for openocd . where can i get download binaries and cfg and other files i need to start openocd via command line and try command line gdb.

[permal]

ok, my hardware is using MMC SD card. so it shares pins with JTAG. I can debug without mouting SD card in my code.. still does not debug using olimex arm-usb-ocd-h openocd

Can you share command line for openocd . where can i get download binaries and cfg and other files i need to start openocd via command line and try command line gdb.

As I wrote in my first reply, I did not get JTAG debugging to work with the Olimex device. Others seems to have managed to get it to work (search the forum), but I did not so I am now using the Wrover v3 kit.

[snahmad75]

ok, i will try with Wrover v3 kit. i guess Wrover v3 kit comes with built in JTAG