Forum Replies Created
-
Posts
-
Hi,
You need to make a post-build action because the header file will be updated during build. Simply use the Custom Actions page in the VisualGDB Project Properties dialog to setup a custom action. Note that you will need VisualGDB Custom Edition and higher.
You can also configure VisualGDB to use a cross-compilation toolchain (i.e. build the code on the Windows machine) to avoid this problem completely.
Hi,
Looks like you are using the Angstrom image for Beaglebone that requires special setup. Please follow this tutorial for details.
Note that you need to use a compatible toolchain. The new Debian-based toolchain will only work with Debian-based images.
Hi,
This looks like a bug in the Android toolchain caused by incompatibility between your Android version and the toolchain version. The only known solution to this is to try different toolchains (selected on the Makefile Settings page of VisualGDB Project Properties). If this does not help, please try another device.
Hi,
Linux kernel debugging is quite tricky compared to user-mode debugging as the debugging infrastructure misses many things that are taken for granted in user mode. E.g. loading symbols for a dynamically loaded kernel mode requires parsing internal Kernel structures and manually specifying section addresses.
We have created a separate product called VisualKernel that greatly simplifies all those tasks and provides out-of-the-box kernel debugging experience for most common Linux distros and we recommend using it for kernel debugging instead of VisualGDB.
Hi,
Please change the file extension to .S.
Note that the EWARM assembler syntax is different from the GNU ARM assembler syntax so you would need to change some directives. You can run the GCC with the -S flag to compile a .c/.cpp file into an assembly file to see a working example of an assembly file for your architecture.
We would recommend creating a basic “LED Blink” project and gradually replacing it with the files from the other project you want to use. This way you would start with a working project and would be able to address build errors (e.g. missing include directories or missing files) one-by-one.
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).
