This is a quick guide on how to deploy the .NET Micro-Framework to the target using Eclipse and GDB. This might not be directly applicable to your case but you might get a general idea from it.
http://discovertheexperience.blogspot.c ... et_09.htmlIn the comments of that post is a trackback from another developer blog who did things a little bit differently. That might help too.
I used this tutorial to get an idea as well. If you are using the SAM-ICE then you might want to do the following:
Instead of getting OpenOCD in your External Tools menu, just add the JLink GDB-Server that came with your SAM-ICE (or this package for the Segger JLink ARM which is basically the same thing >>
http://www.segger.com/cms/jlink-software.html)
Instead of connecting your GDB Debugger to localhost:3333 (as you would for openOCD) you connect to localhost:2331 and then need to provide the debugger commands such as the basic initialization routines, load, break, etc.
I don't know what your build output looks like. Instead of pointing to a *.axf file as described in the blog about the .NET MF, you might want to point eclipse to the location of your *.elf file or equivalent. Not too sure about that, though.
Just in case (however unlikely) your target is an AT91SAM9162, you can find a GDB intialization script for that here:
http://yangchern.blogspot.com/2010/02/a ... cript.html