[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).

[support]

Hi,

We would advise the following steps:

1. Use the filter to show one or more registers you are interested in
2. Mark them as favorite by clicking in the leftmost column for those registers
3. Repeat 1-2 until all registers you are looking for are marked as favourite
4. Switch the “Favourite only” view to see only the registers marked in steps 1-2

If this is not convenient for your use case, feel free to let us know more and we will try to improve the hardware register viewer to make it more intuitive.

[support]

Hi,

This looks like a common problem of the ESP32 toolchain. Please follow the instructions described in this thread in order to fix it.

Please also note that the ESP-IDF is not as stable as other SDKs; components may be added and removed between versions, and the master branch may simply not always work. VisualGDB provides convenient user interface and workarounds for common issues, however the exact contents of each ESP-IDF release is outside our control, so we would generally advise trying several ESP-IDF versions and finding the one that works the best for you.

[support]

Hi,

This looks like a corrupt/incomplete BSP installation. Please try opening the VisualGDB Package Manager (via Tools->VisualGDB) and reinstalling the STM32 BSP.

[support]

 

Hi,

 

Thanks for checking this. As another quick test, could you try using the same CMakeLists.txt and defining BUILD_VERSION via VisualGDB Project Properties -> CMake Build -> CMake Configuration Variables? Does it result in a different outcome?

[support]

Hi,

Just wanted to share an updated build: http://sysprogs.com/files/tmp/VisualGDB-5.4.5.2451.msi

It now properly supports adding/removing components and source files just like the regular ESP-IDF projects (i.e. it will update the correct ESP-IDF-specific statements, so you won’t need to worry about that). It is still missing support for target property editing, however it should be more convenient than the previous build if you are actively experimenting with the new ESP-IDF.

[support]

Hi,

Thanks, we have indeed managed to reproduce this, however it looks like a problem specific to ESP-IDF (regular VisualGDB Linux projects built with CMake work as expected).

Could you quickly recheck whether it reproduces in your setup when running the normal Windows CMake manually or via idf.py? If not, we should be able to analyze the differences on our side and ensure it works as well. If it doesn’t work outside VisualGDB either, it’s likely caused by some constructs inside ESP-IDF itself (e.g. multiple project() definitions) and we would advise either experimenting with internal ESP-IDF definitions, or simply defining PROJECT_VERSION explicitly.

[support]

Hi,

Thanks for sharing this and good to know it works. Looks like there might have been another confusion though.

Have you tried using our latest experimental toolchain (http://sysprogs.com/files/gnutoolchains/esp32/esp32-gcc5.2.0-r13.exe, not listed on the download page yet, linked in the post above), or did you download the R12 toolchain listed on the download page?

[support]

 

Thanks for the log. We have rechecked this and it indeed turns out that trying to send a string consisting purely of whitespace characters causes VS to throw an exception.

Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.5.2450.msi. It will filter out empty lines and will also not stop the test session even if the VS refuses to relay the test message.

[support]

Hi,

Not fully sure what you meant, but the ST SDKs include a few TCP/IP samples based on the lwIP stack, so we would advise simply cloning any of them via the VisualGDB Embedded Project Wizard.

[support]

Hi,

Strange. Our toolchain is a repackaged copy of this archive with the following extra files/directories:

• toolchain.xml
• esp32-bsp
• esp-idf

None of those should be related to any Python issues, so most likely there is some other difference between the toolchain that worked and the current one. Could you please double-check which MSYS2 environment you used originally? If you cannot find it anymore, please try downloading it from scratch from the Espressif site, applying the fix and check if the new ESP-IDF works there. If not, there might be some other step that you performed with the previous checkout.

The “Open Cygwin Terminal here” command was renamed to “Open ESP-IDF Terminal here” in the build that fixed compatibility with the MSYS2 toolchains, so you are likely still using an old build (the officially released Preview 5 doesn’t include MSYS2 toolchain support as we haven’t tested it sufficiently yet). Please try this one: http://sysprogs.com/files/tmp/VisualGDB-5.4.5.2448.msi

[support]

Hi,

The code 2 typically indicates a missing file, so it might be caused by some components of the toolchain missing or corrupt. As a quick check, please try running the same command line manually (simply copy the contents of both “executable” and “arguments” to a command prompt window). If it doesn’t help identify the problem, please try reinstalling the toolchain.

[Author]

Posts