[ket]

Hi,

Which SSH server do you have installed on the embedded linux device?
Which settings are you using to connect with VisualGDB/SmarTTY (public key, password?) ?

[ket]

Hi,

Thanks for notifying us. We have not experienced any compatibility issues with other Visual Studio plugins.

Do you have any kind of stack trace of the crash? Was an exception log created?

[ket]

Hi,

Static libraries are not linked when built. Please add the additional linker inputs to the app or shared library project using this static library.

Currently the ADDITIONAL_LINKER_INPUTS variable is not correctly used in the Makefile, we will fix this issue in the next release of VisualGDB.
As a workaround add the following line just before the “all_make_files := …” line:

LIBRARY_LDFLAGS += $(ADDITIONAL_LINKER_INPUTS)

[ket]

Hi,

Currently, no. The option to add extra parameters to “am start” is planned to be added into the upcoming 4.1 version.

[ket]

Hi,

Have you tried setting the “Disable -file-list-exec-source-files” option?
With large projects polling all the source files at once tends to take a long time, how large is your project?

The call stack can only show functions with symbols, i.e. you cannot step into system libraries as they are not built with symbols.

As for the delay, are you using a Windows vm to run Visual Studio and channeling the USB connection of the Android device into the vm?

Btw, VisualGDB also uses NDK and ant to build Android projects.

[ket]

Hi,

Certainly, please check your email.

[ket]

Hi,

Although we never specifically tested it, VisualGDB should support it as it runs Linux and connects to the network.

Use the Raspberry Pi tutorial for reference as it is very similar:
http://visualgdb.com/tutorials/raspberry/

[ket]

Hi,

Exactly which of the above issues are you experiencing?

Please submit a full GDB log, so enable diagnostic logging in the GDB settings page of VisualGDB Project Properties. Then start debugging, replicate your scenario, stop debugging, give us the gdb log file from your project directory.

[ket]

Hi,

We tried replicating your scenario on an otherwise clean machine and did not experience any issues.

Please follow these steps to give us an exception log:
1.Open regedit.
2.Go to HKCUSoftwareSysprogsVisualGDBSettings.
3.Create a string value called “ExceptionReportDir”. Set it to something like “c:temp”. Ensure that c:temp exists and is writable by the user account that runs Visual Studio.
4.Run Visual Studio, let the exception happen.
5.Look in the directory specified above for .exception files. Send us the relevant files.

The usual fix to Visual Studio crashes is to also install the latest updates. In addition to that make sure that your .NET 2.0 framework is updated.

[ket]

Hi,

Is stdio.h provided by vxworks? If yes, have you copied the system headers over from vxworks as instructed before?

[ket]

Hi,

Please try reloading the symbols (step 6 of this tutorial shows where to open that window). Make sure you are debugging the Debug configuration. Also try using a real device.

If that doesn’t work, then give us your full gdb log. In order to get a full log, please enable diagnostic logging in the GDB settings page of VisualGDB Project Properties. Then start debugging, replicate your scenario, stop debugging, send us the gdb log file from your project directory.

[ket]

Hi,

Do you already have a working project using TI Tiva/Stellaris without a BSP? If not, then that should be the first step.

The downloaded BSPs are stored in %LOCALAPPDATA%VisualGDBEmbeddedBSPs, you can edit and add your own BSPs there.
Have a look at how some of the BSPs there are made, try using AT91SAM7S or STM32 as a reference as TI Tiva/Stellaris should also use the arm-eabi toolchain. Try initially only defining one MCU in the BSP.xml, once that works you can add others based on it. Make the BSP.xml data based on the TI Tiva/Stellaris datasheet and add the peripherals, startup file, linker script in the directory tree. Those files should be available from the TI website software for Tiva/Stellaris, the peripheral library is usually a separate download and the startup/linker file is usually part of an example. Finally add a basic sample to make new project making easy.

Let us know if you need any clarifications.

[ket]

Hi,

Thanks for coming back to post what solved your issue.
The problems you were experiencing were definitely one of the strangest we have seen. Nice to hear that debugging is working now.

[ket]

VisualGDB version 4.0r4 has now been released including a fix for this issue.

[ket]

Hi,

Look into config.log for the exact cause of the error. The compiler is probably complaining about missing headers, you need to copy the system headers from your vxworks powerpc target to either sysrootusrinclude if you are using sysroot or include if not. The location depends on how it is done for vxworks powerpc.

[Author]

Posts