Use of gdb with RedBoot and eCos from Windows host

[Jan Larcombe]

Hi,

I'm new to the use of gdb and I am having problems getting it to work.

I am using a single board computer (ARCOM Merlin) which is running
eCos, I
have been able to load and run simple programs on the board using the
"load -m ymodem" command and "Send File" from within HyperTerminal.
The  programs always run after typeing "go" without any problem.

I am now getting to the stage where I need to be able to debug the
application on the board and this is where I am running into problems.
I have looked around the net and can't find much which addresses
remote debugging. 
Anyway here are the questions.

When I build the eCos part of the system do I have to include all the 
source level debugging support (ie "include GDB stubs in HAL" and
include GDB external break support for stubs") or is this already
supplied by RedBoot?

I know that I put Redboot into GDB stub mode by typing a "$" on the
console do I have to load my application down prior to this or will
this all be handled by GDB later?

On my windows host I am running cygwin. After disconnecting
HyperTerminal
The commands that I have tried are as follows:
gdb
(gdb) lots of copyright stuff displayed
(gdb) set baudrate 57600 - this is the default rate that HyperTerminal
was  connected at.
(gdb) target remote COM2 - the COM port of the PC which is connected
to  the target processor (same as for HyperTerminal)

I am getting a number of error messages:

COM2: Not a typewriter - I have checked and my eCos build does have
tty serial drivers configured

or:
Segmentation fault (core dumped)

I am obviously missing a vital step in my setups - but I am not sure
what it
is

Thanks for any help you may be able to give


J P Larombe