This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: loading images with redboot


On Wed, 2001-10-10 at 13:44, Dan Conti wrote:
> > -----Original Message-----
> > From: Gary Thomas [mailto:gthomas@redhat.com]
> > Subject: Re: [ECOS] loading images with redboot
> > 
> > On Wed, 2001-10-10 at 12:23, Dan Conti wrote:
> > > the only other thing that i've noticed is that after i do 
> > 'load' i get
> > > lines like this from redboot:
> > > 
> > > Entry point: 0x00020040, address range: 0x00020000-0x000ae0cc
> > > 
> > > except the address range there makes no sense - that's 
> > 712908 bytes, my
> > > srec image is 1551644, and a bin objcopy of it is 581836.
> > 
> > 0xae0cc-0x20000=0x8e0cc=581836(base 10)  These numbers look 
> > right to me.
> 
> ahh yes, in my absent mindedness i forgot to subtract the 0x20000 at the
> beginning.
>  
> > > i'm getting this using the following command sequence in redboot: 
> > > 
> > > fis init -f
> > > reset
> > > load -v -m xmodem -b 0x20000 img
> > > fis create -b 0x20000 -l 1551644 -e 0x20000 -r 0x20000 img
> >                                       ^^^^^^^
> > Why noe 0x20040, which is the entry address given above?
> 
> because at the time i didn't quite understand why the reset vector on a
> given image doesn't point to the entry point for that image, but i
> figured it out just now. the revised line looks like this:
> 
> fis create -b 0x20000 -l 581836 -e 0x20040 -r 0x20000 img
> reset
> fis load img -b 0x20000
> go 0x20040
> 
> but this still doesn't seem to work.
> 
> i can (sort of) attach the debugger to an image that i load with 'fis
> load', but it's not stable enough for me to fully step through the
> image, so it's not very useful. 
> 

What's the problem?  I do this all the time.  The only thing that you
need to remember to do is set the PC before you start.
  (gdb) tar rem XXX
  (gdb) set $pc=0x20040
  (gdb) ...

If this doesn't work for you, we'd like to know the details.  As I said,
we use it all the time.

> > > reset
> > > fis load img -b 0x20000
> > > go 0x20000
> > > 
> > > at this point it hangs.
> > > 
> > > --
> > > Dan Conti             e danc@iobjects.com
> > > Software Engineer     p    (425) 289 0326
> > 
> > 
> > 



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]