[support]

Hi,

You should be able to modify the original mspgcc linker script. Normally mspgcc uses the msp430.x script located in <SysGCC>\msp430\msp430\lib\ldscripts that in turn includes msp430f5528\memory.x and msp430f5528\periph.x for device-specific data. You can make your own script based on msp430.x and specify it via the -T linker flag (i.e. add -Tc:/path/to/my-script.x to LDFLAGS).

You can also try reusing the script from Code Composer, however you may need to adjust it to compensate for the differences in interrupt handling (.vectors section vs .intXX sections) and to include peripheral address definitions from periph.x.

[support]

Hi,

As m68k devices are not as popular as the ARM ones, we don’t provide fully-automatic wizard templates. Instead you can follow the legacy device tutorial to specify the flags manually.

In order to get debugging to work please add the “-interpreter mi” argument to GDB command line (or use the ‘custom GDB stub’ mode if you want VisualGDB to set the command line arguments automatically).

• This reply was modified 10 years, 3 months ago by support.

[support]

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?

[support]

Hi,

Thanks for the suggestion. We will evaluate the possibility of adding this feature after we release our new IntelliSense engine.

[support]

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.

• This reply was modified 10 years, 3 months ago by support.

[support]

Hi,

Sorry for the delayed reply. We have been switching to the new forum engine. If you need an urgent answer, please contact our support email, we answer that within 24-48 hours.

Let us know if you experience further problems with your setup.

• This reply was modified 10 years, 3 months ago by support.

[support]

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?

[support]

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.

[support]

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/

[support]

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.

[support]

Hi,

Please check permissions on the “C:Program Files (x86)SysprogsVisualGDB\VisualGDB.exe” file. Can you run it manually from Command Prompt?

[support]

Hi,

We have updated our OpenOCD package to support the Nucleo-F411RE board correctly. You can update it via Tools->Embedded Tools Manager.

[support]

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.

[support]

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.

[support]

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.

[Author]

Posts