Forum Replies Created
-
Posts
-
Hi,
Please check that you actually have write access to the location where you are trying to install it and that your antivirus is not blocking the toolchain installer. If nothing helps, please try downloading it manually from http://gnutoolchains.com/esp8266/ and run the installer in the interactive mode.
Hi,
This is normally something handled by the Segger GDB stub (VisualGDB launches it with the parameters you specify via settings and expects it to take care of the low-level JTAG interaction and provide high-level debugging information to gdb), so please check with Segger support if this is possible with their tools.
If not, you could try using OpenOCD instead. If secure JTAG is not supported by it yet, you could patch it (consider using our easy-to-build OpenOCD fork), wait for someone else to contribute the patch, or we could add it for you via our paid customization services.
Hi,
Until relatively recently, STM8 devices did not have a usable GDB debugger, so VisualGDB could not be used with them. Currently, it looks like there is an unofficial port of gdb and binutils (although you still need to rely on SDCC instead ofGCC), so you might be theoretically able to get it to work by following this tutorial. That said, we have not investigated this at all and cannot promise that it will work. We will try to do a quick research into STM8 around Q3 2019 and see if the available tools are sufficient to provide reasonable building/debugging experience.
Alternatively if you can confirm that the underlying tools are fully usable (and share details), we should be able to update VisualGDB to support STM8 out-of-the-box earlier.
Sorry, it is not possible to directly call a function that would need to run on a different device. Unfortunately, as this is not a VisualGDB-specific inquiry, but rather a generic programming question, we are not able to allocate resources to walk you through this as we have to focus on making our products better and helping users that are affected by VisualGDB bugs. For general programming questions, please consider creating a question thread on StackOverflow.
Hi,
Unfortunately it’s hard to say what exactly is wrong without knowing the details. Is the imported project using MSBuild, VisualGDB-generated Makefile, or a 3rd-party Makefile? Please also try isolating just one file compilation task (i.e. modify one file and count exactly how much time does it take during VisualGDB-controlled build vs. when running gcc manually). If you are using a custom Makefile, please modify it to start a cmd.exe instance in a new window (using the ‘start’ command) and then try running gcc or make from that window. If it also builds slowly, it could be caused by some environment variables inherited from Visual Studio.
It could also be helpful to temporarily disable your antivirus or trying to use a different disk, as buggy antivirus software or disk errors could cause seemingly random slowdowns.
Hi,
Sorry, the page inside SSH Connection Manager is called “host-wide settings” and you will need to create an entry for your host in order to configure the timestamp difference.
Hi,
In Visual Studio the include search paths need to be specified explicitly. Just adding headers to Solution Explorer will not automatically let your code discover it. Simply add the directories with headers to VisualGDB Project Properties -> MSBuild -> Include Directories and MSBuild will be able to find them.
You can also use the VisualGDB’s header discovery logic – it should normally locate the missing headers automatically and suggest updating the project properties for you. You can read more about this feature here: https://visualgdb.com/tutorials/intellisense/headers/
Hi,
Most likely your targets have a different time zone from the development machine. Please consider adjusting them, or simply add the timestamp offset via Tools->VisualGDB->Manage SSH Connections->Per-host Settings. You can also disable the tar timestamps completely in the same window if you want to restore the v5.3 behavior (setting timestamps to the time of transfer, not the original time of the files on Windows).
Hi,
Please try checking the registry under HKEY_CURRENT_USER\Software\Sysprogs\GNUToolchains. VisualGDB loads toolchains from the paths listed there. Simply create another key following the SysGCC-<target> pattern and restart Visual Studio (or reopen the VisualGDB Package Manager) to register another toolchain with VisualGDB.
No problem. Unfortunately most of the modern antivirus software is not very practical – it tries to either search every exe file against a large database of regular expressions (triggering random false positives for high-entropy compressed images like the toolchain installers) or to flag every file that would issue HTTP requests (like our session server) as suspicious.
We have briefly rechecked with VirusTotal and Avira doesn’t report it as suspicious, so it’s hard to say why it’s triggering on your side. Please consider submitting a false positive request to them with the exact details of your antivirus version & type (we can only do that if we see false positives from major AV vendors on Virus Total). Also if you are not planning to use the floating license, you can simply delete the file.
Update: we have created a page listing the components that most often trigger false positives with antivirus software: https://visualgdb.com/documentation/falsepositives/
Whoa, that’s a big one. VisualGDB doesn’t really include any special framework for interfacing your embedded code with higher-level languages, so you would likely need to design one or reuse something like protobuf. Generally, as this is a rather generic programming question, than a VisualGDB-specific issue, we would advise creating a question on StackOverflow – there’s a large developer community there and you may get some good ideas from other developers.
Hi,
Yes, it’s a part of the VisualGDB installation responsible for the floating license mechanism. If you are using a floating license, it will run in the background, fetching up-to-date session keys from our licensing server to all running VisualGDB instances.
Hi,
Most likely you have corrupted some XML files during the find-and-replace. Please try restoring your project from a backup and also reinstalling VisualGDB to fix any corrupt global files.
Hi,
No problem, we can help you. The second problem turned out to be our bug introduced by a recent refactoring. It was on our radar, but we were not aware it affects regular (non-ESP32) CMake projects as well. We have fixed it in the following build: http://sysprogs.com/files/tmp/VisualGDB-5.4.100.2765.msi
The first problem might be caused by the CMake (not reporting the correct include directory for the specific file), or by VisualGDB (e.g. mapping the path incorrectly). In order to narrow it down, please follow the steps below:
- Identify the exact location of the missing header.
- Open Clang IntelliSense Diagnostics Console and switch it to the Project view. Locate the source file that triggers the problem and check its CFLAGS. If the CFLAGS are empty, check the project’s CFLAGS. Do the CFLAGS reference the correct directory? If not, do they mention a similar directory (that would result from invalid path mapping)?
- If the directory is not correct, or is missing, please check the CodeModel.json file in the VisualGDBCache directory. This is the code model reported by CMake. Does it report the correct include directory for the correct source file? If you are not sure, please attach the code model file and let us know the path of the source file triggering the problem and and the header file that is missing.
Please provide an actual up-to-date description of the problem in a separate thread. Unfortunately we are not realistically able to pinpoint or fix the problem based on a generic description that Clang IntelliSense doesn’t work for some of the projects. We do have extensive tests covering various aspects of the IntelliSense functionality, so if you are experiencing inconsistencies, they are likely caused by the factors not covered by our tests. We will be happy to investigate and fix this, but we would need to be able to reproduce the problem on our side, or get a detailed description of it that will help us reconstruct the circumstances behind the problem.
