Hi
Do you know if gdb is working? You should be able to start a debug session from a standard MS-DOS command line, if you can't, then Eclipse won't be able to either.
It is possible that gdb's BDM stub is not working properly so you need to check that as well. I am assuming that you are using Codesourcery's m68k toolchain.
From an MS-DOS command line:
Change to the folder with your binary in.
Make sure that your toolchain folder is on your current PATH.
Enter:
m68k-elf-sprite -i
If the sprite and the BDM pod driver are installed properly you will see output something like this:
CodeSourcery ColdFire Debug Sprite (Sourcery G++ Lite 4.2-8)
pe: [speed=<n:0-31>&memory-timeout=<n:0-99>] P&E Adaptor
pe://USBMultilink/PE6013569 - USB1 : USB-ML-CF Rev C (PE6013569)
pe://CycloneProMaxSerial:1 - COM1 : Serial Port 1
pe://ParallelPortCable:1 - LPT1 : Parallel Port 1 (Address $0378)
ccs: [timeout=<n>&speed=<n>] CCS Adaptor
ccs://$Host:$Port/$Chain_position - CCS address
The parallel port and serial port are detected, but no device is shown. My USB pod is detected as you can see above.
If you don't see your BDM pod, then you have an installation problem of some kind.
Now you can try gbd. Type:
m68k-elf-gdb
You should see the GDM preamble and a (gdb) prompt.
Now enter the first line of the Eclipse debug startup script, which should be something like:
target remote | m68k-elf-sprite pe://USBMultilink/ m5282evb
You should get some output like:
Remote debugging using | m68k-elf-sprite pe://USBMultilink/ m5282evb
m68k-elf-sprite
pening P&E USBMultilink port 1 (USB1 : USB-ML-CF Rev C (PE6013569))
m68k-elf-sprite:Target reset
0x00000000 in ?? ()
If you don't, then you need to investigate what is wrong (paths, installation, etc.)
Now type:
load your_elf_file.elf
And gdb should load your executable (we don't specify the filename in our script because Eclipse sets it for us).
Finally type:
continue
And your code should be executed.
If all this works, then you know that you have a good gdb installation.
Now you need to set the check box on the Ecilpse debug configuration dialog, Debugger tab, that is called "Verbose console mode". If you try and start a debug session now, you will see the output from gdb in the console which should hopefully point you in the direction of the problem.
I hope that helps,
Paul.