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

[support]

Based on your build log, it looks like VisualGDB is not passing the toolchain definition to CMake. Normally the build command should look like this:

1>  VisualGDB: Run "C:\Program Files (x86)\CMake\bin\cmake.exe -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF .. -DCMAKE_TOOLCHAIN_FILE=toolchain-Debug.cmake -DCMAKE_MAKE_PROGRAM="C:/SysGCC/raspberry/bin/make.exe"" in directory "c:\projects\LinuxProject8/Debug" on local computer

Note the -DCMAKE_TOOLCHAIN_FILE part. Please try creating your VisualGDB project again and double-check that you select the correct cross-toolchain in the project wizard.

[support]

Hi,

This is indeed a bug, thanks for reporting it. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.10.1169.msi

 

[support]

Hi,

Our best guess is that the library is built using a different compiler (e.g. using native g++ instead of a cross-compiler for your ARM board). You can check that by running “readelf -h <file>” for the main application and the .so file. If the “Machine” field is mismatching, please double-check the compiler you are using.

[support]

Hi,

Most likely your firewall has blocked VisualGDB from downloading the project templates automatically.
Please try downloading them manually here: http://visualgdb.com/hwsupport/
You can install them via Tools->VisualGDB Package Manager (v5.2) or Embedded Tools Manager (v5.1).

[support]

Hi,

The ‘U’ in front of the symbol means that the symbol is undefined, hence the RevLibApi.o file expects some other file to define RevLib::RevLibObject::GetInstance().

Please check your source files for the definition (not declaration) of RevLib::RevLibObject::GetInstance() and then check the corresponding .o file.

[support]

Hi,

This is somewhat of a limitation of the way VisualGDB stores the remote directories. As they can be different for different hosts anyway, we would recommend opening the Makefile Settings page of VisualGDB Project Properties, changing something there (e.g. adding and removing space to CFLAGS) and pressing ‘Apply’. This will automatically redetect and re-configure the IntelliSense directories.

You can also try our new MSBuild backend in VisualGDB 5.2 (currently in Beta). It has a more automated way of dealing with remote include directories (you will still need to to click “repair MSBuild settings” after you change the alias target).

[support]

Looks like the Raspicam library is picking up the Windows build of OpenCV.
If you want to use it with OpenCV, please consider following this tutorial for build it for Raspberry Pi. If not, please edit the CMakeLists.txt of the raspicam library to remove references to OpenCV.

The step 22 looks different because you have created your main project with CMake, not GNU Make. Both should work though, so it should not be a problem.

[support]

Hi,

Looks like your library somehow ended up missing those method definitions. According to your build log, your application is linked against the library:

g++ -o LinuxConApp/RevLibConApp -Wl,-gc-sections -Wl,--start-group LinuxConApp/main.o LinuxConApp/ProgressMonitor.o LinuxConApp/RevLibTest.o ../RevLib/wrk/LinuxConApp/RevLib.so -Wl,--rpath='$ORIGIN' -Wl,--rpath='$ORIGIN/../../RevLib/wrk/LinuxConApp/' -Wl,--end-group

You can check the list of functions exported from a library by running the following command on the Linux side:

nm <full path to .so file> | c++filt

If it does not mention anything similar to RevLib::GetRevLibObjectInterface(), please locate the .cpp file that defines it, find a matching .o file on your Linux side and run ‘nm’ on it. If the .o file does not contain the method, please double-check your source code. If the .o file does not exist, please double-check the Library Makefile.

[support]

Hi,

Normally all you need to do is add a reference to the .so project in the properties of your main project (right-click in Solution Explorer, Add Reference).

[support]

Hi,

Yes, you can always download the older BSPs here: http://visualgdb.com/hwsupport/

Normally though a BSP upgrade should not affect stand-alone projects (you can try simply renaming the BSP directory and confirming that the project still builds), so perhaps the upgrade coincided with something else?

[Author]

Posts