V4 esp8266 gdbstub did not work , now it does...

[freeck]

Gdbstub combined with "Platform and Boards" (esp8266) version 2.0 and higher did not work.
It seems that the latest uart-functions compared to the older version (esp8266->1.6.5-947-g39819f0) behave differently.
So the workaround is to use boards.txt version "1.6.5-947-g39819f0".

[jantje]

Thanks for the input :-)

[jantje]

@freeck Did you get this to work with the newer versions already?

[freeck]

I reported this issue at esp8266/Arduino#2663
But unfortunately no response yet.
For the time being I keep using bsp v1.6 , and use the latest libraries from v2.3, that works fine for me until now....
Any suggestions how to tackle this issue would be welcome....

[jantje]

If I understand this is a issue for my hardware repository to state that only 1.6.5 is supported

[freeck]

Yes, correct.

When I get some inspiration I will digg into this problem once again, although this issue seems to be not an high priority one as nobody responses...

[jantje]

That is one of the disadvantages of being a early bird ;-)

[freeck]

Finally got some inspiration. Version 2.3 is working now (for 90%).
I overlooked a statement in my version of file gdbstub-cfg.h
#ifndef GDBSTUB_CTRLC_BREAK
#define GDBSTUB_CTRLC_BREAK 0 // this was set to 1 in version of release V1.6 and worked fine so far.
#endif_
" Is working for 90%" means that there is still a (minor) issue: the console output (ets_printf statements) is not redirected to the Eclipse debug console.
It seems that function "os_install_putc1(gdb_semihost_putchar1)" (file gdbstub.c) is not working or is overridden. However the ets_printf messages are sent to the serial port , so with a second serial port of my PC I am able to observe the messages.

[jantje]

Sounds good
You mean changing this line?
https://github.com/jantje/hardware/blob/master/jantje/ESP8266/libraries/gdb/gdbstub-cfg.h#L30

[jantje]

Some stuff has changed in cdt as well as to default enabled or not in regards to shown debug info.
So that may be a root cause as well

[freeck]

Sure, set the define to 0.

[jantje]

Will do when I get home

[freeck]

This case can be closed , I dont expect the root cause will be solved. There is a workaround (reported earlier in this thread) which is acceptable.

NOTE: Sending too much serial data to the terminal of Sloeber results in an issue reported here https://github.com/Sloeber/arduino-eclipse-plugin/issues/830#issuecomment-335477997.
So I use Realterm to handle the serial data.

[jantje]

I still havn't changed to 0 :-(

[jantje]

Did a commit for this one

[freeck]

When you get a message in de debugconsole like "...bogus information...." or something like that; check wether the gdbstub is realy installed in your target. You can check this by viewing the output of the serial port of the target: it should, after a reset, send debugmessage $T05#B9
And dont forget to set the buildoptions to -ggdb -Og

[jantje]

@freeck
Thanks but ... I first need to find my nodemcu as running nodemcu code on a lonin board might be the issue as well :-(