[support]

Hi,

It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey​

[support]

The window should normally activate automatically as per tutorial and does not depend on the Visual Studio version.

In general, some VisualGDB settings look alike and it’s very easy to inadvertently break things by selecting an incompatible combination of settings. If you are new to VisualGDB, we advise following the tutorials as close as possible. If VisualGDB doesn’t work the way you expect, please provide the repro steps including all relevant screenshots as suggested earlier, and we will try to point out what could be causing the issue.

Due to the sheer amount of different project types and configurations, we will not be able to suggest anything meaningful without seeing the full context of the issue.

[support]

Hi All,

Build issues like this one are often caused by subtle differences in the configuration (spaces in paths, environment, SDK versions), so in order to troubleshoot them efficiently we always ask our users to reduce them to a specific parameter controlled by VisualGDB, such as the CMake command line. Based on your screenshot, everything works as expected – the first line of the configuration log is an exportable command line shown in cyan, as shown in the documentation page.  The build log is not shown yet because the project configuration has not succeeded. Please follow our instructions from our previous reply in order to capture and edit the build command. Once you can confirm that adjusting the command line solves the issues, please share both batch files, and we will update VisualGDB to adjust the command line accordingly.

[support]

Hi,

If VisualGDB is not working as per tutorial, please provide the complete and detailed steps to reproduce the issue as described below:

1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

[support]

Good to know it works. In general, the “empty project” option simply strips all sources from original project template. It cannot automatically determine which of these sources would be needed in each specific scenario, so it may indeed involve some trial-and-error to figure that out. Having a working project based on the full template as a comparison could be a good reference point.

[support]

Thanks, we have reproduced the issue. It is triggered by selecting “Empty project” on the Sample Selection page of the wizard. This option assumes that you are familiar with the underlying SDK and can add all the necessary files manually.

Please try selecting “Default project” instead – it will import a sample project from the SDK itself, that should include all the necessary files.

That said, with this specified SDK, you will need to manually reference the AtmelStart framework via VisualGDB Project Properties -> Embedded Frameworks. We will address this in the next VisualGDB version; until then, please reference the framework manually after creating a project.

[support]

Thanks for the detailed repro steps. The issue was triggered by adding folders to first-level Solution Explorer nodes with source/header filters disabled. As it is a relatively rare scenario, it makes sense why it wasn’t caught by our tests or reported by anyone else.

We have fixed the issue in the following build (and also added a checkbox for creating an extra node for the imported folder itself): VisualGDB-5.6.104.4538.msi

[support]

Hi,

This is handled directly by CMake, rather than VisualGDB. Feel free to browse through CMake source code to see if there is a way to modify this behavior.

[support]

Hi,

Good to know it works.

Regarding the activation, you can always reenter your key via Help->About VisualGDB in order to update its state.

[support]

Thanks for the detailed repro steps. It looks like you are targeting a device from an Atmel START SDK that you have previously imported into VisualGDB. This issue could be a bug of this specific SDK, or a glitch in our importing logic.

Please try deleting the imported SDK (its location is shown at the bottom of the Device Selection page in the wizard) and importing it again. If the problem persists, please upload original SDK archive in a file sharing service and post a link here, so that we could recheck if our importing logic is handling it correctly.

[support]

Thanks for updating your profile. Unfortunately, we are not able to review specific projects for errors, however we can help you get the command dumping to work.

If you could attach a screenshot of the entire Visual Studio window showing the VisualGDB Build window with the missing commands, we can help you understand why they are missing.

[support]

Hi,

Please refer to the following page for more details: https://visualgdb.com/documentation/colors/

[support]

Hi,

No problem, we will try to help you. First of all, it looks like your support period has expired, so we would kindly ask you to renew it here.

Second of all, please try dumping the configuration and build commands to batch files as described here. Then, run them and make sure the problem persists.

Once you confirm it, please try editing them, replacing any incorrectly escaped characters. Once you can confirm that this fixes the build, please share both the original and patched batch files, and we will update VisualGDB to use the correct encoding.

[support]

Unfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:

1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

[support]

Hi,

Sorry, VisualGDB does not support the XC16 devices. They use a completely different toolchain from PIC32 that has never been tested on our side, and we are not aware of any debug stack on XC16 that would be reliably compatible with the GDB workflow.

[Author]

Posts