Adding board.buildinfo as well...

I've tried uninstalling and reinstalling the extensions as well as VM.  Same results.

I also tried creating a new Arduino project with defaults and same results.

I checked the regedit setting for the microgdg.exe location, and I needed to copy the microgdb.exe to that location (C:\program files (x86)\VS\...Extensions\xaohtdp2.q2m\

I have run out of ideas and suggestions to try to fix this.


Edit:How can I tell if Microgdb is working correctly?  When i run it from a powershell, it executes, but I can't "target remote :3333"...  It doesn't produce any errors, but it also doesn't connect to a local openocd session.  To the best of my ability, I think I have the prerequisites installed, but something is just not right....


Anyone have any other ideas?
Thanks!!!

Thank for the reply!

"vmicro>debugger>Microsoft GDB Debugger" is enabled.

After uploading, "Debug>Attach To Process" attempts to start the debugger, but after 15 seconds it times out.

Attached are the GDB logs, and platform.txt for the ESP8266 that I created.

I am using the ESP8266 gdb and openocd from the sysprogs toolchain (enhanced for esp8266)   

When debugging, I launched openocd previously/separately to try to see gdb attach to it, but nothing seems to connect to it.

Maybe the logs will poing in the direction.  Thanks again for your support!
Steven

Useful info. I need to try it.

It is possible the sysprogs toolchain wants less instruction which would be an easy fix.

Can you tell me from where and what I need to install to replicate your tests?

questions

where is your platform.txt located?

why is the openocd pre init tool commented out?

please save your platform.txt in a simpler format. note the unicode when viewed here 
http://www.visualmicro.com/public_html/yabbfiles/Attachments/platform_008.txt

What external start command did you use

Hi Tim,

Have you had any luck replicating the issue with the sysprogs toolchain?  Is there any additional information I can help provide?

As an aside, i substituted a Segger Jlink for the Olimex hardware with the same results. (still able to use OpenOCD and GDB outside of VS/VM to load and debug programs, but not from within.)

Thanks for your continued support!
Steven

Yes, I suppose there is some hardware involved...

If you have either a NodeMCU, the connections are shown below.  Huzzah uses the same pin names, but the physical pin numbers are different.   

ESP8266 Signal      ESP8266 Pin      NodeMCU Signal      NodeMCU Pin      JTAG20 Signal      JTAG20 Pin
VDDPST              17                       VDD3V                      1 on J2              VDD                       1
VDD                      PAD                       GND                      2 on J2              GND                       4
MTDI              10                       GPIO12                      7 on J2              TDI                       5
MTMS              9                       GPIO14                      8 on J2              TMS                       7
MTCK              12                       GPIO13                      6 on J2              TCK                       9
MTDO              13                       GPIO15                      5 on J2              TDO                       13
EXT_RSTB              32                       RST                              3 on J1              nTRST or nSRST  3 (Olimex) or 15 (Segger)

These pinouts were borrowed from:  https://visualgdb.com/tutorials/esp8266/nodemcu/jtag/

The ESP8266 is a little quirky when jtag starts (It doesn't always respond to JTAG commands when a program is already running, but once GDB issues a "mon reset halt", the ESP8266 JTAG wakes up and listens to commands from that point forward.

I think once we can get microGDB talking to the ElfGDB, the reset of the details will sort themselves out as GDB is GDB (I hope).

Hi Tim,

I'll be happy to work with the scripts and options, and once a stable set is found, I will share back with the group so that others can benefit from the findings as well.

It isn't possible for you to try to manage every slight variation in boards, and empowering the users closest to the hardware to fix their own problems is a force multiplier.

I'll look forward to the new version with options.
Thanks,
Steven