Forum Replies Created
-
Posts
-
Thanks, we have added it to the backlog and will consider supporting it in one of the future VisualGDB releases.
Hi,
It looks like you have accidentally resized one of the tool windows below the minimum size. Please try updating to the latest VisualGDB 5.5 Preview 4. It contains a fix for this issue.
Hi,
You can add new files to your project same way as for regular VS projects: right-click on the project node in Solution Explorer and select Add->Existing Item.
Hi,
It looks like the project is missing some components (e.g. interrupt vector table or a reset handler). Please make sure you include them in the project.
The easiest way to do it would be to start with a non-empty project and remove all extra components from VisualGDB Project Properties -> Embedded Frameworks, and also remove everything from the main file.
Hi,
Indeed, unlike MSBuild, where VisualGDB controls most of the build process, ESP-IDF projects are thin wrappers on top of the ESP-IDF build system. They synchronize the Solution Explorer view with the ESP-IDF project structure, however they inherit all limitations of the underlying ESP-IDF build logic, since they delegate the actual build process to it.
Unfortunately, the $(SolutionDir) variable is not available for this type of projects, as it is designed to be built outside Visual Studio as well (with no solution in place). That said, you can simply use relative paths and other variables. Also absolute paths or parent directory paths may not work as expected due to the limitations of ESP-IDF itself. If you would like to troubleshoot it, try right-clicking on the build command line in the VisualGDB Output window (shown in cyan) and dumping it to a batch file. Then you can quickly try out several modifications of the command line, see which one is accepted by ESP-IDF, and update the VisualGDB settings accordingly.
You can move the VisualGDBCache directory by adding the following element to the .vgdbproj/.vgdbcmake file directly under the VisualGDBSettings2 element:
<BuildContextDirectory>[relative path to the VisualGDBCache directory]</BuildContextDirectory>
You can change the name of the SDKConfig file via VisualGDB Project Properties -> ESP-IDF Project -> SDKConfig File (ensure you use VisualGDB 5.5 Preview 4). That said, we have not tested it outside of the default directory, so ESP-IDF might not accept it (you can troubleshot CMake issues via our CMake Debugger).
Most of VisualGDB’s documentation is structured as various step-by-step tutorials showing various common scenarios. We also publish answers to common issues under the visualgdb.com/support/ and visualgdb.com/KB/ URLs and link them from the forum and support replies, so simply googling it should quickly reveal relevant documentation. We do not have a a comprehensive list of all possible VisualGDB windows, as they are frequently updated to reflect changes in external frameworks or feature requests from our users, and the tutorials give a good overview of the most commonly used settings. There is a page listing all global VisualGDB settings here though.
Hi,
Please try updating to VisualGDB 5.5 Preview 4. If the problem persists, please share a screenshot of the Debug Settings page of VisualGDB Project Properties, as well as the actual path where the binary gets deployed, and we will help you recheck everything.
The only way to diagnose it is to create a new similar project from scratch and compare the .vcxproj and .filters files. You would need to make a list of changes, manually merge them between the files and recheck whether each of the changes fixes the issue. This could be time-consuming, there is no other way to pinpoint it and we are not able to do this for you, since this is not a project created by us. Depending on your constraints, simply re-creating the project could be faster.
Hi,
If the VS project properties don’t work either, the project file is unfortunately corrupt and VisualGDB won’t be able to use it either.
Most likely, you have accidentally edited the file manually, breaking some parts required by VS or VisualGDB. As this is generally something outside of our control, unfortunately we cannot review the project file within our regular product support. Our best advice would be to try recreating the project. If this is a Makefile project, you can also create a dummy project of similar type and just copy the new .vcxproj and .filters files over the ones and re-add source files to the project. Most of the build settings are stored in the Makefiles anyway, so they won’t be reset.
Also if you can confirm that the file corruption happens consistently as a result of using VisualGDB GUI, we will be happy to fix it, although we would need to know the exact steps to reproduce the problem on our side.
Hi,
Please refer to the following page for details: https://visualgdb.com/support/oldpackages/
No problem, we actually do have a tutorial explaining the roles of various files and a recommended .gitignore setup. Please feel free to look through it: https://visualgdb.com/tutorials/arm/multiuser/
Hi,
You can remove the link to the original project by removing the ImportedProject element from the embedded profile file (typically called mcu.xml, stm32.xml, etc. in the project directory).
This will permanently disable this warning.
Please carefully read the second part of our previous reply. It describes exactly what to do if the newly created project works.
No problem, we will walk you through pinpointing it.
First of all, please try creating a similar project (GNU Make, same toolchain/target) and check if the project properties window works for it. If not, please make sure you can create regular VC++ projects (i.e. have the VC++ components installed).
If the newly created project works, please try opening the VS Project Properties (not VisualGDB Project Properties) for the project and check the NMake Settings page. Does the page appear properly and list the .vgdbsettings file as the primary output? If you cannot find anything suspicious, please attach a screenshot of the NMake Settings page and also the entire VS window having the problematic configuration selected, so that we could check for common issues.
Thanks for renewing your license. It looks like the project has not been fully loaded.
Please try updating to VisualGDB 5.5 Preview 4 and let us know if the problem persists. If it does, please attach an updated stack trace and we will help you troubleshoot it.
Hi,
It looks like your technical support has expired. We would be happy to help you resolve this, however we would kindly ask you to renew your technical support here first: https://sysprogs.com/splm/mykey
