Forum Replies Created
-
Posts
-
Hi,
Sorry, not currently. VSCode is a completely different product from the regular VS and supporting it would essentially mean creating a completely independent plugin re-implementing most of the functionality using a different stack.
Hi,
No problem. Regarding the environment, we usually recommend choosing “fix value” if you are unsure. This works around the case where some PATH variables are applied for regular console sessions, but not for ‘command’ sessions used by VisualGDB to launch the debugger, leading to hard-to-trace “library not found” errors.
Hi,
Most likely your toolchain is not compatible with the target system image.
Please ensure you are using EXACTLY the same SD card image as listed for your toolchain on the toolchains page: http://gnutoolchains.com/raspberry/Hi,
Please try installing the latest v5.3 Preview 8. Then click at the ‘show details’ hyperlink in the exception window and post the details here. This should help us understand what could be causing it.
Another quicker solution would be to simply re-create the project via VisualGDB Project Wizard and compare the settings with the original project. Most likely some of the settings in the .vcxproj file got accidentally replaced by an empty string.
Hi,
This feature was added to VisualGDB 5.3 and is not available in v5.2. Please ensure you install the latest preview build.
Hi,
No worries, good to know you got it to work. If you encounter any further problems, feel free to start another topic.
Hi,
According to our records, your technical support as expired. Please renew it via https://sysprogs.com/splm/mykey and we will be happy to help you.
Hi,
Yes, this is a known limitation of Linux systems, although it’s very well-known and relatively well-documented, so as long as you can find someone with basic Linux knowledge, they should be able to figure it out quickly.
Hi,
The problem could also be caused by Visual Studio having some files in the toolchain folder open (e.g. the debugging plugin).
Please try updating to Preview 8 (your log mentions version 5.3.6 that is Preview 6). It includes a better toolchain updating mechanism that first removes the previous toolchain folder and only then installs the new toolchain.
Hi,
Please try searching the library files (.so) for the ones defining the missing symbols. Then ensure that the linker can find them.
Sometimes the .so files contain a link to another file instead of the actual library (you can see this in text editor). If this is the case for the .so file containing the missing symbols, please ensure that the target linked from the original .so file exists. If it’s using syntax like /usr/lib/… please replace it with =/usr/lib/… so that the linker can automatically substitute sysroot.
Hi,
If your program uses X11, the ‘sudo’ command won’t automatically forward the X11 connections. The easiest way around it would be to create a new ‘root’ connection to your Linux machine (instead of the current user name). You may need to enable root logins explicitly in your sshd configuration (check your Linux distro manual for specific steps to do that).
Hi,
Thanks for checking this. It looks like your antivirus might be preventing VisualGDB from running the downloaded executable. Please try disabling it and updating the toolchain again.
Hi,
We are planning to update our STM32 package in the next 1-2 months, so the new devices will be supported then. Until then please try following the legacy device tutorial: https://visualgdb.com/tutorials/arm/legacy/
You can also try cloning our STM32 BSP generator and running it on the latest STM32 SDK, however this will likely trigger errors due to changes introduced by ST (we will update the generator as a part of our BSP update process).
Hi,
This could be if your C++11 headers are out-of-sync with the libraries. Please ensure you are using exactly the same target image as our toolchain uses (see http://gnutoolchains.com/raspberry/) and try resynchronizing the sysroot if you install any packages on top of the original installation.
