[ECOS] RedBoot porting problem

[ECOS] RedBoot porting problem

[Jeremy Lin]

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..

Thanks to all!

Regards, 
Jeremy Lin


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

RE: [ECOS] RedBoot porting problem

[Gary Thomas]

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

RE: [ECOS] RedBoot porting problem

[Jeremy Lin]

Hi, 
Thanks for all the replies. I will keep trying.
Here is how I test Redboot on my board so far,
I have a working gdb stub to boot up the board, then I
load the redboot image file (redboot.img), which is compiled
to run from RAM, by JTAG ICE and run it. The reason I need
to use JTAG instead of the existing gdb stub in flash to load
it is I have only one serial port on board. 
Then if it's working, since I don't have a flash programming 
driver for my board, I'm going to burn the ROM-Start image to EEPROM.

Thanks again!
Jeremy Lin

--- Gary Thomas <gthomas@cambridge.redhat.com> wrote:
> 
> 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
> 



__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/

Re: [ECOS] RedBoot porting problem

[Jonathan Larmour]

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.

Is this a public board? If so, it would be good if you could consider
contributing back. Mail ecos-maintainers@redhat.com to discuss further if
so!

> 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..

That implies both PC and SP are 0x0. Something's wrong there.

Also are sure your reprogramming of the board worked?

But my guess is that your RedBoot is hitting an exception of some sort
(e.g. by accessing an illegal memory address or whatever) on startup, which
causes it to enter the stub, as all exceptions do.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

RE: [ECOS] RedBoot porting problem

[Narayana, Venkat A.]

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..

Are you bringing up this from flash? If so 
what flash u r having,i mean u need to have
proper driver.
I ran into same issue sometime back and i discovered
that it is because of flash's timing issue. My flash
is Intel's strata running in x8 mode.
Do let me know how u made it work.

Venkat N