Forum Replies Created
-
Posts
-
No problem. We have rechecked the TFS integration with the latest VS build and it looks like the Arduino projects were indeed not handling it correctly.
Please try this build: VisualGDB-5.4.107.3206.msi
If the message still appears, please select the “Use solution binding” option. The SCC icons should now work.
In order to eliminate the message completely, please enable View->Other Windows->VisualGDB Diagnostics Console (using the new build), create a new project in a source-controlled directory and let us know:
- Whether the lock icons appear after you created the project
- If yes, whether they reappear after you reopen the solution
- The full log from the Diagnostics Console showing the messages from creating and reopening the solution
No problem, please try this build: VisualGDB-5.4.107.3203.msi
Hi,
Most likely, some other program (e.g. CMake itself) is using that folder and hence it cannot be deleted.
This can normally be ignored, as VisualGDB will delete every file and subfolder that is not being used.
The reason is the Visual Studio design. The regular disassembly window is a part of the debugging GUI and only appears during debug sessions.
To view the disassembly outside a debug session, please use the disassembly view in VisualGDB’s embedded memory explorer. It works independently from Visual Studio’s disassembly interfaces and was added exactly for this use case.
Please try Debug->Windows->Disassembly, or right-clicking anywhere in the source and selecting “go to disassembly”.
Unfortunately, the project file you copied is corrupt (e.g. the CMakeTargetSpecificSettings tag is not closed), so we were not able to reproduce the issue with it.
We have tried creating a similar project from scratch (ESP-IDF, CMake) and built it using the following command line:
VisualGDB.exe /build Project.vgdbproj /config:Release
This did work as expected. Please double-check that you are using the latest VisualGDB version and that the newly created project builds the release configuration as expected.
Then try comparing your project with the newly created one to see what setting could be interfering with the configuration selection from command line.
Hi,
Unfortunately, it’s hard to say what is going on without knowing more details.
Please describe exactly what you are doing after your start Visual Studio, what you expect to see and what you actually observe (see our error reporting tips).
Please also attach a screenshot of the entire VS window showing the loaded project in Solution Explorer and the missing menu commands and we will help you understand what is going on.
No worries. BTW, as long as VisualGDB is fully initialized (either when you create/open a compatible project, or just run the Help->About VisualGDB command), the “import folder” command should appear for all .vcxproj projects, even if they are not based on VisualGDB.
Hi,
Please double-check that other VisualGDB commands are present and that the Import Folder command was not explicitly hidden via Tools->Customize.
If nothing helps, please share a screenshot of the About VisualGDB window from the same VS version, and also a screenshot of the entire screen showing Solution Explorer and the context menu where the “Import folder” command would normally appear, so that we could try to understand what is going on.
If Visual Studio lists VisualGDB under the extensions, but does not update the menus, most likely some VS cache is corrupt. Please try repairing the VS installation or completely reinstalling it if the repair doesn’t work.
The ESP-MDF is very new and it’s hard so say how popular it is going to be, and hence when will we add full out-of-the-box support.
We could add the full MDF integration early as a part of our paid consulting services – do the necessary research and document the exact steps needed to get certain functionality working with ESP-MDF and VisualGDB. If you are interested, please contact our sales with more details and we will get you a quote.
Please try using the following tool from Microsoft to fix the Windows Installer issues: https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed
Sorry, VisualGDB hasn’t been explicitly tested with ESP-MDF. If the MDF framework works together with ESP-IDF, you should be able to import an existing MDF-enabled project into VisualGDB and then use the regular VisualGDB GUI for building and debugging it.
Hi,
Most likely the DMA module is not enabled for your project via the STM32 HAL configuration file. Please try comparing the configuration file to a project that is successfully using DMA and ensure all the necessary definitions are present.
