[support]

Hi,

The recent ESP-IDF versions have more specific Python requirements than the older ones, so we created a separate consolidated toolchain mode that fully mirrors the setup used by the Espressif’s VS Code extension, and provides maximum compatibility.

Please consider deleting the existing toolchain/Python and creating a new project by selecting the consolidated toolchain. Once it works, you can try switching the existing project to ESP-IDF 6.0. That said, switching between ESP-IDF versions can require some adjustments to the project, so please make sure you have a good backup before you begin the conversion.

[support]

Hi,

The oldversions page shows all versions available for download, including the last one.

Either way, download page always shows the latest version, and the number is a part of the download URL.

[support]

Hi,

You can find it on this page: https://visualgdb.com/history/

[support]

Hi,

Based on the other feedback we received, it looks like the latest ESP32 OpenOCD might not be compatible with the old ESP-IDF versions.

You can easily revert to the older OpenOCD package as shown here: https://visualgdb.com/support/oldpackages/

[support]

Hi,

The RP2040/2350 support is provided by the Raspberry Pi Pico SDK. As long as you are using the version that supports your device, VisualGDB should work just fine with it.

[support]

Hi,

Sure, feel free to renew, and we will rebuild the Renesas BSP based on the latest packs.

[support]

Thanks for the trace file.  The trace refers to the window that is shown when VisualGDB detects a changed SSH host key (e.g. different VM appearing under the same hostname). However, it should normally be shown in the correct GUI thread.

You can try triggering the window by editing %APPDATA%\VisualGDB\KnownHosts.xml file (change the KeyBase64 for the machine you are using). Does it always immediately result in a new trace in InvalidGUIThreadTraces? If not, is there any particular scenario to make the trace appear?

[support]

Hi,

Normally, everything should work automatically. If not, you can reach out to our support with your license key details, and we will look into it.

[support]

Hi,

It can be a glitch related to first installing an early preview of VS2026, and then upgrading it to the latest stable one. VisualGDB installer finds the latest MSBuild version with a non-empty Platforms subdirectory, and copies its platform files alongside the default platforms. This normally matches the Visual Studio’s default mechanism for finding the platform files.

It is difficult to say why it would look for the files in a different location this time, but copying/symlinking the VisualGDB platform to a different MSBuild version should work just fine.

If anyone else encounters the same problem, feel free to post here, and we will investigate it further.

[support]

Hi,

This means that the MSBuild files are missing from the VS installation. You can confirm it by trying to create a regular Win32 C++ project (non-VisualGDB) – it should be either missing, or would run into the same problem.

Installing Visual C++ project support via the VS installer should fix it. You can also use CMake-based projects instead, as they do not rely on MSBuild.

[support]

Thanks for sharing this.

[support]

It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey

[support]

Thanks for the update. Could it be caused by a different extension then? The problem is very sneaky: any extension creating a Winforms window from a background thread within the VS process will cause VS to hang later when a system notification arrives. On our side, it started happening after we added a very specific workaround to the final v6.1, and this one got fixed in 6.1R2 after multiple users confirmed the issue.

We have not heard of anyone else reporting this after 6.1R2, so it could have a completely different cause. Have you encountered the issue before v6.1 or when not using VisualGDB at all?

[support]

Hi,

Sure, you can use the CMake platform/configuration GUI as shown here: https://visualgdb.com/tutorials/cmake/multiplatform/

[support]

Hi,

Sorry, we do not have any special support for LittleFS, but you should be able to achieve it via custom build steps and custom shortcuts.

[Author]

Posts