[gojimmypi]

Thanks for your reply. I’m looking at the ESP8266 tutorial here:

http://visualgdb.com/tutorials/esp8266/

I was about to order an Olimex ARM-USB-OCD-H per your suggestion, however:

The end of Step 1 says:

Note that we use the Olimex USB-OCD-H as a USB-to-COM adapter only as the Xtensa JTAG software does not support it (supported devices are listed below).

Which sounds like the OCD-H is *not* being used as JTAG, rather a simple USB-to-TTL (Rx/Tx) port?

Further down in Step 7 there’s a note:

VisualGDB supports 3 debug methods for ESP8266 devices:

• A special OpenOCD port that supports all JTAG programmers supported by the original OpenOCD
• Xtensa OCD Daemon (xt-ocd) that supports ML605, Flyswatter 1/2/3, Jtagkey 2, Olimex tiny-h, Segger J-link, ByteTools Catapult, RVI JTAG and Macraigor probes
• GDB stub from Espressif that does not requre a separate JTAG connection

Note it specifies a *different* Olimex device, the  “Olimex tiny-h” – which is listed as a USB JTAG device here: https://www.olimex.com/Products/ARM/JTAG/ARM-USB-TINY-H/

The ARM-USB-OCD-H is listed as a “3-IN-1 fast USB ARM JTAG, USB-to-RS232 virtual port and power supply 5VDC device” here:

https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/

and both of the products say “supported by OpenOCD arm debugger”

Am I misreading the tutorial? Could you please confirm the recommendation for ARM-USB-OCD-H despite what Steps 1 & 7 say? (I think they may actually be essentially the same device; the more expensive one including the Tx/Rx & power, eh?)

As I have no experience with these Olimex devices, any suggestions or clarifications will be greatly appreciated before I place an order. 🙂

Thanks

 

[gojimmypi]

actually, please disregard the question on “Cannot resolve the address of _estack” as apparently is can be ignored! I have it working with my MSP430!

https://sysprogs.com/w/forums/topic/problem-debugging-esp8266/

I’ll start a new topic regarding Bus Pirate and USB Blaster

[gojimmypi]

thanks a lot for prompt reply!

Indeed the x6989 is in that toolchain and it compiles successfully in Visual Studio 2015 Version 14.0.25431.01 Update 3 with VisualGDB 5.2

However, I am unable to single step the “blink” example:

1>—— Build started: Project: GDB-8, Configuration: Debug VisualGDB ——
1>  LEDBlink.cpp
1>  Linking ../VisualGDB/Debug/GDB-8…
1>  ——————- Memory utilization report ——————-
1>  Used FLASH: 578 bytes out of 46KB (1%)
1>  Used RAM: 24 bytes out of 2048 bytes (1%)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Your VisualGDB trial expires in 30 days!
C:\SysGCC\msp430-elf\bin\msp430-elf-gdb.exe –interpreter mi C:\workspace\GDB-8\VisualGDB\Debug\GDB-8
Cannot resolve the address of _estack. Skipping stack pointer validity check.

Any suggestions as to what I might be doing wrong?

Really my goal is to program the ESP8266/ESP32 however I don’t currently have any of the mainstream JTAG tools (I’ve tried my Altera USB Blaster and Bus Pirate without success using OpenOCD)…. so I thought this MSP430 might be easier to get acquainted with the VisualGDB software until I can get a Segger J-Link. (that’s a good JTAG interface for the ESP family, right?)

Thanks a lot 🙂

 

 

 

[Author]

Posts