This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: help! redboot console
Dear Paul D. DeRocco,
Thank you for your advice! This problem is solved!
Yes, I use a simple bootloader to load the ram-based Redboot since Redboot has not been successfully ported to this board so far. But I confirm that this simple bootloader has correctly initialise the board as big-endian. If not, I don't think it can run well, nor can Redboot. But when Redboot prints something, this problem happens.
This time I force to set big-endian a second time though the simple bootloader has done that job. And the information output by Redboot is CORRECT now!
So I am confused. If it is a matter of little/big endian, why does the board run happily except that it outputs something wrong to console?
Best Regards,
--
kneep <caozhiyuan@hotmail.com>
On Sun, 9 May 2004 20:13:13 -0700
"Paul D. DeRocco" <pderocco@ix.netcom.com> wrote:
> > From: kneep
> >
> > Does endian affect the byte order of a STRING?
>
> When an object file is loaded, the data in it are loaded 32 bits at a time,
> not a byte at a time, so any disagreement between the order will show up as
> reversed bytes within each 32-bit word.
>
> > And I confirm that Redboot is compiled as big-endian and my
> > machine is running big-endian because everything goes well except
> > that problem.
> > So what will the point be?
>
> Don't know. But it sure smells like a big-endian/little-endian problem. You
> say you're running a RAM-based redboot. Does that mean that you're using
> something else to load redboot? If so, does that support big-endian mode?
>
> --
>
> Ciao, Paul D. DeRocco
> Paul mailto:pderocco@ix.netcom.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss