Forum Replies Created
-
Posts
-
Hi,
Please try creating a new MSBuild-based project, keeping the default value of Code Database Folder Name and setting the “Output Directory” field to the following:
$(SolutionDir)..\test\$(Platform)$(Configuration)
Then reopen the solution. The CodeDB directory should be created under the ..\test directory. If this doesn’t help, please let us know where exactly it is created. If this helps, please compare this setting to the setting in your project and adjust your project accordingly.
Hi,
Looks like the VisualGDB debug engine might not be initialized properly. Could you please share a screenshot of your About VisualGDB window?
Hi,
Thanks, we have rechecked this. The latest update to the STM32Cube SDKs renamed the sample configuration files for FatFS, assuming that you would rename and copy them to the project directory manually, so the checkboxes indeed don’t work anymore (they only work for including files from BSP). We have updated BSP rules to remove them (will take effect in the next BSP update). We have also removed the BSP directory with ffconf.h from the include directory list to avoid confusion between the 2 files.
As a workaround, please locate the matching template files (e.g. FatFS\src\drivers\sd_diskio_template.*), copy them to the project directory and add them to Solution Explorer.
The native VS IntelliSense is known to hardcode several macros and VS-specific features; our best advice is to use the Clang IntelliSense that is specifically designed to work around this type of issues.
Hi,
You can change the location of the CodeDB folder as follows:
Tools->Options->Text Editor->C/C++ (VisualGDB)->Indexing->Code Database Folder Name
The output directory (e.g. VisualGDB\Debug) can be changed via regular Visual Studio project properties (first page) for MSBuild projects and via VisualGDB Project Properties for other project types.
Hi,
We are planning to roll out Android CMake support around the beginning of the next year. As a temporary workaround, we can publish a version addressing the build issues (but not including the 2-way CMake integration yet) in 2-3 weeks. Let us know if you would like to try it out.
Hi,
Looks like your STM32 BSP is incomplete. Please try reinstalling it via Tools->VisualGDB->Manage VisualGDB Packages.
Hi,
This could be the case if the 3rd-party code you are trying to import was not compatible with GCC (the compiler used by VisualGDB that is different from the online mbed compiler). The “conflicting return type” error usually points to several locations where a method is defined/declared (implying that those locations have different return type specification). We would advise double-checking those locations (e.g. one of them might be after including a header file that redefines off_t). You can also use the “generate preprocessor output” option in VS File Properties to get the fully preprocessed output of the corresponding source files (that will expand all #define and #include directives making it easier to understand cryptic error messages).
Hi,
This doesn’t look like a message produced by VisualGDB. Our latest mbed package is based on mbed 5.6.3, so most likely the message comes from some missing configuration variables. We would advise trying to locate the code producing the message and adjusting it accordingly.
Hi,
We are sorry for the inconvenience. Unfortunately Apple is known for not maintaining backward compatibility for 3rd-party tools like gdb, so we cannot promise that gdb won’t be broken by a recent update to any other OS X version. We would advise trying Mac OS 10.12 Sierra (as long as you can debug your program with gdb via command line, VisualGDB should support it as well).
Hi,
Please try setting the VS Project Properties -> ARM Settings -> Floating-point unit type.
You can read more about various FPU options supported by GCC here: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
Hi,
Sorry for the delayed reply. We have tried reproducing this with different toolchains and device settings, but could not get any similar behavior. Please ensure that you are using the latest VisualGDB 5.3R6. Please also feel free to share your template file with us. As it looks like a VisualGDB bug, we will be happy to fix it if we can reproduce the problem on our side.
Hi,
The VM error shown in the log is actually a known Java issue and can be easily solved via environment: https://stackoverflow.com/questions/18040361/java-could-not-reserve-enough-space-for-object-heap-error
Regarding Gradle support, the latest Gradle switched the build system from ndk-build to CMake, breaking backward compatibility. The latest version of VisualGDB has introduced a new Advanced CMake subsystem (currently supported for Linux and Embedded projects only) that replaces the regular Visual C++ logic for CMake-based projects and we are planning to extend it with support for Android projects in the next major VisualGDB release.
Currently we recommend installing an SDK version that supports ndk-build (importing Gradle projects from Android Studio is supported). Once we release a VisualGDB preview supporting CMake on Android, the CMake-based projects will start working out-of-the-box as well.
Hi,
We have just rechecked everything on the latest MacOS High Sierra and could not reproduce the problem with the gcc specs. The project got created fully automatically, although debugging was not possible because MacOS High Sierra does not have a compatible gdb build yet.
We would advise trying an earlier MacOS build and also updating to VisualGDB 5.3R6 (looks like you are using the previous v5.2).
Hi,
Do you mean VisualGDB 5.3r6? If not, please update to the latest version. If yes, we can confirm that we tested it with VS2017 15.4.4 and found no problems. Please try repairing the VS installation and reinstalling VisualGDB.
Hi,
As MacOS is different from Linux in many ways, is much less popular among our users and often introduces breaking changes, we don’t guarantee that VisualGDB will support the latest version out-of-the-box (although it automatically detects and applies a few workarounds).
Our best advice would be to try installing gdb from macports and configuring VisualGDB to use it. If this doesn’t work, please post the details here and we will walk you through setting it up.
