From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Jeremy Lin <chienyul@yahoo.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] RedBoot porting problem
Date: Wed, 13 Jun 2001 13:14:00 -0000
Message-id: <XFMail.20010613141345.gthomas@cambridge.redhat.com>
References: <20010613185053.86839.qmail@web13908.mail.yahoo.com>
X-SW-Source: 2001-06/msg00479.html

On 13-Jun-2001 Jeremy Lin wrote:
> Hi,
> I use CVS version of eCos for my target.
> Now I have a working HAL and serial driver for 
> my platform(SAMSUNG KS32C50100 based), and
> the gdb stub works fine on my board. 
> I was trying to port redboot to my platform. I
> tried to compile it by choosing template "redboot"
> and it compiled successfully; I also have a set of
> ecm files which is copied from pid platform.
> But when I load the redboot image file and run it,
> instead of redboot banner, the serial port always
> outputs a string like this "$T0a0f:00000000;0d:00000000;#f9",
> just like what I got when using gdb stub.
> Does that mean it still in gdb protocol mode? How can I get
> the redboot mode? Please give me a hint..

It means that something went wrong when you started it up.  Are
you running this from ROM or RAM?

You can get a clue by simply connecting to your board via GDB
and getting a backtrace and register info.  This may give you
an idea why it is failing.

  % arm-elf-gdb -nw redboot.elf
  (gdb) set remotebaud 38400
  (gdb) tar rem /dev/ttyS0
  (gdb) info reg
  (gdb) bt