This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Axiom CME-555: RedBoot ROM crashing
- From: Eric Gregory Castle <ecastle at engin dot umich dot edu>
- To: Bob Koninckx <bob dot koninckx at o-3s dot com>
- Cc: Eric Castle <ecastle at umich dot edu>, ecos-discuss at sources dot redhat dot com
- Date: Tue, 25 May 2004 10:03:58 -0400 (EDT)
- Subject: Re: [ECOS] Axiom CME-555: RedBoot ROM crashing
- References: <200405172218.i4HMIU7V028408@imr2.netsolmail.com><1084861496.1160.18.camel@pc-002.vuilenbos.net>
On Tue, 18 May 2004, Bob Koninckx wrote:
> On Tue, 2004-05-18 at 00:18, Eric Castle wrote:
> > Hi again Bob, everyone on the list,
> >
> > We have an Axiom CME-555 board and are attempting to load RedBoot into
> > internal flash. We built this using the 2.0 version of eCos using the
> > configtool by:
> > 1) Selecting Axiom CME-555 and RedBoot from the templates menu
>
> that's ok
>
> > 2) Importing the redboot_ROM.ecm file.
>
> that's ok too
>
> > 3) Selecting the "RESET vector jumps to startup" option (this actually gets
>
> don't do that
Looked at that again, you were right.
>
> > it so that execution goes to the start of the program).
> >
> > We download the produced .elf file using the flash programmer in Metrowerks
> > CodeWarrior and a wiggler. The jumper settings are M-select off, Ram-select
> > 1, and Flash-select 2. We set the config switch so that 2, 4, 5, and 6 are
> > on (5 and 6 allow writes to internal flash, 2 and 4 are standard). This
> > allows us to successfully download RedBoot to internal flash.
> >
> > We then reset the board, setting the config switch so that only 2 and 4 are
> > on, and setting mode switch 2, switch 1 on, so that internal flash is
> > enabled. After opening a hyperterminal window (running at settings that are
> > at least compatible with a RAM version of RedBoot), we don't get any output.
> >
> > Examining the code, it seems to fail somewhere within RedBoot. We noticed a
> > few pieces of suspicious behavior (using OCD Commander to try stepping
> > through execution):
>
> If you have access to a bdm, it shouldn't be too hard to find out what's
> wrong
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?
> >
> > 1) It did not seem to recognize floating point instructions (maybe this is
> > just a failing of OCD Commander?)
>
> 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?
> In the powerpc 5xx variant hal package, turn on
>
> Variant FPU support
> enable internal flash
> set QSCI interrupt source priority to 31
I had all of these set except the last. This alters the priority of the
serial module; why?
>
> >
> > 2) It hung on a "RFI" instruction.
>
>
> Could be that something causes an exception (illegal instruction
> perhaps). Normally, redboot should not execute any rfi
>
>
> >
> >
> > Does anyone have any idea if how we configured RedBoot incorrectly, or what
> > is going wrong in our version of RedBoot? Any ideas or assistance would be
> > greatly appreciated.
>
> 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?
> Bob
>
> >
> > Thanks,
And more thanks,
-Eric
> > -Eric Castle and Miguel Vega
> > FEGI
> > University of Michigan
> >
> >
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss