[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.

Another common cause of errors is updating to a new toolchain/BSP/SDK. Many of these components are maintained by device vendors or communities, and require minor adjustments to the project when switching to newer versions. If you have recently updated any of such components, please consider reverting back to the old version as described here. There is no need to downgrade VisualGDB itself, as it is updated separately from such components.

You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.

[support]

Both Segger RTT and the fast semihosting framework rely on the same underlying principles (ring buffer in the target memory accessed without stopping the CPU), so there should not be any noticeable performance difference between them, as long as you are using the optimized release build. The bottleneck in both cases would be the JTAG/SWD bandwidth when doing background memory reads.

Regarding Quick Debug, according to our records, you are using the VisualGDB Embedded Edition that does not support Quick Debug. In order to use Quick Debug, please upgrade your key to the Custom edition or higher here: https://sysprogs.com/splm/mykey.

If it still doesn’t work, 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 quick debug preset 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.

You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.

[support]

Hi,

This is by design. The Quick Debug feature is supported starting from the Custom edition of VisualGDB (see the feature matrix), and will indeed not work with the Linux and Embedded editions.

[support]

As the VisualGDB semihosting/profiling framework provides similar functionality to RTT, and is not limited to specific debug probes, we do not have any plans of replacing it with RTT. On the contrary, we have plans of extending it to support more fine-grain tracing functionality.

[support]

Hi,

VisualGDB stores this information in the .vgdbcmake files. This is more powerful than the regular CMake presets, as VisualGDB supports orthogonal configurations/platforms, each of them able to override project-level, build-level or debug-level settings. E.g. you can define multiple platforms for Embedded vs. Linux vs. Win32, and multiple configurations for build types.

You can find more about platforms in CMake-based projects in the Linux platform tutorial and the simulation platform tutorial.

[support]

Hi,

The Arduino package issues were caused by a slight change to the JSON schema on the Arduino side. VisualGDB 5.6R4 already handles it correctly.

Regarding the other issues, please let us know the email address associated with your license key so that we could link it to your support profile, and we will investigate them further.

[support]

Hi,

No problem, we have we reproduced and fixed the issue. Please try this build: VisualGDB-5.6.104.4533.msi

[support]

Thanks for renewing your license. The error was triggered by the settings updating logic in VisualGDB: it expected a non-empty project directory in order to save the converted register definition file there.

We have updated VisualGDB to save the converted register definition files to the directory of the original files when using Quick Debug presets. Please feel free to try this build: VisualGDB-5.6.104.4533.msi

[support]

This looks like an issue between OpenOCD and a particular ST-Link. You can try extracting the OpenOCD command line used by VisualGDB from the first line in the settings test window, running it manually, and cross-referencing the serial number command against the serial number shown in the Device Manager.

If OpenOCD fails to recognize the device despite the correct serial number, you can try using other OpenOCD builds (e.g. the ST fork).

[support]

Hi,

No problem, please renew your license via this page, and we will gladly investigate and fix it.

[support]

Hi,

It looks like an issue triggered by the project layout, and not specific to a particular SVD file.

We can gladly investigate it further if you could provide the steps we could follow on our side to reproduce the problem from scratch (including any steps necessary to create the project).

We would also kindly ask you to renew your support period here, as it has expired a while ago.

[support]

Hi,

Installing the same (latest) version of VisualGDB on all machines should normally help. You can double-check the installed version via Help->About VisualGDB.

[support]

Hi,

The build error looks like something on your computer is interfering with low-level operations. It could be malware, buggy antivirus software, RAM malfunction, but it doesn’t look like something VisualGDB would directly control.

Regarding unit tests, please try following this tutorial. It shows all the necessary steps to run unit tests within Windows applications.

[support]

Hi

Currently, 64-bit Raspberry Pi images appear more experimental than mainstream (e.g. not shown directly near the 32-bit images on the website), so we do not have any plans of releasing compatible cross-toolchains until we see this change. That said, if you are OK covering the toolchain building costs directly, feel free to contact our support with more details, and we can gladly give you a quote (we might be able to reduce/waive the fee if your company holds multiple VisualGDB licenses).

[support]

Hi,

Most likely, the problem was triggered by changing some setting in the old project, or hardcoding some parameter in it in a way that only worked with a specific version.

As you now have 2 nearly identical projects that work differently, you can always try comparing them file-by-file (and editing them to eliminate the differences one-by-one), to see what exact setting was causing this.

[Author]

Posts