[support]

Hi,

Our ESP8266 toolchain only includes the libraries shipped with the RTOS and non-OS SDKs; if you want to use external libraries, you indeed need to download them (we recommend saving them outside the toolchain directory to avoid losing them during a toolchain update).

[support]

Hi,

VisualGDB would put the sources into AutoDownloadedSources if it doesn’t know how the Windows path corresponding to them. Could you please give an example of a file (i.e. full path) that gets opened via this mechanism and let us know your shared folder settings (a screenshot or a summary of used paths)?

Regarding “Go to Definition”. Please try locating the source file that should normally contain the definition of the symbol and check that:

• It is included in one of the open projects in Solution Explorer
• Physically present on the disk and accessible via VS
• Does not show any critical errors when opened from VS

Please also try enabling the Clang IntelliSense engine – it uses a different mechanism for locating definitions and should work better with remote projects.

[support]

Hi,

Thanks for the attached file. It does look like STM32CubeMX references a file that is not copied (and not actually needed, as removing it from the .vcxproj file fixed the problem). It also doesn’t mention the USE_FULL_LL_DRIVER macro anywhere in the gpdsc file. This could be a bug worth reporting to ST and if it’s not fixed in one of the next STM32CubeMX updates, we will consider adding logic for detecting this and automatically adding the macro and skipping the missing file.

[support]

Hi,

Please try clicking on “Debug using” and then select “USB Devices”. It should recognize your USB-to-COM bridge and let you select it there.

[support]

Hi,

STM32 devices should normally include the “Fixed stack/heap” framework. Are  you using a custom project or an mbed-based project?

[support]

Hi,

No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.17.1957.msi

It will show detailed information on toolchain selection logic via View->Other Windows->VisualGDB Diagnostics Console. Please share the output from that window and we should be able to fix this.

[support]

Hi,

Please find the answers to your questions below:

1) The mbed codebase is very volatile, so workarounds that worked with the latest version supported by us may not work with the latest one. We only recommend using the generator if you are OK resolving this type of issues (or getting paid out-of-schedule BSPs from us if you prefer).

The hardware register definitions use a different format than ARM SVD (providing higher-level detail). VisualGDB can automatically convert SVD to its internal XML format as well, however the STM32 definitions are based on parsing the STM32 header files as the provide more details. If your MCU definition file is not recognized, please ensure that the <MCU> element in BSP.XML refers to it via the <MCUDefinitionFile> element.

2) The specs-related settings look the same as for our regular toolchain, so it’s hard to say why they would behave differently. Please try checking the exact gcc command line VisualGDB uses (for Makefile projects it’s displayed by default, for MSBuild projects is shown after you increase the build log verbosity). Does the command line make sense? Does manually adding the -L<specs directory> to the command line help? Is the command line different from the one used by your previous build method (e.g. is it missing some extra arguments)? If you are not sure, please post the gcc command line from VisualGDB build, the gcc command line from your current build system and the error messages shown by VisualGDB.

5) Please try following this tutorial. It provides an example of importing a project with generating a VisualGDB Makefile.

[support]

Hi,

The “Fixed stack and heap” is only available on BSPs with linker scripts are generated by VisualGDB. If you are using a different BSP, you would need to edit the linker script manually (the exact steps depend on the device type) and also specify the stack bounds on the Dynamic Analysis page so that VisualGDB could verify it.

[support]

Hi,

If the files are referenced by the gpdsc file, it could be our bug. Please feel free to attach the generated gpdsc file (and files copied by STM32CubeMX) and we could quickly investigate whether this is something we could fix.

[support]

Hi,

ESP8266 supports only one hardware breakpoint. If you would like to set more breakpoints, please try moving some of your functions to RAM by declaring them with ICACHE_FLASH_ATTR.

If you don’t want to use the gdb stub, simply disable the call to gdbstub_init().

Regarding the empty com port list, please try attaching a screenshot of this so that we could see what is going on.

[support]

Hi,

Sorry, avrdude unfortunately doesn’t support debugging. Our best advice would be to try patching AVaRICE to add support for your device (it conveniently stores device descriptions in a single table in the source code), however we cannot guarantee that this would work.

[support]

Hi,

No problem, we have added an automatic warning for this case in the upcoming v5.3R8.

[support]

Hi,

Switching FLASH mode to “DIO” likely did the trick.

Regarding the breakpoint issue, please attach a full GDB log as shown here so that we could help you diagnose this.

[support]

Hi,

We haven’t tested VisualGDB with LL projects yet, however this looks like the GPDSC file references some sources that were not copied by the STM32CubeMX tool. You could check this by examining the gpdsc file (or we could check this for you if you could attach the screenshots of your STM32CubeMX settings). If it appears that STM32CubeMX indeed doesn’t copy the files, please file a bug report with ST. If the files are copied to a different location or a named differently, please let us know and we will add a workaround.

[support]

Hi,

No problem, we have a detailed tutorial explaining how to use the dynamic analysis to verify the stack size: https://visualgdb.com/tutorials/arm/stack/

[Author]

Posts