You are using a arm toolchain when compiling.
Exactly how where you expecting a Windows machine using an x86 processor
to debug an arm application?
To debug the application, it must be run on a real arm processor - in some
situations, it is possible to run a remote gdb stub on the remote system
and using gdb on the PC to debug the code in the target system.
/PWM
On Wed, 2 Feb 2005, Mayank Kaushik wrote:
> Hi,
> I needed a (free) IDE to make life easier, im using Bloodshed Dev C++. I just set it up to use arm-elf-gcc.exe(Cygwin binary) ..Ive entered all options, paths, includes correctly (i think). When i click on "Rebuild All", my Makefile is triggered, and the project compiles succesfully. (ive set the linker up to produce a binary i can load into my microcontroller). (Im on WinXP)
> The compilation proceeds smoothly, and ends thus:
> ..
> ..
> ..
> arm-elf-gcc -nostdlib -Tld.script -N -o loader entry.o div0.o _udivsi3.o _umodsi3.o init.o crt0.o main.o asm_isr.o jump.o lib_AT91RM9200.o
> arm-elf-objcopy -O binary -j .text loader loader.text
> arm-elf-objcopy -O binary -j .data loader loader.data
> cat loader.text loader.data > loader.bin
> Execution terminated
> Compilation successful
> ==================================
> But Bloodshed Dev shows a "Warning: Project is not Compiled" at the end..then when i try to debug it, it says the above "Warning: Project is not Compiled" again, and doesnt proceed with the debug. If i click on Compile again, nothing happens obviously since nothing had changed..and the debug still doesnt happen.(Ive set it up with arm-elf-gdb)..
>
> Help :-(
> Regards
> Mayank
|