[ket]

Hi,

Those are harmless warnings. IntelliSense is picking up some differences in what is allowed in c code in Linux but not in Windows.

[ket]

Hi,

We have seen some similar issues before, where the linker does not seem to find the library based on the name even if it is on its search path.
As a work-around try specifying the library with its full path and name in the LDFLAGS variable in flags.mak (e.g. LDFLAGS := -Wl,-gc-sections C:/RaspberryPi/opt/vc/lib/libvcos.so).

Btw, the default directory to copy additional libraries and headers to for the cross-toolchain is at C:SysGCCraspberryarm-linux-gnueabihfsysroot. This should not however affect the issue you are having.

Sometimes also issues arise from copying the directories from the Raspberry PI in ways that may break symbolic links. You can open a SSH console to Raspberry PI, from Visual Studio Tools->SSH Host Manager. In our SSH console there is a SCP menu that allows easy downloading of directories in tar files.

[ket]

Hi,

The undefined reference errors indicate that the linker does not know about the PiFace library. Add the library names in the flags.mak LIBRARY_NAMES variable. The library names should be separated by spaces and not include the lib prefix or the .so or .a suffixes (in this case probably just piface or piface-1.0).

As you are using the cross-compiler, the cross-toolchain probably does not include the PiFace library. You need to copy the library and its includes into the sysroot directory of the cross-toolchain from the Rasperry PI if you have not done so already.

The IntelliSense warnings look harmless in this case, it is only picking up some c code differences between Linux and Windows.

[ket]

This issue was caused by gdb reporting non-expanded paths and not recognizing the expanded absolute paths. A work-around was added in VisualGDB version 3.1.r5. VisualGDB will now try to fix breakpoints by using the path that gdb reports.

[ket]

Hi,

Go to VisualGDB Project Properties, in the Build section remove the libs directory from the ‘Additional directories to delete on clean’ setting.

[ket]

Hi,

For Linux/Embedded/cygwin/MinGW projects the include paths should be specified in flags.mak, for Android projects in Android.mk. Also, for remote projects the path specified should be the path on the remote build machine as that is where the Makefile will be used.

Additionally in the VisualGDB Project Properties you can specify IntelliSense includes that are used by Visual Studio IntelliSense.

The VisualGDB Source Cache Manager caches remote sources locally for them to be browsable and accessible to IntelliSense, it is not related to include directories.

[ket]

Hi,

Adding a new header file in Solution Explorer with the usual right-click menu option Add->New Item should be all that you need to do. The include in the source file should be a simple ‘include “MyHeader.h”‘.

Does the project path or file names have spaces in them? Are you using source transfer or shared directories for the source?

[ket]

Hi,

In flags.mak you can use the system environment variables as those are passed to make. In VisualGDB Project Properties you can use the VisualGDB Build variables, you can see the defined variables from the link in the lower left corner of the VisualGDB Project Properties window.

For the next release of VisualGDB a new feature is planned that will allow to define your own variables with user-specific values.

[ket]

The Olimex programmer could come with a special version of MSP430.dll.
Try copying the MSP430.dll from Olimex into our MSP430 toolchain directory (usually at C:SysGCCmsp430bin).

[ket]

You can make new windows and controls for example with Qt Designer, refer to their manual here http://qt-project.org/doc/qt-4.8/designer-manual.html.
Setting up Qt projects with VisualGDB is described in our tutorial at http://visualgdb.com/tutorials/linux/qt/.

[ket]

Hi,

VisualGDB is essentially using GDB, so look up the instructions on how to use GDB with OLIMEX. We have tested using OLIMEX before with VisualGDB, so it should be possible.

[ket]

Hi,

Apart from the breakpoint not being hit, the log is completely normal, bss is now present. Try using mspdebug simulator instead of the GDB simulator as it sometimes has issues.
You do not need to replace the entire main loop of your program, just add this variable and the variable usage.
Our example should work as is but the toolchain can have bugs. Are you using our MSP430 toolchain installed from the wizard or some other toolchain version?

[ket]

Hi,

bss is a section of uninitialized global variables. Hence try making a uninitialized global variable for example as follows:
int unused;
int main()
{
volatile int test = unused;
}

Let us know if this does not work for you and we will look into updating the toolchain.

[ket]

Hi,

Thanks for the feedback. Normally we accommodate NDK changes in our next release following the usual release cycle, but the problems you described were worth making a hotfix. Please download VisualGDB 3.1r3 from our website. Below are the details:

1. Fixed.
2. Fixed. Additionally we added the option to choose which toolchain to use for gdb.
3. The path mappings in VisualGDB Project Properties are used differently, they are used only for mappings between the development and target machines. There is no VisualGDB Project Properties in the right-click menu on the project or in the Project->VisualGDB Project Properties? Is there a vgdbsettings file in the project directory?
4. The changes in the directories came with the latest NDK version and would be normally accommodated in the next release of VisualGDB. The users that purchased a license within a year from the release can upgrade for free, otherwise they need to renew the license.
5. Depends on which errors are you getting. VisualGDB reuses the IntelliSense mechanism of Visual Studio by tweaking it in 2 ways:
a. Forcing it to use the Linux directories instead of its native directories.
b. Forcing it to consume the gcc_compat.h file that contains #define directives for GCC-specific language features (e.g. __attribute__). Most of those definitions are blank, as the features are irrelevant to the browsing IntelliSense does.
Your problem can be caused by either a path conflict or a missing definition in gcc_compat.h. Could you give examples on the errors or make a screenshot of them so that we can help you identify the main cause of them?

[ket]

Currently it is not possible to exclude specific subdirectories. The “Files to transfer” field is used to filter file names without the path only e.g a filter value *.*;-*.txt;-*partial* will transfer all files expect txt files and files with partial in its file name.

Try experimenting with filemasks and having several file transfer commands, some including all subdirectories, some including no subdirectories.

[Author]

Posts