[support]

Hi,

OK, thanks for clarifying this. The exact steps depend on your project type. Are you using MSBuild, GNU Make, QMake or CMake?

[support]

Hi,

We have just rested everything. The ESP-IDF v3.1 works as expected. Trying out the master branch indeed results in errors.

It looks like a known bug of the latest ESP-IDF and Espressif might be working on resolving it. As one of the comments on the bug thread mentions, you might be able to get it to work by rebuilding the toolchain from scratch (let us know if you need help getting VisualGDB to recognize the rebuilt toolchain), but if you don’t want to spend time diagnosing incompatibility between different components, we would simply advise waiting until Espressif fixes this (we will update our toolchain accordingly once they release a stable package compatible with the master branch).

[support]

Hi,

No worries. Sometimes the names in the SDKs can be indeed confusing and we are happy to point you to the right direction.

[support]

Hi,

This message itself does not indicate any error, it simply means that the target has stopped at a breakpoint. Please let us know what exactly you are doing, what are you observing/expecting and share the ENTIRE output of the OpenOCD window and the GDB Session window (after you switch it to the “All GDB Interaction” mode).

[support]

Hi,

Normally all you need to do is switch the active configuration from Debug to Release in Visual Studio. Unless you have explicitly deleted the release configuration, it should be already present.

The VS configuration selector is typically found on the toolbar near the undo/redo buttons. If you are not sure, please attach a screenshot of your VS window and we will help you find it.

[support]

Hi,

This is by design. The Quick Info will use the declaration that could be found by parsing just the current source file (or more likely simply fetching it from the cache created when you opened/saved it). The Go-to-Definition relies on a project-wide cache that may take longer time to update (as the function might be defined in a different file). If you are interested in previewing the function definition, please use the “Peek Definition” command instead.

[support]

Hi,

Indeed the new toolchain in based on a different environment (MSYS2 vs Cygwin) and hence requires VisualGDB 5.4 Preview 6 or later in order to work correctly.

[support]

Hi,

Sorry for the confusion. We have rechecked the repro steps you mentioned and were able to reproduce them, however we also reproduced them when building the project from command line outside VisualGDB (using idf.py), so the problem is likely caused by some other difference between the 2 projects.

Please try building the modified “hello, world” project using the regular VS CMake interface. Does it still work as expected?

If yes, please try building the project manually from an MSYS2 shell using the CMake version from VisualGDB (under %LOCALAPPDATA%\VisualGDB\CMake) and then using the CMake version used by Visual Studio. If this produces different results, please let us know the CMake version used by the regular VS.

P.S. VisualGDB now officially supports CMake-based ESP-IDF projects. Please consider updating to v5.4 Preview 6.

[support]

Hi,

Most likely you have defined the macro after the Qt header files were included. Either way, we have added the definition to ignore __declspec() to VisualGDB 5.4 Preview 6. Please feel free to update to this version – it will automatically skip __declspec() in your code.

[support]

Hi All,

Just wanted to share an update that we have added support for resource folders to the CMake-based ESP-IDF projects (and other Advanced CMake projects) to VisualGDB 5.4 Preview 6.

You can use the Add->Pin a Resource Folder in Solution Explorer command to attach an arbitrary folder with the specified file masks to Solution Explorer.

[support]

Sorry for the delay. We were running the final tests on the new VisualGDB 5.4 Preview 6 that considerably improves the ESP-IDF experience and have just released it.

Please try downloading VisualGDB 5.4 Preview 6 and then update your ESP32 toolchain to the latest version. Please try using CMake instead of the regular GNU Make when creating the project – it should result in much faster build speed.

Let us know if you encounter any problems with the new toolchain and VisualGDB build and we will be happy to help.

[support]

Hi,

Thanks for the detailed description. VisualGDB actually supports most of the features you described:

1. You can tweak the colors of various C++-related items via Tools->Options->Environment->Fonts and Colors->C/C++ <…>. Visual Studio itself now supports separate colors for various C++ entity types and VisualGDB adds even more (e.g. template non-type parameters vs. type parameters).
2. This is not yet supported, although is planned for the final v5.4.
3. Open File in Solution is somewhat replaced in VS2017 via the “Search Solution Explorer” command (ctrl + ;). If it is not as useful, we would appreciate if you could share the details.
4. This is also supported (Ctrl+K, then Ctrl-O).
5. This is supported via the override hierarchy viewer (right click -> View Override Hierarchy).
6. VisualGDB has 2 features similar to it: the navigation bar that lists all scopes and symbols (with filtering) and right click -> Explore Source File.
7. This is supported via the regular Find References command (Shift-F12). Unlike the regular VC++ IntelliSense that searches by name and than slowly validates each reference, the Clang IntelliSense maintains a highly optimized reference cache that can find the exact locations of all references of a certain symbol almost instantly (building the initial cache might take time for large projects, but once built, the search is very fast).

[support]

Hi,

Please try adding the following lines to your main header:

#ifdef SYSPROGS_CODESENSE
#define __declspec(x)
#endif

This should force the Clang IntelliSense to ignore the __declspec modifier altogether.

[support]

Hi,

Thanks for your feedback. The syntax highlighting with Clang IntelliSense is fully under VisualGDB’s control, so we should be able to add options that would allow tweaking it (unless you are looking for something very specific that will only work for a handful of projects). Freel free to let us know the exact functionality you are looking for and we could see if this is something that can be added easily.

Also with the navigation, we are working on a mechanism that will allow quickly searching in the global symbol cache of Clang IntelliSense, letting you quickly find definitions of symbols anywhere in the project. Let us know if this is something you would find helpful and we could share a link to a preview build with this feature once it is available.

[support]

Hi,

If you are using the regular STM32F7 (not mbed-based) examples, CMSIS-OS is simply a wrapper around FreeRTOS (you can check this by selecting “Go to Definition” for any of the CMSIS-related functions).

This abstraction level comes from the original STM32 SDK libraries and is intended to facilitate porting your code between different RTOSes (e.g. FreeRTOS vs Keil RTX).

[Author]

Posts