[support]

Good to know it works. BTW, the fix is included in the latest Beta 2, so feel free to update to it.

[support]

Hi,

Please follow the instructions described in this thread to move arbitrary system functions to FLASH.

[support]

Hi,

Can you try VisualGDB 5.2 Beta 2? We have optimized the thread-related logic in v5.2, so if the threads window is hidden, it should not query and thread information at all and will cache things as well.

[support]

Hi,

Thanks, we’ll look into it and post an update once we can ship a stable build.

[support]

Hi,

Looks like you forgot to specify the -DCMAKE_SYSTEM_PROCESSOR=armv71 as shown on step 18 of this tutorial. Explicitly specifying it in CMake command settings should solve the problem.

[support]

Sorry about that, it may be a bug of the Clang IntelliSense. If it reports that ‘string’ is not a class, please try including <string> explicitly and checking if it still complains about it. If yes, please copy the definition of the ‘string’ class from the <string> file to the source file and check if it ignores it again or complains about another missing class.

Alternatively if you could reproduce it on a small separate example (it should include your toolchain’s include directories) and send it to us, we could investigate it on our side.

[support]

Hi,

Thanks for sharing this. Looks like the Atmel libraries were designed for an older version of the toolchain that did not define _impure_ptr properly. Commenting it out should indeed resolve the problem.

[support]

Hi,

Yes, the missing file can easily declare some functions or types related to the ifstream and break IntelliSense for it. Please try clicking at the error to see which file includes the file.

Perhaps your compiler inserts some implicit preprocessor macro that VisualGDB does not catch, i.e.:

#ifdef SOMEMACRO
#include <somefile.h>
#else
#include <gnu/stubs.h>
#endif

So the compiler includes <somefile.h> and succeeds, but IntelliSense tries to include gnu/stubs.h and fails. Searching your target include directories for stubs.h and checking the code around the relevant #include<> statement should help clarify this.

• This reply was modified 7 years, 7 months ago by support.

[support]

Hi,

We do have a tutorial explaining how to create a basic bootloader with VisualGDB: http://visualgdb.com/tutorials/arm/bootloader/

Hopefully this clarifies the necessary steps. If not, feel free to ask further questions here and we will do our best to help you.

[support]

Hi,

From a quick look it looks like the ST USB library only supports one device class at a time. We would recommend double-checking this on ST forums.

[support]

Hi,

From a quick look it looks like the ST USB library only supports one device class at a time. We would recommend double-checking this on ST forums. If this is confirmed, please consider using third-party USB device stacks.

[support]

Hi,

First of all, please try VisualGDB 5.2 Beta 1. We have resolved a lot of IntelliSense-related issues there. If the problem occurs there as well, please check if it reports any missing header files and use the automatic header discovery feature to locate them.

[support]

There should not be any extra setting needed. Perhaps while specifying -std=c++11 you have accidentally removed -ggdb?

[support]

Hi,

Looks like you might be specifying some arguments to fopen() incorrectly. Please refer to fopen() reference for details on various modes.

[support]

Hi,

You can add a custom file transfer to pre-build actions via VisualGDB Project Properties (requires Custom edition or higher) or simply change the local source directory on the Project Settings page to the parent directory that contains both your Makefile directory and the source file directories.

[Author]

Posts