[support]

Hi,

VisualGDB uses its own formatting engine, but it tries to import the VS settings that are similar to VisualGDB settings. Every version of VS has slightly different formatting settings, so this mechanism may sometimes be buggy. If you manage to reliably reproduce a case where VisualGDB does not follow VS formatting settings, please let us know the details and we will fix this.

[support]

Hi,

The “Error: JTAG scan chain interrogation failed: all zeroes” error almost 100% indicates a wiring problems (that also includes power and reset issues). Hence our best advice is to get exactly the same hardware as shown in the tutorial, get it to work and once you get a stable reference point, start experimenting with different boards.

[support]

Hi,

Yes, this is by design. If the typed text fully matches the selected suggestion, pressing ‘;’ would auto-complete that suggestion. We added a special exception for C/C++ keywords, but otherwise this behavior is still by design.

[support]

Hi,

We could add an option like that, but it could be confusing as the information will obviously be outdated (e.g. the offsets of function definitions will be old). Let us know which commands in your opinion would still be useful in such mode and we will consider adding this option.

[support]

Hi,

The “Add recursive” option is only available starting from the Custom edition. If you are using a lower edition, you can add files one directory at a time, or pick the root directory when importing the project.

Please note that when importing arbitrary 3rd-party code, you will most likely need to configure include paths and preprocessor macros, as VisualGDB cannot automatically guess them. You can find a detailed tutorial on this process here: https://visualgdb.com/tutorials/intellisense/headers/

[support]

Hi,

This may happen if your distro installs Qt5 in a location that VisualGDB cannot locate. Could you please try running “which qtchooser” from the command line and check if it is located properly?

[support]

Hi,

You might be using assembly files that are intended for a different compiler (e.g. Keil or IAR). Unfortunately unlike C/C++, the syntax of the assembly files is totally different for the different compilers (mainly when it comes to special directives, declaring symbols, etc) and they are not compatible with each other. Please double-check that your codebase contains a version of the assembly files that is compatible with GCC.

[support]

Hi,

This is expected if you are debugging optimized code (the mapping between source lines and the actual instructions is very inaccurate then).

If you can reproduce this in the unoptimized code, please provide us more details so that we could look into this:

1. A snippet from your source file with the line numbers
2. A snippet from the gdb log (or the ‘all gdb interaction’ mode of the GDB Session window) showing the commands and gdb responses that are executed in response to using the “Set next statement” command. This should explain what is going on.

[support]

Hi,

Please try enabling verbose mode for the linker via VS Project Properties -> Linker -> Advanced. This should produce a massive debug output showing ALL the libraries checked by the linker. If librtc.a is on the list, but the problem still occurs, please try running the <target>-nm tool on the library to get a list of all symbols in it and double-check that this version of the library actually contains that symbol.

[support]

Normally this should not be related. Let us know if the problem persists after fixing the sysroot synchronization.

[support]

Hi,

Normally tar should skip the inaccessible files and handle the rest, so the rest of the files should be synchronized properly (unless you see clues to the opposite, e.g. if the sync stops before the progress bar reaches the end).

[support]

Hi,

If you don’t want to add the linker script to Solution Explorer, you don’t need to modify template.xml at all. Just add the file in the archive and VisualGDB will extract it when it creates the project.

Regarding the warnings, we might be able to help if you could send us screenshots of your Solution Explorer, your VisualGDB Project Properties specifying the linker script and the warning. If you don’t want to upload them to an image hosting, you can simply send them to us via our support interface.

[support]

Hi,

VisualGDB supports both STM32CubeMX and mbed. Please refer to the following tutorials

• https://visualgdb.com/tutorials/arm/stm32/cube/
• http://visualgdb.com/w/tutorials/tag/mbed/

[support]

Hi,

We do have a tutorial on that already: https://visualgdb.com/tutorials/arm/stm32/cube/

[support]

Hi,

Looks like your cross-toolchain might be corrupt. Please try reinstalling it.

[Author]

Posts