This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: loading images with redboot
- To: Dan Conti <danc at iobjects dot com>
- Subject: RE: [ECOS] loading images with redboot
- From: Gary Thomas <gthomas at redhat dot com>
- Date: 10 Oct 2001 14:15:48 +0900
- Cc: "Ecos-Discuss (E-mail)" <ecos-discuss at sources dot redhat dot com>
- References: <D8DFF0AFE792914996F997E68FEC3A48F3ED@bunker.iobjects.com>
On Wed, 2001-10-10 at 14:10, Dan Conti wrote:
> > -----Original Message-----
> > From: Gary Thomas [mailto:gthomas@redhat.com]
> > Sent: Tuesday, October 09, 2001 9:57 PM
> > Subject: RE: [ECOS] loading images with redboot
> >
> > 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.
>
> I was giving redboot a bad command after issuing 'fis load' to it. If i
> just do 'fis load', then attach gdb, set the pc etc, my program runs
> fine. Sorry for the false alarm.
>
> I'm still at a loss as to why i can't do 'go 0x20040' from inside
> redboot. My eventual goal is to not have a debugger attached to this
> image. The image itself is apparently being transferred properly, since
> i can attach gdb and run it.
I'm a little perplexed as well - obviously we do this all the time too!
Can you get any hint what the program is doing when you run it that way?
There really should be no difference (modulo virtual vector I/O, but it
doesn't seem that this is your problem) when running it one way vs the
other.