[support]

Hi,

If killing OpenOCD via task manager doesn’t work, this looks like a USB driver/controller bug. Please try using a different USB port or a different computer. Also if you are using a VM, please try running it on real hardware instead as USB virtualization is sometimes buggy.

[support]

Hi,

Thanks for clarifying this. The common settings (like tab sizes) are unfortunately managed by the VS language service mechanism, so they have to be separate. All advanced formatting settings that come from VisualGDB (like indentation for classes/namespaces/functions) are actually inherited from the regular VC++ settings.

We understand this is annoying, however as the workaround is relatively simple (changing a very small set of options once), we don’t want to go hacking the language service internals and risk breaking something on a higher scale, sorry.

[support]

Hi,

The screenshots look OK, so it’s hard to say what is causing this. You can try holding SHIFT while right-clicking on the project – this will force all VisualGDB menu commands to appear.

Deleting .vgdbsettings files unfortunately won’t help as this will lose all VisualGDB settings associated with the project. Re-creating the project via the wizard and comparing the .vxcproj and .vgdbsettings files via a diff tool might help through.

We understand this is annoying and we will try to help you resolve it ASAP, so please follow the steps below to isolate it:

• Can you locate a specific project that fails to upgrade? If yes, what happens if you move add it to an empty solution (so that the solution will only have 1 project)?
• If the project still fails to upgrade, please locate a similar project that works, add it to another empty solution and double-check that it works. Then compare the .vxcproj files and .vgdbsettings files for the working and non-working project. If you don’t see anything out of the ordinary, please attach the files here (or send them via our support form) and we will check for common issues.

[support]

Hi,

Please try updating to the latest Nordic BSP based on SDK 14.0. It contains a few bugfixes, so it might simply fix this as well.

If it doesn’t help, please try building the project using Nordic command-line tools. You can do this by updating the <Nordic SDK>\components\toolchain\gcc\Makefile.windows as follows:

GNU_INSTALL_ROOT := E:/sysgcc/arm-eabi/bin/
GNU_VERSION := 6.2.0
GNU_PREFIX := arm-eabi

Then go to the directory of a sample project (e.g. examples\ble_peripheral\ble_app_hids_mouse\pca10056\s140\armgcc) and build the project by running “make”.

Finally first try debugging your regular VisualGDB project so that the softdevice is programmed, then replace its ELF file (without extension) by the .out file from the manually built project and try debugging again (select “do not rebuild” so that VisualGDB doesn’t rebuild its project). If the problem is also reproduced with the original Nordic firmware, it might be an incompatibility between your SDK and your device (in our experiments devices bought a couple of years ago did not work anymore with SDK 12.0 and simply buying a newer revision of the board solved the problem).

If the original Nordic example works, but the same example built with VisualGDB fails, it is definitely our bug and we will definitely fix it once we can reproduce it (or once you could run a few quick tests on your device that will pinpoint the difference).

[support]

Hi,

Those paths should be internally stored as relative paths. You can double-check it via VS project properties (not VisualGDB Project Properties) -> NMake -> Additional Include Directories.

VisualGDB applies a few internal transformation to the paths when storing them to allow portability across different machines, so the displayed paths are shown as expanded full paths to avoid confusion.

[support]

Hi,

VisualGDB doesn’t support visualization of boost types out-of-the-box, however we do support natvis, so you can locate the current Boost visualization files and add them to your project.

See this tutorial for a detailed example: https://visualgdb.com/tutorials/custom/natvis/

[support]

Hi,

You can simply create a support ticket via https://sysprogs.com/support/ and provide a link to this forum.

[support]

Hi,

Thanks for checking this. If waiting for 10 minutes does not help, looks like we will need further information from your in order to resolve it. Please try following the instructions from the first part of the previous reply.

Regarding the ‘convert to MSBuild’, please try attaching a screenshot of your VisualGDB Project Properties window so that we could check for common problems.

[support]

Hi,

Yes, normally you can just use the regular “subdir” or “..\dir\subdir” syntax.

Also for many cases (like SDK directories), VisualGDB handles this automatically and uses generalized paths like $(BSP_ROOT) instead. Feel free to let us know more about your setup so that we could advise how to set it up in the easiest way.

[support]

Hi,

Thanks for your feedback. However unfortunately we are not able to pinpoint the problem based on this description. Please feel free to provide us more details if you would like our help resolving this.

[support]

Hi,

Please let us know the email associated with your license key so that we can check the status of your support.

[support]

Hi,

Please use Test->Run all tests or Test->Debug All Tests (or right-click on individual unit tests in Test Explorer) to run tests. Simply running a test project with F5 will not engage the extra logic for selecting tests and reporting/interpreting test results.

[support]

Hi,

It looks like VisualGDB did not manage to save one project file after modifying it (TC2.jpg). This sometimes happens if the project is not loaded correctly in the Solution Explorer, or if some other bug prevents it from being saved. Could you try locating the project that fails to update (e.g. by checking which of the projects did not get modified)? Does excluding it from solution solve the problem? If yes, could you compare that .vcxproj file with other .vxcproj files to see if some manual modifications could be causing this?

This problem also sometimes happens when you try pressing ‘upgrade’ while VS is still loading the projects, so simply waiting 10-15 seconds before pressing it may help.

With ‘missing toolchain ID’, the logic responsible for fixing it could get interrupted by broken toolchain updating process, so once you resolve problem #1, the problem #2 should get automatically resolved as well.

[support]

Hi,

OK, we have published a detailed tutorial showing how to use VisualGDB with TFS here: https://visualgdb.com/tutorials/ci/tfs/

Please try updating your VisualGDB to the latest v5.3 and follow the tutorial. Please try checking that the %VISUALGDB_DIR% variable is defined correctly in the command prompt window where you launch the build agent (it should not have a trailing ‘\’).

[support]

Hi,

Strange, it looks like a statement that should normally be added to non-MSBuild projects got added to an MSBuild-based one. Could it be that the same project combines both MSBuild and non-MSBuild configurations? Also if you could share the project file with us via support form, or post it here, this would help understand what is going on.

[Author]

Posts