[support]

Hi,

OK, thanks for the GDB log. It looks like the FLASH programming code does not report any errors (code 0 below):

-data-evaluate-expression “\*\(\(unsigned\ \*\)0x3fff8014\)”
^done,value=”0″

so normally the program should work. Are you able to communicate with the board using the esptool.py? If yes, could you try reading the FLASH memory at addresses 0 and 0x10000 and comparing it with the OMC-<address>.bin files?  This should explain if the FLASH gets programmed at all.

We have also ordered a NodeMCU board and should get it by the end of March. We will check it once it arrives as post a detailed tutorial.

[support]

Hi,

The “Invalid configuration” would happen if you have accidentally deleted the file with per-configuration flags. The easiest workaround would be to re-create the project.

Please note that for new projects we recommend using MSBuild as it is faster and more flexible.

[support]

Hi,

Sorry, this is not supported on MSBuild yet. As a workaround, please try running pkg-config and adding the flags manually.

[support]

Hi,

This is expected as GNU Make uses absolute paths in the dependency files. Please try rebuilding the project (Build->Rebuild All) instead of just building it.

[support]

Hi,

It’s hard to say why this happens without seeing the debug log. Please enable gdb logging on the Advanced GDB Settings page and check the debug log for messages explaining the unexpected end of session.

If you are not sure, please attach the debug log here and we will help you pinpoint the problem.

[support]

Hi,

Thanks for your feedback. Although this is not possible now, we have added a note to the v5.3 feature list and will add an option to start renaming via a menu command.

[support]

Hi,

No problem. If you encounter further issues, feel free to contact us again.

[support]

Hi,

As usual with ESP8266, it’s hard to say for sure. Something on the board may be interfering with JTAG or something in the board firmware may be interfering with FLASH programming. As those things are not really documented, unfortunately we can only guess here.

BTW, you can use VisualGDB with the UART gdb stub as well (see this tutorial). This mode does not involve JTAG and should work if VisualMicro works as well.

Also feel free to attach the full gdb log so that we could check for common errors.

Regarding other questions:

1. The large project.bin file is actually not needed. It’s a default binary file containing ALL the sections from the image. It is useful on other targets like ARM or MSP430, but not on ESP8266 or ESP32. You can disable it via the VS Project Properties (Generate binary files = No). Manually programming the other 2 files should be sufficient (you can also use <SysGCC>\esp8266\esp8266-bsp\ESPImageTool.exe to program an ELF file via a COM port).
2. We never had to change the default sector/erase block sizes, but as those values are not well documented, we made them editable.
3. The names for the FLASH modes, frequencies, sizes, C1/C2 come from the esptool.py provided by Espressif and to our best knowledge specify the FLASH parameters that the ESP8266 device will use. On VisualGDB side selecting one of those changes the values in the ESP8266 image header (which is undocumented) similarly to what esptool.py does. Please double-check the exact semantics and meanings of those with Espressif.
4. The reset options you mentioned do not apply to JTAG programming. In fact, lack for reliable reset (that stops the CPU immediately after resetting before the ROM starts various background processes) is one of the main reasons why JTAG debugging is very unreliable compared to the GDB stub.

[support]

Hi,

This could happen if your firmware is putting the CPU to the sleep mode.

Please try the steps described in the following tutorial to enable the “connect under reset” mode: https://visualgdb.com/tutorials/stm32/sleep/

[support]

Hi,

Based on the log snippet you attached, this should work. Perhaps it is an extern “C” problem?

[support]

Hi,

This does indeed go beyond the scope of our product support, so our best advice would be to stop the debug session with the “Break all” command and check if the program is stopped on an unhandled exception or something similar.

If not, please consider asking on the STemWin forums as they should have a better knowledge of the library internals.

[support]

Hi,

Most likely some of the network parameters (IP address, subnet mask, gateway, etc) is not configured properly. Please refer to your University documentation on network configuration and connectivity to figure out correct IP addresses and network configuration.

[support]

Hi,

Thanks for clarifying this. It is actually a known behavior of gdb. When jumping to a line with a breakpoint, the breakpoint will get triggered after resuming the program as if the line got reached naturally.

It should not interfere with anything else; simply press F5 or F10 again to continue debugging.

[support]

Hi,

When we tested the OpenOCD SWO support with ST-Link, we could not get it to work reliably and gave up. There are several discussions online describing the OpenOCD commands to use (e.g. this), but we cannot recommend this approach due to low reliability.

Instead we recommend using the fast semihosting that comes with VisualGDB (simply enable it on the Embedded Frameworks page). It uses a memory buffer inside your chip to stream debug messages from your firmware to VisualGDB without stopping the core. This works very fast and is 100% reliable.

[support]

Hi,

This looks like a conflict between the system file provided by VisualGDB and the one that comes from STM32CubeMX. Please remove the reference to the default system init file via VisualGDB Project Properties -> Embedded Frameworks.

[Author]

Posts