- This topic has 5 replies, 2 voices, and was last updated 6 years, 11 months ago by
.
-
Posts
-
Hello.
My setup is the following:
- Visual studio 2017 community
- Latest VisualGDB
- Feather esp8266 (adafruit)
I connected my J-link edu to the JTAG pins of the board but I cannot debug.
Here is the output:
<h6>C:\SysGCC\esp8266\esp8266-bsp\OpenOCD\bin\openocd.exe -c “gdb_port 13831” -c “telnet_port 13832” -f interface/jlink.cfg -f target/esp8266.cfg -c “adapter_khz 3000” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.9.0 (2015-11-04-20:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
stop_wdt
adapter speed: 3000 kHz
VisualGDB_OpenOCD_Ready
Info : J-Link ARM V8 compiled Nov 28 2014 13:44:46
Info : J-Link caps 0xb9ff7bbf
Info : J-Link hw version 80000
Info : J-Link hw type J-Link
Info : J-Link max mem block 9224
Info : J-Link configuration
Info : USB-Address: 0x0
Info : Kickstart power on JTAG-pin 19: 0xffffffff
Info : Vref = 1.656 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 1 TRST = 1
Info : J-Link JTAG Interface ready
Info : clock speed 3000 kHz
Info : TAP esp8266.cpu does not have IDCODE
Info : halted: PC: 0x40000f68
Info : debug cause: 0x20
Info : accepting ‘gdb’ connection on tcp/13831
Info : TAP esp8266.cpu does not have IDCODE
Warn : xtensa_deassert_reset: ‘reset halt’ is not supported for Xtensa. Have halted some time after resetting (not the same thing!)
Error: timed out while waiting for target halted
TARGET: esp8266.cpu – Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer'</h6>
<h6>Info : TAP esp8266.cpu does not have IDCODE
Warn : xtensa_deassert_reset: ‘reset halt’ is not supported for Xtensa. Have halted some time after resetting (not the same thing!)
Error: timed out while waiting for target halted
TARGET: esp8266.cpu – Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer'</h6>
<h6>Warn : WARNING! The target is already running. All changes GDB did to registers will be discarded! Waiting for target to halt.
Info : Halt timed out, wake up GDB.
Warn : target esp8266.cpu is not halted
Warn : target not halted</h6>
I also attach a picture of the JTAG test.Thanks,
Vasileios
Hi,
Looks like the target is identified properly, but something goes wrong when OpenOCD tries to reset it. Please try connecting the reset pin to JTAG pin #3 or #15 (different JTAG debuggers use different pins). If nothing helps, please try disconnecting it completely and selecting a different reset method.
Hello.
So, I now tried a different reset pin.
I get the message “All reported device registers have a value of 0. …”.
When I connect the other reset pin, I get the same message again.
The device is not broken however, I can program it from the Arduino IDE.
Any ideas?
Hi,
The Arduino might be using the built-in bootloader, not JTAG. In this case the problem could be caused by JTAG wiring issues (cross-talk, bad soldering, etc). In case of weird JTAG problems we usually recommend using one of the boards that listed in our tutorials, replicating the wiring 1-to-1 and once you get it to work, switching the setup to your regular board.
The problem could also be software-related (sometimes ESP8266 firmware modifies some undocumented ESP8266 registers making debugging impossible). In this case erasing the FLASH memory via the bootloader and esptool.py and then programming it again might help.
- You must be logged in to reply to this topic.