From: Bob Koninckx <bob.koninckx@o-3s.com>
To: Eric Gregory Castle <ecastle@engin.umich.edu>
Cc: Eric Castle <ecastle@umich.edu>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Axiom CME-555: RedBoot ROM crashing
Date: Thu, 27 May 2004 22:58:00 -0000 [thread overview]
Message-ID: <1085695182.2567.22.camel@pc-002.vuilenbos.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0405201847580.24824@red.engin.umich.edu>
Eric, sorry that it took me so long to reply. Becoming a father is a
good excuse tough :-)
On Tue, 2004-05-25 at 16:03, Eric Gregory Castle wrote:
> That's what I'd hoped, but using OCD commander and the wiggler seems to
> give rather bogus results. Stepping through results in rather random
> jumping that quickly ends at unknown opcodes or address 0xFFFFFFFF.
>
> Is there some sort of settings that need to be enabled to use a background
> debugger?
>
hmmm... stepping one instruction at a time should work since it does not
require write access to program memory on the powerpc. Are you sure you
initialize th processor as it should _before_ trying to step? You find
info on how to do this on axiom's website. Make sure your debugger works
using some piece of working software.
...
> > Floating point? Redboot does not use floating point instructions. May be
> > usefull for debugging to purposes to turn them on anyway
>
> Did you mean on, or to turn off floating point?
Turn them on. Even if redboot does not use them, the application you are
debugging might. Turning on floating point support makes sure redboot
saves floating point registers, enabling GDB to display their contents.
> I had all of these set except the last. This alters the priority of the
> serial module; why?
It is not really necessary I suppose. Just gave you the configuration
that works for me.
> >
> > Try stepping through the code from the reset vector and see how far you
> > get. Make sure the reset vector effectively gets you to the _start
> > routine. From what you describe, I doubt it will be the case.
>
> No, it doesn't seem to. Any idea why?
>
Nope. That's for you to find out :-)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-05-27 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405172218.i4HMIU7V028408@imr2.netsolmail.com>
2004-05-18 8:58 ` Bob Koninckx
2004-05-25 14:45 ` Eric Gregory Castle
2004-05-27 22:58 ` Bob Koninckx [this message]
2004-05-31 3:19 ` Eric Castle
2004-05-18 6:10 Eric Castle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1085695182.2567.22.camel@pc-002.vuilenbos.net \
--to=bob.koninckx@o-3s.com \
--cc=ecastle@engin.umich.edu \
--cc=ecastle@umich.edu \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).