[TvdVen]

This did resolve my issue, thank you 🙂

[TvdVen]

I can’t seem to edit my previous post anymore, but I seem to have stumbled upon the fix since then. Changing the default baud rate of 74880 in the uart_init_new() function to 115200 and setting the COM port baud rate to that same value has resulted in legible output. Thank you for the assistance!

[TvdVen]

Thank you for the advice. I have now connected a USB-to-UART cable to my ESP8266 (alongside the Segger J-Link), and succeeded in opening a raw terminal for the COM port.

I am receiving output on the COM port, but a lot more than the simple printf(“test”); that I am expecting, and it is all garbled (including the “test”).

I have experimented with a few of the settings, mostly baud rate, which I think should be set to 74880. This value is also what the uart_config is set to in uart_init_new() (see OP).

However, I have noticed that it works seemingly identically without calling uart_init_new(), so I am unsure whether this is necessary or what it is good for.

My output looks like this before my call to printf():

b??d???????????????????FC?????b?????????????????b???b?????D?????????????????b???b?????D??????????????????b???b?????D?????bG?B?SV@Y?VTRj1FXk?U?W?s5i?Ptm@ZhXxPd\2hY??X?!KefXIPPa?SV@YX[DGQm?QY*i?5tX?D+a_g??R\lRj!?1X63V?cv5GhG1i7_g??R^lRj!iVe??XYgWl\?D?{?Qv_%yhP?m*?[PPe??X?i?w?dXD

Printing “test” adds Z*i.

I doubt the garbled output will be helpful in helping you determine what might be going wrong, but do you have any suggestions as to what I could check/try?

• This reply was modified 6 years, 10 months ago by TvdVen.

[TvdVen]

Hi, thank you for the advice. I have since started using a Segger J-Link de debug rather than the GDB stub, and this has solved the problem (though it is not exactly clear to me how).

In case it might still help someone, I have attached a screencap of the settings that I am now using, though I had tried this permutation previously with the GDB stub without success.

Attachments:

You must be logged in to view attached files.

[TvdVen]

Hello,
Thank you for the suggestion, based on this I have tried every permutation of the following settings:

• GDB Stub Baud Rate 74800/74880/115200
• Bootloader Baud Rate 115200
• FLASH Mode QIO/DIO
• FLASH Frequency 40/26/20/80 MHz

No success, though.

To double check whether I even have the correct GND pin, I changed it, which results in a failure to connect to the bootloader before flashing even happens, so I believe the connection is correct.

I also, only now, thought to check whether flashing was actually successful (beyond the progress bar completing). Using the settings

[ GDB Stub Baud Rate 74880 / Bootloader Baud Rat 115200 / FLASH Mode QIO / FLASH Freq. 26 MHz / FLASH Size 2MB – c1 ] I am able to flash successfully (ESP8266 properly starts hosting a simple ‘Hello World’ web page, which I can connect to).

It’s nice to know that something is working, but unfortunately VisualGDB is still failing to connect to the GDB stub. Do you maybe have any other advice?

I’m going to try a different USB->UART cable next (I also have a second ESP8266 board, which I will try as well), in case there’s a hardware error (however unlikely).

Thanks for the help so far!

[TvdVen]

I am encountering this same issue, and have tried the steps suggested above.

(Except for UART_SetBaudrate(UART0,74880), these are undefined in HTTPDemo.cpp, am I missing an include perhaps?).

I am using the Visual Studio 2015 extension for VisualGDB on Win8.1.

I have tried the following GDB Stub Baud Rates: 74880, 115200 and 74800 (as shown in the example here).

I have left Bootloader Baud Rate at 115200.

The bitrate of my usb-serial com connection defaults to 9600, I am unsure if this is related.

When I ‘Test’ the debugging using Bootloader + GDB Stub from the debug settings a window pops up, but nothing is ever logged.

It appears to hang on ‘Connecting to stub…’ in the bottom left.

When trying to debug the project, the chip is flashed but connecting to the GDB stub times out with what appears to be the same output as OP.

“VisualGDB has encountered a problem while starting debugging: Failed to connect to the gdb stub. Please check your settings.”

Has a solution been found for this problem? Any advice will be appreciated 🙂

• This reply was modified 6 years, 11 months ago by TvdVen.
• This reply was modified 6 years, 11 months ago by TvdVen.
• This reply was modified 6 years, 11 months ago by TvdVen.

[Author]

Posts