Hi everyone,
I have a problem with the Jlink GDB server and the debugger on eclipse. The Jlink command line works completely fine though(which is sort of good news). For our project we are using

1) SEGGER GDBserver v4.02d to connect to the JLINK.
2) YAGARTO Eclipse/GNU-ARM toolchain as compile/debug solution.
3) Custom AT91SAM7 based board

So let me describe in detail what happens.

1) When I open the J link GDB Server , the J-link is connected(green), the target is detected(green) but the GDB is waiting for the connection(red)

2) Then I open eclipse and load the appropriate .elf file

3) Set the 'Initialize' commands to (Debug->Commands tab)
target remote localhost:2331

4) Set the 'Run' commands
monitor reset
monitor speed 30
monitor speed auto
monitor long 0xffffff60 0x00320100
monitor long 0xfffffd44 0xa0008000
monitor long 0xfffffc20 0xa0000601
monitor sleep 100
monitor long 0xfffffc2c 0x00480a0e
monitor sleep 200
monitor long 0xfffffc30 0x7
monitor sleep 100
monitor long 0xfffffd08 0xa5000401
set remote memory-write-packet-size 1024
set remote memory-write-packet-size fixed
set remote memory-read-packet-size 1024
set remote memory-read-packet-size fixed
symbol-file freertos.elf
continue

5) Then when I press debug, i have these errors on the console tab in Eclipse
target remote localhost:2331
Remote communication error: No such file or directory.
putpkt: write failed: No error.
monitor reset
putpkt: write failed: No error.
monitor speed auto
putpkt: write failed: No error.
monitor long 0xffffff60 0x00320100
putpkt: write failed: No error.
monitor long 0xfffffd44 0xa0008000
putpkt: write failed: No error.
monitor long 0xfffffc20 0xa0000601
putpkt: write failed: No error.
monitor sleep 100
putpkt: write failed: No error.
monitor long 0xfffffc2c 0x00480a0e
putpkt: write failed: No error.
monitor sleep 200
putpkt: write failed: No error.
monitor long 0xfffffc30 0x7
putpkt: write failed: No error.
monitor sleep 100
putpkt: write failed: No error.
monitor long 0xfffffd08 0xa5000401
putpkt: write failed: No error.
set remote memory-write-packet-size 1024
putpkt: write failed: No error.
set remote memory-write-packet-size fixed
putpkt: write failed: No error.
set remote memory-read-packet-size 1024
putpkt: write failed: No error.
set remote memory-read-packet-size fixed
putpkt: write failed: No error.
symbol-file freertos.elf
freertos.elf: No such file or directory.
continue
putpkt: write failed: No error.
kill
The program is not being run.
putpkt: write failed: No error.

AND
On the J link GDB server I have the following

SEGGER J-Link GDB Server V4.06b

JLinkARM.dll V4.06b (DLL compiled Jun 12 2009 13:25:42)

Listening on TCP/IP port 2331

J-Link connected
Firmware: J-Link ARM V6 compiled May 27 2009 17:26:00
Hardware: V6.00
S/N: 26000071
OEM: SAM-ICE
Feature(s): RDI

J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x3F0F0F0F (ARM7)
SAM-ICE found !
ERROR: Failed to retrieve protocol information
Connection to debugger closed !


ERROR: Attempt to connect failed

I am not able to figure out what the problem is. I have referred to the following link http://www.yagarto.de/howto/jlink/index.html.
And used the tutorial they recommend (which is actually found on the atmel website).

Any suggestions on how to overcome this problem??

Thanks,
Monish

I got around this problem by using "mon xyz" instead of "monitor xyz"

hope this helps