[support]

Hi,

No, that should be sufficient. VisualGDB will warn that the stub is not included and the debugging won’t work, but if you ignore the warning, the programming will still succeed.

You can also use the ESPImageTool.exe from the toolchain directory to program the binary directly.

[support]

Hi,

If you are using the GDB stub, it will wait for the debugger to connect after each restart, i.e. the device won’t start without a debugger until you disable the gdb stub.

[support]

Hi,

Please check the ActivityLog.xml file mentioned in the error message for detailed error records. This should explain why VisualGDB is not initializing.

Either way, please try reinstalling VisualGDB as it would repair any corrupt files.

[support]

Hi,

Unfortunately the ESP8266/ESP32 devices are not very reliable and often behave unpredictably. We could quickly check if your firmware works with our Olimex ESP8266-EVB to see if the problem is in the board or in the firmware. Feel free to archive your project (with the binaries) and upload it to a file hosting so that we could check it.

[support]

Hi,

Thanks, we will update this post once the support for handcrafted PCH file is available. In the meanwhile feel free to attach the logs from the Clang IntelliSense Diagnostics Console showing the slow parse and we can advise you on possible workarounds (it usually happens then VisualGDB fails to cache rarely modified parts of the files properly).

[support]

Hi,

No problem. If you are using MSBuild, you can use the regular VS Project Properties as well. For other build systems like GNU Make the VisualGDB Project Properties will be the right place to go.

[support]

Hi,

It depends on what your goal is. The values in the XML file are copied from the default values for your MCU when you convert the project to a stand-alone one. They are propagated to the actual Makefile (or MSBuild property sheet file) once you change settings on the first page of VisualGDB Project Properties.

If you are not sure, we would recommend checking in the entire project to a source control system like git or SVN and then changing the parts that look suspicious and observing the outcome. You can also just change the FLASH/RAM Size/Base. Those settings are only used in GUI hints and the memory explorer and don’t directly affect compilation.

[support]

Hi,

Thanks for the updated log. The stack address now looks writable, so the problem must be caused by something else. It could be memory corruption somewhere in your code, or a hardware problem.

Can you reproduce the same behavior with the basic LEDBlink project or does it work as expected?

[support]

Hi,

According to your log, the program exits normally with code 1. This usually indicates an error, so please check the Program Output window for the error messages shown by the program.

[support]

Hi,

Sorry, there is not much documentation on this one. DEBUG_DEFAULT_INTERRUPT_HANDLERS is a preprocessor macro used in an #ifdef statement, so it should be specified in the place where other preprocessor macros are. It is different for different project types, but generally opening the Build Settings page of VisualGDB Project Properties, locating a similarly named field and adding the macro there should be sufficient to get it working.

[support]

Hi,

Looks like your STL might be using a slightly different internal representation than VisualGDB is used to.

Please try reproducing the “no member named _M_data” again and then evaluate the following expression in the Watch window:

*((std::__cxx11::list<UnidentifiedPod, std::allocator<UnidentifiedPod> >::_Node *)<<ADDRESS>>)

Note that the address and the type must match the one reported in the GDB session window (will change between debug sessions)

[support]

Hi,

Thanks for reporting this, looks like a bug on our side. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.15.1444.msi

[support]

Hi,

VisualGDB Project Properties does not support editing the FLASH/SRAM addresses as they are usually defined by us in the BSPs. Looks like your project is a stand-alone project, so you can modify the FLASH/RAM parameters directly in the stm32.xml file:

    <FamilyID>STM32F4</FamilyID>
    <FLASHSize>1048576</FLASHSize>
    <RAMSize>196608</RAMSize>
    <FLASHBase>134217728</FLASHBase>
    <RAMBase>536870912</RAMBase>

[support]

Hi,

Thanks for the detailed log. It looks like the _estack value in your image does not match the one in our linker script and it ends up pointing outside the RAM area on your chip, causing runtime errors. Please fix the value of _estack so that it points at the actual end of RAM.

VisualGDB should normally show a warning that the end of stack is not writable; if this does not happen, please let us know and we will investigate and fix.

[support]

Hi,

It is included in the latest BSP update the is currently undergoing tests. We would expect it to be released in the next 1-2 weeks.

[Author]

Posts