Annoying Intellisense problems

[urosg]

I just created a new STM32CubeMX project via the build in wizard.

I opted for separate c/h files for each peripheral (using STM32H753ZI) and when I open “usart.c” file I get Intellisense red underlined keywords “GPIO_PIN_14” etc.

With error “[Clang intellisense] Error: use of undeclared identified ‘uint16_t'” – see attached screen snip.

 

Since the project compiles and runs without problems this is rather annoying.

I already tried deleting the .VisualGDB folder from the project after closing the project and then reloading it, does not help.

 

I am currently running the latest 5.6R3 (build 4531), what can I do to fix this?

 

Attachments:

You must be logged in to view attached files.

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

Another common cause of errors is updating to a new toolchain/BSP/SDK. Many of these components are maintained by device vendors or communities, and require minor adjustments to the project when switching to newer versions. If you have recently updated any of such components, please consider reverting back to the old version as described here. There is no need to downgrade VisualGDB itself, as it is updated separately from such components.

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.

[urosg]

Recreating project from scratch seems to have helped (which was ok for this project as it was an old skeleton project), but it is hardly a solution IMHO as this means, that every time an update is available there is potential it will break.

 

Thank you for the reply, I will check other projects and see if the problem persists as it is problematic for Intellisense, no errors/warnings are present in build logs.

[support]

Hi,

Most likely, the problem was triggered by changing some setting in the old project, or hardcoding some parameter in it in a way that only worked with a specific version.

As you now have 2 nearly identical projects that work differently, you can always try comparing them file-by-file (and editing them to eliminate the differences one-by-one), to see what exact setting was causing this.

[Author]

Posts