[support]

Hi,

Good to know it works. BTW, although VisualGDB does not directly support the Keil’s event recorder mechanism, it provides a similar mechanism for tracking various events – real-time watch. Feel free to follow this tutorial to try it out.

[support]

Thanks for the suggestion. We can indeed cache the toolchain/IDF version used during the last build and force a full rebuild when it doesn’t match anymore. We will investigate this and get back to you around the middle of the next week.

[support]

Hi,

In order to reduce the size of the projects, VisualGDB does not copy all of the shared files (e.g. Nordic SDK) to each project. Instead, it stores them in a shared location (typically under %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs) and references them from the projects. Each time you open such a project, VisualGDB would check if the referenced BSP is available. If not, it would show a dialog allowing you to download it.

Furthermore, as different versions of BSPs are not always compatible, VisualGDB remembers the exact BSP version referenced by the project and shows a warning you described when another BSP version is installed.

You can eliminate the messages when opening the projects in one of 2 ways:

• If you are OK using the same BSP version for all of the projects, please simply click the “Use version XXX” button. This will update the version number stored in the project file, so next time you open it, the message won’t be shown (unless you switch the BSP version again). This will need to be done for each project referencing this BSP. We can also add a setting for automatically upgrading the BSP version, however it may cause weird problems as the BSPs are not always 100% compatible.
• Alternatively, you can install multiple versions of the same BSP (requires the Custom edition or higher). Simply use the checkbox under Tools->VisualGDB->Manage VisualGDB Packages->Installed->BSPs ->Nordic to enable the multi-version mode. Then VisualGDB will keep multiple versions of the same BSP, letting you have multiple projects using different BSP versions. In this mode, clicking “Download” in the window shown when opening a project will download the exact version of the BSP referenced by the project without replacing the previous version you had installed.

We are not sure what you meant with the Microsoft-style include directories. Normally you can set them under VS project properties (MSBuild projects) or VisualGDB project properties. If this is not what you are looking for, please describe what you are looking for using the first 2 steps of the 3-step format described here: http://visualgdb.com/support/reporting/#3step

[support]

No problem, we have contacted Whole Tomato with the case details and will update you once we get the tools integrated.

[support]

Please ensure that the parameter names after @param are not wrapped with any ‘<>’, e.g.:

@param setting

[support]

Sorry, ESP-IDF is not very backward-compatible. Unfortunately, it isn’t something controlled by us – it’s a design choice by Espressif to introduce new features faster at a cost of backward compatibility. Our best advice for porting the project would be to create a new one with the latest IDF/toolchain and then move your code one file at a time, resolving the build issues.

We can help you find the COM port setting if you could post screenshots of the project properties and debug properties page of VisualGDB Project Properties.

[support]

Please try attaching another instance of Visual Studio to the one causing memory leaks (ensure you have the ‘auto’ selection for debugging engines). Then select Debug->Windows->Show Diagnostic Tools and switch to Memory View. Start your work session and do the regular work tasks for about 5 minutes. Then click the “Take snapshot” button in the Memory view of the Diagnostic tools and work for another 10 minutes. Then click “Take snapshot again” and wait for the updated line to appear.

Finally click on the difference between the memory snapshots (see the attached file) and share a screenshot of the snapshot window that will open up. It will list the exact memory differences between the 2 snapshots, showing what has consumed the memory.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

It looks like the ‘*’ frame around the comment is interfering with the comment parsing logic.

Please ensure that the line containing the ‘@param’ comment does not have any other characters (other then spaces) in front of the @param part and VisualGDB will handle it correctly.

[support]

Good to know it works. BTW, you can also force VisualGDB to clear the BSP-related caches and reload all package definitions by opening and closing the Tools->VisualGDB->Manage VisualGDB Packages window.

[support]

Thanks for reporting this. It turns out, VisualGDB incorrectly substituted VisualGDB-level variables that are not available on the MSBuild level.

Please try using the relative path (from the .vcxproj file’s directory) instead.

You can also try this VisualGDB build that will not substitute unsupported variables when editing settings via VisualGDB Project Properties: VisualGDB-5.4.105.3146.msi

[support]

Strange. Have you tried regenerating those files via the first page of VisualGDB Project Properties after moving the BSP and restarting VS? If this didn’t help, could you please try creating a new project based on the BSP and then share a file that was generated using the incorrect paths? This should help us narrow the issue down and release a hotfix ASAP.

[support]

Thanks for sharing this and good to know it works. We would still advise setting the AGENT_WORKFOLDER variable, as it would suppress various interactive prompts (e.g. about activating the new version after an update, or installing missing toolchains/BSPs).

[support]

Sorry, Visual Assist only works with regular VC++ projects (i.e. Embedded Project Wizard) and not with advanced projects such as the new ESP-IDF project type, as those projects are not based on VC++ and Visual Assist does not know how to attach to them.

You can use the regular Tools->Options->Environment->Fonts and Colors to modify the syntax highlighting colors for both regular C/C++ and VisualGDB-based projects.

If you are missing some fine-grain highlighting rules/settings, please feel free to let us know. The code highlighting for ESP-IDF projects is fully managed by VisualGDB, so we might be able to add a few extra cases there as long as it doesn’t require a major change on our side.

[support]

Most likely, VisualGDB was not activated on the machine/account where you are running the build and hence it tries to display the key prompt.

The easiest way to get it to work would be to ensure you can build the projects manually on the same machine using the same user account.

We would also advise setting the AGENT_WORKFOLDER environment variable (used by TFS) to a non-empty value so that VisualGDB will activate the unattended mode, reducing the amount of prompts and GUI.

If this doesn’t help, please let us know and we will help you get it to work.

[support]

Sorry, the IntelliSense behavior looks correct. You can double-check this by completing the expression manually and checking whether the code compiles without errors. If it does, but VisualGDB still doesn’t suggest it, please let us know.

[Author]

Posts