[support]

Hi,

Please try using VisualGDB Project Properties -> Embedded Debug Tweaking to enable saving of various output types to files.

If you would like to access the files on the Windows machine from the embedded targets, please consider using the Test Resource Manager API.

[support]

Hi,

Sorry, this is not supported. In order to keep compatibility with older Visual Studio versions, VisualGDB is using a legacy interface for managing the code outline. Although it supports all of the other functionality, it indeed does not show the structure guide lines. We will consider updating to the newer interfaces in one of the next VisualGDB releases.

[support]

Hi,

This might be related to a bug where VisualGDB would not pass the target selection flags to the IntelliSense engine. Please try this build: VisualGDB-5.6.1.4051.msi

If it doesn’t solve the problem, please try checking the CppEngineTuningInfo.xml file. It contains a list of rules for determining the target based on the preprocessor flags discovered from the project. Please let us know if your target is listed there and the flags shown in View->Clang IntelliSense Status->Project Structure match any of the targets defined in CppEngineTuningInfo.xml.

[support]

Hi,

The “Valgrind failed to initialize” error is shown when the diagnostics process (with the ‘cat’ command) would exit prematurely. Please try running the commands manually to reproduce the problem:

rm -rf /tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa
mkdir /tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa
mkdifo /tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/valgrind.log
valgrind --log-file="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/valgrind.log" --vgdb-prefix="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa" --tool=callgrind --callgrind-out-file="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/callgrind.out" --vgdb=yes --vgdb-error=0 /tmp/CentralControllingApplication
cat "/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa/valgrind.log"
vgdb --vgdb-prefix="/tmp/26c17f45-e5f7-41fa-890b-15cdd7464eaa" --port=2000

Then, check for any suspicious messages or strange behavior. Note that the last 3 commands will need to run in parallel from 3 different terminal windows.

If none of the commands exits, please try checking if running gdb (gdb <executable>) and connecting it to Valgrind (target remote :2000 followed by continue) works.

Please let us know your findings and we will help you configure VisualGDB to work with your setup as well.

[support]

The ‘\n’ behavior could vary between different C library versions and environments. Please see step 6 of the tutorial for an explanation.

[support]

Thanks for clarifying this. Most likely, you have skipped some other step of the tutorial then.

We can gladly help you recheck everything if you could share the exact steps you follow, from the very beginning to reproducing the problem, including all relevant screenshots. Please see our problem reporting guidelines for a very detailed example.

[support]

Hi,

Raspberry Pi is still supported, although the Git repository of the WiringPi library has indeed changed. We have updated our tutorial to reflect the new address.

The WiringPi tutorial indeed shows the older VisualGDB GUI, however the names and locations of the relevant settings have not changed. We do recommend using MSBuild instead of GNU Make though. Please double-check that you specify both include paths and library names per step 7 of the tutorial.

If nothing helps, please feel free to let us know more about the errors you get, including any relevant screenshots, and we will try to suggest a workaround.

[support]

@arrow201, thanks for pointing this out!

[support]

Hi,

No problem, please refer for the following page for a detailed explanation of the STM32 project structure: https://visualgdb.com/documentation/embedded/stm32/

[support]

Sorry, not sure what you meant. Our tutorial does show how to create a project from scratch. If something doesn’t work as it is shown in the tutorial, please double-check that you follow all the steps as described. If it still doesn’t help, please feel free to share the complete steps to reproduce the issue, including all the relevant screenshots per our problem reporting guidelines and we will look further into this.

[support]

Hi,

For all sales- and license-related inquiries, please contact our sales via our contact form.

[support]

Sorry, this looks like an issue in OpenOCD executable and not something specific to VisualGDB. Our best advice would be to try programming this device using the Eclipse-based STM32CubeIDE that also uses OpenOCD. If the STM32CubeIDE works, please try using the OpenOCD script from it with VisualGDB – you should get the same results since the underlying mechanism will be the same.

If OpenOCD doesn’t work there either, please consider using Segger J-Link. It comes with a very well-tested and fully supported replacement for OpenOCD and typically just works out-of-the-box.

[support]

Hi,

The settings on the VisualGDB side appear correct. So this is likely a bug in J-Link, or some kind incompatibility between the Segger software, firmware and hardware. If the problem can be reproduced outside VisualGDB as well, we would advise checking it with Segger support.

Another option would be to just use OpenOCD. It supports J-Link as long as you replace the regular Segger USB driver with the WinUSB one, and we have successfully used it to debug Raspberry Pi Pico. If you use the “USB Devices” view in VisualGDB instead of “Debug Methods”, it will automatically suggest installing the matching USB driver.

[support]

Normally it should work out-of-the-box. If not, please create and attach a gdb log file demonstrating the issue and we will look further into it.

Also in order for us to link your account to your company’s support profile, please either update your forum email address accordingly, or let us know your company email/key via the support form.

[support]

Hi,

It looks like your support has expired. Please kindly renew it on this page and we will try to help you find a workaround.

[Author]

Posts