[support]

Hi,

Please try updating to VisualGDB 5.5 Preview 5. It includes automatic troubleshooting for missing references.

[support]

Hi,

No problem, we have updated VisualGDB’s IntelliSense engine to properly handle the “-x c++” flag for .c file in MSBuild projects. Please try this build: VisualGDB-5.5.5.3602.msi

Please make sure you delete the CodeDB folder before you open the solution, as it would contain cached settings from the previous version.

[support]

Hi,

Normally this should work. Please make sure you restarted VS from the Start menu (not from another program) after defining the new environment variable, as the environment is not immediately applied to all existing processes.

If it doesn’t help, please check the .vcxproj file and the .rsp files (you can read more about the .rsp  files here) for the definition of the macro and also double-check it with running “echo %FOOSTR%” from Command Prompt.

If nothing helps, please share the contents of the .rsp file, the .vcxproj file and the output from echo %FOOSTR% and we can recheck for common issues.

[support]

Hi,

The “Add Folder Recursively” command is still supported, however it only works with VC++-based projects and requires the Custom edition or higher.

[support]

Strange. Running the synchronization as Administrator should get the symlinks to work. Please double-check that you actually run the correct instance of Visual Studio as Administrator. If it doesn’t help, please try checking whether the mklink command works. If this doesn’t help, please let us know which Windows version you are using.

The FILE structure should be declared in <sysgcc>\raspberry\arm-linux-gnueabihf\sysroot\usr\include\arm-linux-gnueabihf\bits\types\FILE.h. Please check whether the file exists. If not, please try enabling SysprogsSync logs via Tools->Options->VisualGDB->General->SSH->Log SysprogsSync Transfers and then check the log file for errors in nearby directories.

If it doesn’t help, please upload the log file to a file hosting service (e.g. DropBox) and share a link to it so that we could check what is going on.

[support]

Hi,

Please try resetting the Python environment as shown here: https://visualgdb.com/documentation/espidf/#python

[support]

Hi,

It looks like the first set of warnings refers to unreadable target directories that should not be related to the build, so you can safely ignore them.

The second set of warnings looks like Windows does not allow creating symbolic links for some directories. Please double-check that the toolchain is installed on a NTFS volume (required for symlinks). If it doesn’t help, please try running Visual Studio as Administrator, as sometimes symlink problems are caused by missing permissions.

[support]

Hi,

This is a known bug in the STM32CubeMX generator. It doesn’t properly escape the “&” symbol in the generated XML files (i.e. produces “value1&value2” instead of “value1&amp;value2”). The easiest workaround would be to patch the file manually before importing it into VisualGDB.

Please also consider reporting this to ST, as the issue is on their side.

[support]

Thanks, we have reproduced the problem and fixed it in the following build: VisualGDB-5.5.5.3599.msi

Let us know if you encounter further issues and we will be happy to help.

[support]

Hi,

No problem, we have a very detailed tutorial on creating custom projects that are not directly supported: https://visualgdb.com/tutorials/arm/legacy/

We have also open-sourced our tools for generating BSPs, so you can simply fork one of the similar BSP generators here: https://github.com/sysprogs/BSPTools/

Alternatively, we can do the necessary research and create a BSP based on your requirements as a part of our paid BSP program. Feel free to contact our sales if you would like to get a quote.

[support]

OK, we have updated VisualGDB to work with the latest MCUXpresso SDK: VisualGDB-5.5.5.3597.msi

For multi-core devices, it will create a separate device entry for each core (e.g. LPC55S69_CM33_CORE0), so you can choose a specific core when creating a project.

Please note that the example you mentioned (lpcxpresso55s69_host_suspend_resume_hid_mouse_freertos) does not build under the MCUXpresso IDE due to an error in the SDK definition. It will also not build with VisualGDB unless you manually resolve the build errors (same way as with the MCUXpresso IDE). Examples that build with MCUXpresso IDE will also build with VisualGDB.

Please refer to the regular Visual Studio documentation for steps on creating multiple projects in the same solution, they will work with VisualGDB as well.

[support]

Hi,

We have retested the STM32Nucleo-L476RG board with the latest ST-Link firmware (V2.J34.M25) and unfortunately still could not reproduce the problem. We would advise trying another board instead.

[support]

Hi,

Based on our experience, upgrading the project to a newer ESP-IDF release might be a non-trivial task, since different ESP-IDF versions are not 100% backward-compatible.

Our best advice would be to read the release notes and check how similar code examples changed between different versions.

[support]

Please note that our technical support covers the issues with VisualGDB only. We are not able to help troubleshooting specific projects, or resolve any issues in external tools.

[support]

Sorry, most likely the file was too large to be uploaded. Would you be able to upload it to a file sharing service (e.g. Dropbox) and share a link with us?

[Author]

Posts