[support]

Hi,

Such behavior is usually configured via the sdkconfig parameters. VisualGDB provides a GUI for editing them on the first page of VisualGDB Project Properties, although the exact settings are defined by the ESP-IDF and do not come from VisualGDB.

If you need help locating a specific sdkconfig setting, feel free to ask on the Espressif forums. If you can confirm that the setting works when edited manually but is not working with the VisualGDB GUI, feel free to let us know and we will investigate.

[support]

Hi,

It could be related to paths or missing libraries on the target. You can use the View->Other Windows->VisualGDB Diagnostics Console window to see the exact gdbserver command line used by VisualGDB (e.g. cd <directory> && gdbserver <…>).

Then, try running it remotely via SSH from another machine:

ssh <username>@<deployment machine> <gdbserver command line>

If you get a similar error, please double-check that the executable is compatible with the target and included in the PATH.

[support]

Hi,

VisualGDB tries to use gdbserver if the project is built on one machine and deployed to another one. You can double-check it on the first page of VisualGDB Project Properties.

[support]

Sorry, works just fine on our side, after removing references to the headers you didn’t attach.

Such issues are practically always caused by something very subtle in some very rare place (e.g. a specific overridden #define or edited file) and are impossible to troubleshoot without pulling them apart as we described earlier.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Sorry for the delay. We have investigated this and it turns out NRFConnect 2.4+ requires a newer version of Python (we tested 3.11.5 and it worked). However, older NRFConnect versions, and some other frameworks used by VisualGDB are not compatible with Python 3.11 and require older versions (3.8 works).

We have updated VisualGDB to keep separate track of several Python installations and pick them based on the project type and the SDK version.

Please try installing this build [VisualGDB-6.0.2.4929.msi] and updating the package catalog via Tools->VisualGDB->Manage VisualGDB Packages->Online. It should fetch the correct package definitions and pick the correct Python package compatible with the NRFConnect version you are using.

[support]

Hi,

We are not aware of any known problems that would cause this. A good starting point would be to try reproducing the problem on a clean project created from scratch. If you can reproduce it there, please share the repro steps that we could follow in order to reproduce the problem on our side.

If not, please try comparing the broken project files against the working one – the difference is likely caused by some setting or something particular about the project structure.

 

[support]

Hi,

OK, we have investigated the issue with MSBuild projects. Turns out, it was a combination of the Visual Studio bug we reported in May, and a change in the STM32IDE project structure, that referenced the headers in a different way, that interfered with one of the workarounds used for older projects.

We have fixed it in this build: VisualGDB-6.0.2.4922.msi

With CMake, VisualGDB would normally group the source files by their physical paths, hence the source/header filters would indeed be linked to each other. If you wish, you can disable the splitting into sources/headers entirely, or disable grouping by paths and group by virtual folders instead (similar to MSBuild). See this page for more details.

In general, CMake projects support multiple targets (applications/libraries) within the same project. If you are importing a large external library with a non-trivial folder structure, we would advise putting it into a separate static library (see this tutorial). It will appear under a separate node in Solution Explorer (side-by-side with the application node, but within the CMake project node). If you have multiple such libraries, you can organize them arbitrarily by creating virtual target folders (target grouping is separate from source file grouping, so you can group targets by their function, and keep path-based grouping for files).

The best of organizing the code this way is that the library-specific settings will be stored in the library’s CMakeLists.txt file, separate from the rest of the project. E.g. if the library has some public include directories and expects certain preprocessor macros, you will only need to specify it once, and can then reference that library from any other embedded project, and VisualGDB will automatically combine the project-level settings (e.g. target device) with library-level settings (which sources to build and which include directories to use).

[support]

Hi,

This one is a bit hard to tell. The error message mentions converting QFile to QIODevice, but the code doesn’t look like it’s doing anything similar.

Please try simplifying the repro example until you can narrow down a specific missed part, i.e.:

1. Try closing the project, deleting the .visualgdb directory, and opening it again. This will clear all IntelliSense caches.
2. Remove all code after the error. Ensure the problem persists. Check if there are other errors listed in the Errors window that could make more sense (e.g. some declaration or header file missing).
3. Try moving the error into a separate .cpp file with a minimum set of includes and just 1 function inside the file itself. If the problem no longer reproduces, it was triggered by some include file, or another function above the error in the original source file. Moving it around the source file should help locate the part that causes the issues.
4. If the problem still persists, try breaking down the expression. E.g. does just calling “styleFile.readAll()” trigger the IntelliSense error? If yes, how is readAll() declared? Does calling other methods declared nearby also trigger IntelliSense errors?

[support]

Hi,

This should not normally happen, however it’s hard to determine the exact cause of it from the screenshot. Normally, we would advise using Advanced CMake – it is fully controlled by VisualGDB and should work better in most cases.

If you specifically would like to use MSBuild and it’s not working, feel free to attach the sample project that you are importing, and we can recheck if we can reproduce the issue.

[support]

Hi,

This looks like a legacy CMake project that is not fully compatible with Qt5. Please turn on the “Use the Advanced CMake Project Subsystem” checkbox on the very first screenshot and it should work just fine.

[support]

Hi,

It looks like you specified both command and arguments together:

<Command>cmd /c "echo test"</Command>

Please use this syntax instead:

<Command>cmd</Command>
<Arguments>/c "echo test"</Arguments>

If you are using the VisualGDB Project Properties window, simply put the /c “echo test” part in the Arguments field.

[support]

Hi,

Following the tutorials should normally work as expected, as long as you follow all the steps correctly. Strange errors are usually caused by changing some settings to unexpected values, and unfortunately, it is practically impossible for us to suggest anything meaningful without seeing what exact settings you are changing.

Please try following the tutorial again, taking screenshots of each step. If the problem persists, please attach the screenshots allowing us to reproduce the same steps on our side, and we will try to suggest what could be causing it.

[support]

Hi,

Sorry, there’s not much we can suggest without a precise description of the problem as the diagnostic log doesn’t show anything out of the ordinary.

Our best advice would be to narrow down a specific function that is not working, reproduce the issue on a clean project and describe the desired/observed behavior along with a screenshot demonstrating it.

[support]

Hi,

Most likely, you are using a toolchain that is not compatible with your SD card image. Please try using a clean SD card image that matches your toolchain (see this page).

[support]

Hi,

Advanced CMake projects can group targets and sources in numerous ways configurable via VS project properties for the top-level project node (see this page). The default behavior is grouping by types and paths. However, if you start adding virtual folders on either target level or project level, it stops grouping them by physical paths and uses virtual folders instead.

As long as you don’t have any virtual folders defined and have not disabled grouping by physical path, it should work just fine. If not, please share a screenshot of your Solution Explorer, grouping settings from the VS Project Properties, and let us know the actual physical paths of the underlying objects.

[Author]

Posts