[support]

Hi,

This looks like a bug in VS itself. The trace shows that Visual GDB is sending a debug event (e.g. breakpoint updated) to Visual Studio, but Visual Studio never returns from it.

Please try disabling other extensions, and if it doesn’t help, completely uninstalling and reinstalling Visual Studio.

[support]

Hi,

This one is somewhat tricky. Live Watch has the go-to-definition command because the symbol files (where the variable list comes from) record the definitions of variables. So, the command works independently from the IntelliSense engine (and even for projects built outside VisualGDB). Finding all references requires properly parsing all source files, and this is done by a completely different part of VisualGDB.

That said, it’s still fairly straight-forward to achieve: you can go to the variable definition via Live Watch, right-click on it in code and select Find All References.

[support]

Hi,

There are a couple of debugging techniques to try here. You can try building a debug build of OpenOCD and setting breakpoints in FLASHPlugin.c to see what requests it gets from gdb, and what it passes to the plugin. You can then try modifying the plugin code to pass these values explicitly and hope to reproduce the problem in a debuggable context.

Another technique would be to reproduce the problem, terminate OpenOCD via Task Manager when it stops responding (it will leave the plugin loaded and running on the device), and do Debug->Attach to Running Program from another Visual Studio instance where you have the plugin project. This will let you see the state of the plugin and determine what it’s doing. You can also modify the plugin to keep some kind of a circular log in the RAM, that can be examined when you attach the debugger.

[support]

No worries, but yes, the live mode in the Hardware Registers window is exactly what you need.

[support]

Thanks for renewing. The error looks like the project was not properly loaded, or the license was not properly applied.

We have updated VisualGDB to show a more informative error message in this case. Please try this build: VisualGDB-6.0.107.5300.msi

[support]

No problem, we have rechecked both remaining issues. The logic for moving the solution file was indeed not used when importing CMake projects, and the logic handling rebuilds contained a glitch that didn’t work with some combinations of settings. We have fixed it in this build: VisualGDB-6.0.107.5300.msi

[support]

Sorry, we don’t have any further advice beyond what we already mentioned.

[support]

Hi,

No problem, this is indeed a separate issue. That said, it shouldn’t be VisualGDB-specific. VisualGDB uses the same low-level debugging tool as the STM32CubeIDE, and both ultimately show the values they receive from the chip via the debug interface. There might be some device register or OpenOCD command overriding this behavior, and turning it on will fix the problem regardless of the IDE you are using, but VisualGDB cannot do it automatically.

[support]

Sorry, this doesn’t look like any known issue. Please try following the tutorials from scratch, make sure it works there, and then try comparing the broken project against the working one. If you can point out a specific setting that consistently triggers the problem, we might be able to suggest a workaround.

[support]

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]

Looks like something is broken with the symbols. Please make sure you understand which symbols are loaded, which paths are referenced by them, and what paths are expected by gdb.

[support]

Hi,

Due to historical reasons, the maximum memory size shown in the build output and in the Memory Explorer is fixed for each device type. It doesn’t affect anything other than the displayed utilization, so for the devices with variable size we usually just take the default value from the default vendor-supplied linker script.

You can always patch it on your side by editing the MemoryMap tag in BSP.XML under %LOCALAPPDATA%\VisualGDB.

Another option would be to configure VisualGDB to infer the memory map from the linker script (requires Custom edition) via VisualGDB Project Properties -> Memories.

[support]

Hi,

Please refer to the following thread: https://sysprogs.com/w/forums/topic/debugger-setup-for-black-magic-probe/

[support]

Hi,

Sure, this is already supported. You can use the Debug->Windows->Hardware Registers window, locate the appropriate pin status register (see the device datasheet for the exact name) and turn on the live mode for it (lightning bolt icon). You can also flag several similar registers as favorite, so you can quickly view their realtime values without having to locate each one individually.

[support]

Hi,

Looks like VisualGDB fails to generate BSP.cmake due to some error with the gpdsc file:

VisualGDB found an error: Файл ‘C:\Users\user\mySpace\workspace\_superior\stm32Project\firmware\TestFirmware\TestFirmware.gpdsc’ РЅРµ найден.

Please double-check the error message on your computer. If it’s still unreadable, please consider changing the message language to English via environment.

[Author]

Posts