Forum Replies Created
-
Posts
-
Hi,
Most likely you are missing the UI header file that is generated from the UI definition files on the remote machien as a part of the build. Please locate it on the remote machine and either copy it manually to the Windows machine, or setup a post-build action that will automatically download it after each build.
Hi,
This might happen in VisualGDB is unable to locate your AndroidManifest file. Could you please run a “tree /f” command in your source folder and send us the output?
You can filter out the .c files, but the other file names are important for us to pinpoint the problem.If you had an option to change the GDB Console font independently, would you set it to the same one the text editor uses, or a different one?
Currently you can change the default editor font via Tools->Options->Fonts and colors->Text Editor. We could set the the SSH console/GDB console font based on it.
Hi,
Please try adding –specs=rdimon.specs to your LDFLAGS. This should explicitly include the library providing the debug I/O functionality.
Hi,
Looks like the tar binary on the Edison board does not support all options needed by VisualGDB to transfer multiple files using tar. You can switch to the file-by-file mode via Tools->SSH Host Manager->(your SSH connection)->Edit->Transfer file groups using = File-by-file SCP.
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.
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).
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/
