[support]

Sorry, this is not covered by our technical support. Please refer to the STM32 documentation for further details.

[support]

Unfortunately, VMWare 15 no longer contains the VIX API used by VisualKernel to restart the virtual machine in order to modify its configuration. As a workaround, please follow the steps below to enable debugging of a VMWare 15 machine:

1. Suspend or stop the VM. Make sure it is no longer running.
2. Add the following lines to the vmx file (replace guest64 with guest32 if you are running a 32-bit kernel):

   debugStub.listen.guest64 = 1
   debugStub.listen.guest64.remote = "TRUE"
   debugStub.hideBreakpoints = "FALSE"

3. Start the VM. Make sure the VM log file contains the following lines:

   2020-01-28T10:25:40.627-08:00| vmx| W115: Debug stub: VMware Workstation is listening for debug connection on port 8864.
   2020-01-28T10:25:40.627-08:00| vmx| W115: Debug stub:     (gdb) target remote <host running VM>:8864
   2020-01-28T10:25:40.627-08:00| vmx| W115: Debug stub:     (lldb) gdb-remote <host running VM>:8864

As long as the “target remote” line is present in the log file, VisualKernel will be able to automatically connect to the virtual machine.

We are working on supporting the new JSON-based VMWare API and will make sure that the upcoming VisualKernel 3.2 will handle this automatically and won’t require any manual configuration editing.

[support]

Looks like you did not follow our instructions about creating a project and removing the libraries via VisualGDB Project Properties -> Embedded Frameworks and instead created a project without a linker script and other compiler/linker-level settings. Please make sure you follow those instructions.

[support]

Thanks, we have added it to the backlog and will consider supporting it in one of the future VisualGDB releases.

[support]

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.

[support]

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.

[support]

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.

[support]

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.

[support]

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.

[support]

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.

[support]

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.

[support]

Hi,

Please refer to the following page for details: https://visualgdb.com/support/oldpackages/

[support]

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/

[support]

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.

[support]

Please carefully read the second part of our previous reply. It describes exactly what to do if the newly created project works.

[Author]

Posts