Forum Replies Created
-
Posts
-
Hi,
Currently the font name/size is hardcoded. Would it be more usable if we simply used the default text editor font from VS settings or would you like to have two different fonts for that?
Hi,
Thanks for the suggestion. We will evaluate the possibility of adding this feature after we release our new IntelliSense engine.
Hi,
This feature cannot be disabled due to safety considerations. If an unexpected error happens while the file is being updated, the .old file is the only available backup. Your system most likely cannot overwrite them due to inconsistent file/folder permissions. Please ensure that both .mak/.old files and the folder containing them have the “Full Control” access set for the your user account. Please also ensure that the file is not marked as read-only.
Hi,
The libusb library employed by OpenOCD should support the HID driver used by CMSIS-DAP and VisualGDB should not be installing any special drivers for that. Are you experiencing problems when using that setup?
Hi,
If the other people are not going to use VisualGDB, you only need to share the Makefile and all the .mak files. Simply invoke “make” from the project directory to build them.
The .vgdbsettings files contain various GUI and debugging settings and are not required to build the project.
The gcc_debug.h and gcc_release.h contain preprocessor macros extracted from GCC and are only used to configure IntelliSense.Hi,
You can extract the compiler flags from the Eclipse project and then follow our legacy device tutorial to specify the flags manually: http://visualgdb.com/tutorials/arm/legacy/
Hi,
Please consider using the newlib-nano library. It significantly reduces the size of standard functions like printf(). Follow this tutorial for more details: http://visualgdb.com/tutorials/arm/newlib-nano/
If that does not work, you can download the newlib source code and copy the functions responsible for sending debug text using the semihosting API from there.Hi,
Please check permissions on the “C:Program Files (x86)SysprogsVisualGDB\VisualGDB.exe” file. Can you run it manually from Command Prompt?
Hi,
We have updated our OpenOCD package to support the Nucleo-F411RE board correctly. You can update it via Tools->Embedded Tools Manager.
Hi,
The kgdboe module that is used for network debugging only supports kernels starting from 3.8.0. Please update your kernel or use a different connection method.
You should be able to get it working using the Quick Debug feature. Let us know if you run into specific problems.
We will also do more investigation on our side and will consider publishing a tutorial.Hi,
The Raspberry Pi distro does not include Qt5 packages by default. If you download and install them from a third-party source (or build it from scratch), VisualGDB will support it just like it supports it on Ubuntu.
If you are not using the cross-compiler, your sources are uploaded to a directory like /tmp/VisualGDB/c/projects/xxx (selectable via project wizard) and built there. So the executable will be located in the Debug or Release subdirectory of the source directory.The message about libc.so.pdb does not indicate an error on its own. It simply means that the standard C library on the device does not have symbols (which is the default behavior). However normally the debugger should not stop inside the libc library unless there is some kind of error. Please examine the output window and the GDB session window for warnings and errors. You might have missing directories in the PATH or some other environment issues that cause the libc library to abort with an error.
Hi,
You need to update the Raspberry to have the compatible libraries like libc and libgcc. If you want to support the original Raspbian image, you need to use the same GCC version that the image has.
Hi,
Most likely you are using a corrupt image. Please download a fresh image from the Beaglebone website and re-flash it. Regarding IntelliSense, the error messages are caused by Visual Studio’s IntelliSense engine not being able to handle some GCC-specific constructs. We are currently working on a clang-based IntelliSense engine that will resolve this problem. We will be releasing a preview build within the next few weeks. Please feel free to give it a try once it is out.
