[support]

Hi,

It looks like something between OpenOCD and your board. You can try asking ST, or tying the OpenOCD version/scripts from STM32CubeIDE.

If you can get OpenOCD working outside VisualGDB, we can help you configure VisualGDB to replicate the same result.

[support]

Thanks for renewing your support. Based on the last screenshots you provided, you have left the “target selection command” in VisualGDB Project Properties -> Debug Settings empty, so it confuses VisualGDB’s logic for detecting whether the target is running.

The target selection command should be “target extended-remote blackmagic.local:2345“. Commands like “set mem …” should go to “Additional GDB Commands -> commands before selecting a target” and commands like “mon swp_scan”, “load”, etc should go to “commands after selecting a target”.

[support]

Hi,

This error means that the plugin for decoding the RTOS thread state is corrupt. Please try completely uninstalling VisualGDB, deleting the Program Files (x86)\VisualGDB directory, and installing it back.

If it doesn’t help, you can try disabling the RTOS-specific functionality via VisualGDB Project Properties -> Embedded Debug Tweaking -> Embedded RTOS Support = Disabled.

[support]

Hi,

It is mostly up to the device vendors. Once ST and others begin shipping Rust examples and Rust templates, we will add support very promptly. Until then there will simply be not enough users, sorry.

[support]

Hi,

That would be VisualGDB Project Properties -> Custom Build Steps -> Before transferring files.

That is assuming that by “scanning for out of date files” you meant VisualGDB scanning for files that should be re-uploaded to the target.

If you meant something else, please let us know more details. E,g, if you are talking about the Visual Studio’s logic for determining that a project is up-to-date and skipping the build entirely, you can try disabling the fast up-to-date check via the first page of VS  project properties (not VisualGDB project properties).

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

Hi,

The VisualGDB’s logic for transferring files to the target is completely separate from the contents of the .vcxproj files. So, you can set it up like this:

1. Run the custom Makefile as a custom pre-sync step (not pre-build step). It will run before VisualGDB computes which files need to be uploaded to the build machine.
2. Ensure the file synchronization settings reference all relevant directories. They don’t have to be inside the project directory. You can configure VisualGDB to arbitrarily upload everything in $(ProjectDir)\..\shared to $(BuildDir)/../shared, and it will handle it just fine, even if some files in shared were just updated by the custom pre-sync step.

You can also have a mix of custom Make invocations and custom file upload jobs in the pre-build steps or as manually invokable custom shortcuts, if you want to make the entire setup more modular, and reduce the amount of files checked/updated at once.

[support]

Hi,

VisualGDB is licensed per seat, i.e. computer/user combination. We also offer floating licenses where it counts the number of concurrent sessions from different seats, rather than the number of installations. However, the floating mode requires a continuous Internet connection.

[support]

Sorry, that’s for you to figure out. Probably broken code somewhere.

[support]

Hi,

You can do that, but it could be easier to use the dedicated “Language Standard” setting. The exact name depends on the project type, but it would also be under Project Properties -> C/C++ -> Advanced.

[support]

Thanks for pointing this out. Our RP2350 scripts were ported from the Raspberry Pi’s fork of OpenOCD and did not make it into that build due to a glitch.

That said, look like the OpenOCD developers have fully merged the RP2350 support now, so we have released another OpenOCD update that includes it out-of-the-box without any workaround scripts.

[support]

Hi,

Sorry, it is hard to say why a particular project would not work. You can try creating a new similar project from scratch, make sure that it works as expected, and then compare projects side-by-side.

E.g. you can see the exact object files produced by both projects, symbols inside them (using objdump), or compare the verbose logs to see if any compiler arguments are different.

[support]

Hi,

Sorry, this doesn’t look like anything specific to VisualGDB or any known issue. Most likely, there is a bug somewhere.

[support]

Hi,

You can alternatively try going to VisualGDB Project Properties -> Unit Tests and enabling a checkbox there, but might trigger all kinds of unexpected errors with Make. The GNU Make is very limited compared to CMake, and the Advanced CMake Project Subsystem was designed exactly to bypass the shortcomings of the GNU Make and MSBuild.

We would advise looking through the documentation to get familiar with main concepts. It will take some time to port a non-trivial project, but it will pay off as the project gets more complicated.

[support]

Hi,

Unfortunately, we do not see enough demand for Visual Studio-based kernel development anymore. Many company users moved to developing from Linux directly, and hobbyists typically manage to get things done during the trial period, and cannot justify getting a license. Hence, we will only update VisualKernel once our new cross-platform IDE framework is mature enough to support kernel tracing and debugging directly on Linux.

If your team is interested in using VisualKernel with Visual Studio, feel free to contact us from your work email address with a brief description of your project and the features you are interested in, and we can discuss possible options.

[Author]

Posts