[support]

Hi,

This means that the project file is corrupt. Please try re-creating the project, or manually checking the location shown in the error message for obvious XML errors.

[support]

This error means that Visual Studio refused to save the solution file when VisualGDB requested it. Most likely, it is caused by some setting you picked when creating the project.

Please try starting again and following the tutorial as close as possible. If it doesn’t work, please share the complete steps to reproduce the problem including all the screenshots, and we will try to point out the cause of this issue.

[support]

Sure, you can use the CMake Platform Manager to have an arbitrary combination of platforms and configurations.

Every platform/configuration can use a different toolchain, exclude some targets, or tweak how they are built.

[support]

Thanks, it looks like ESP-IDF 5.0 relies on a newer toolchain, that is still in RC stage. In order to ship a pre-packed toolchain with ESP-IDF 5.0, we would need to take the components from that toolchain, so we would still need to wait a stable release is available.

[support]

Hi,

VisualGDB requires SSH to transfer the files from/to target. If it is not available, you can try using our telnet target plugin, however it is much more fragile than SSH and may require some non-trivial troubleshooting.

[support]

Hi,

This is something to check with Espressif, the maintainers of the ESP32 OpenOCD port. All VisualGDB does in this case is launch OpenOCD with the parameters you select.

[support]

OK, we have updated VisualGDB to allow searching for the internal variable names in the KConfig editor. Please try this build: VisualGDB-5.6.108.4758.msi

It now also supports the “^”, “$” and “;” syntax from Code Explorer, so that you can filter the values more precisely.

[support]

Hi,

Yes, please try asking Espressif. The ESP32 OpenOCD fork is maintained by them and they might have an idea how to get it working. You can also try asking the JTAG programmer vendor.

[support]

Unfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:

1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.

[support]

Hi,

We have just rechecked our ARM toolchain and it works just fine. Most likely, you have configured something incorrectly on our side.

We will monitor the issue and will consider investigating it further if other users report similar issues.

[support]

Hi,

The FreeRTOS integration is available starting from the Custom edition. If you have purchased a lower edition, it would work while the trial period was still active, and would then turn off.

If this is the case, you can always upgrade your VisualGDB key via this page or see this page for a full list of the Custom Edition features.

[support]

No problem. Feel free to bump this thread once ESP-IDF v5 is officially released (not beta and not RC) and we will provide a timeline on fully integrating it.

[support]

If you you would like us to review your code and suggest the best layout for it, please contact our sales for a consulting quote.

Otherwise, please make sure you reproduce the issue on a smaller “hello, world” setup involving the minimal amount of sources and libraries, and solve it successfully for a regular Win32 C++ project. If you then share the steps you needed to solve it for a Win32 project per our problem reporting guidelines (with full screenshots from scratch), we can point out the equivalent steps with VisualGDB.

[support]

Hi,

VisualGDB projects use the same semantics as the regular Win32 C++ projects. If you are new to C++ and are not familiar with header files and libraries, we would advise first creating the project layout you need using the regular Win32 C++ project type. Once that works the way you intend, feel free to let us know how you created it and we will point out the locations of equivalent VisualGDB settings.

That said, the VisualGDB settings for C++ projects are designed to be as close as possible to the original Win32 C++ project properties, so once you get it working for the regular project type, finding the VisualGDB settings should be straight-forward.

[support]

This is by design. C++ and C# projects have different semantics, so this button is not needed on C++ projects.

[Author]

Posts