Forum Replies Created
-
Posts
-
OK, this means that the connection between the gdb machine and the target machine cannot be established. Please try the following:
- Manually launch “gdbserver :2000 <deployed binary>” on the target
- Try connecting to 192.168.0.100:2000 via telnet from the gdb machine. If this does not work, try connecting from the Windows machine. If this does not work either, try connecting from the target machine itself.
If the only machine you can connect from is the target machine itself, please check your network & firewall settings. If you can connect from Windows, but not from Linux, check that both machines are on the same network and that no firewall between them is blocking connections.
If VisualGDB asks for a process to attach, it means that your debug settings have “Attach to a process” selected. Please open VisualGDB Project Properties and change gdb launch mode to “Debug a new instance”. This should resolve the problem.
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.
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?
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.
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-a9OK, 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?
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.
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.
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.
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-gdbfile in the directory of the gcc binary?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.
