[support]

Please use Tools->Embedded Tools Manager->Check for updates.

Please also update VisualGDB to 5.1r6 as the previous versions have a known issue that sometimes corrupts OpenOCD settings with the new OpenOCD.

[support]

Hi,

Normally VisualGDB will automatically deploy everything when you start debugging.

If GDB reports the “Connection timed out.” error, most likely either the gdbserver failed to initialize properly, or your firewall is blocking the connection. Does the gdbserver window in Visual Studio show any errors, or is it reporting a successfully opened socket on port 2000?

[support]

Hi,

Thanks for reporting this, we have fixed the second issue and will fix the first one in v5.2.

If you want to try an internal build with the first one resolved, let us know.

[support]

Hi,

Sorry for the late reply. The error you are observing happens because some parts of the code are built with the “hard float” ABI and others with “soft float”.

You can resolve this by adding the following flags to COMMONFLAGS:

-march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9

[support]

OK, we have just finished updating our IntelliSense engine to a newer version of Clang that should resolve many issues. Could you try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.7.713.msi?

[support]

Hi,

Building a Windows toolchain is not straight-forward. We provide basic build instructions here, however it usually never builds out-of-the-box and requires some patching dependent on the compiler version and platform.

We also offer a toolchain building service: you can send us your Linux toolchain and we could build a Windows equivalent. Simply contact our sales with more details to get a quote on that.

[support]

Hi,

Please specify the “–sysroot=<SDKTARGETSYSROOT>” argument in COMMONFLAGS in VisualGDB Project Properties.

You can find more details in our Edison tutorial showing how to configure a similar Windows toolchain. The only difference is that in the Edison tutorial the toolchain runs on Windows and in your case it runs on a remote Linux machine.

[support]

We did not investigate this yet. VS detection is actually managed by an installer plugin provided by Microsoft (part of the WiX toolset), so by the time of the final release Microsoft will most likely resolve this on their side. Does the HKLM\Software\Wow6432Node\Microsoft\VisualStudio\15.0\InstallDir value point to the installation directory? If not, please try creating it similar to the previous versions. If yes, something more deep is causing the problem, so we would recommend installing the full version until Microsoft fixes the detection.

[support]

OK, we have released an update that supports it. Please update your OpenOCD package to 0.9.0r9.

[support]

The script you mentioned defines CC as “arm-poky-linux-gnueabi-gcc“.

Could you try running “which arm-poky-linux-gnueabi-gcc” in the build environment and then checking if there is a arm-poky-linux-gnueabi-gdb file in the directory of the gcc binary?

[support]

Hi,

This is actually a limitation of the algorithm used by VisualGDB to detect compiler/linker settings from the project settings. It does not work for projects with variables like ${OpenCV_LIBS}.

However it should not affect building or IntelliSense as long as you have the ‘configure IntelliSense based on CFLAGS’ flag set, so you can simply press the ‘ignore’ button when VisualGDB reports this.

[support]

Hi,

Looks like your VS installation might be missing some components that are required to detect its location. Please try installing the full version.

[support]

Hi,

It is possible to build a cross-compiler for Windows, but it’s non-trivial and error-prone. We do provide very basic instructions here, however in many cases things don’t work out-of-the-box and need additional fixing. We could build a Windows cross- toolchain for you as a service (contact our sales to get a quote), or you can just setup VisualGDB to build everything on your Linux machine with the cross-toolchain and deploy it to the ARM board like shown in the tutorial mentioned earlier. The second option does not require building an extra toolchain and once you configure a project, will do everything automatically.

[support]

Hi,

This is not supported yet, however we will consider adding a switch to the upcoming update of our OpenOCD package that we expect to release this week.

[support]

Hi,

We did not use a level translator; the Olimex debugger worked just fine without it.

If you encounter any driver issues, simply run UsbDriverTool and install the WinUSB driver for your Olimex debugger via right-click.

[Author]

Posts