From: Gary Thomas <gary@mlbassoc.com>
To: Mark Salter <msalter@redhat.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: [ECOS] Problem with little-endian RedBoot for GRG board
Date: Wed, 01 Sep 2004 13:14:00 -0000 [thread overview]
Message-ID: <1094044494.10166.563.camel@hermes> (raw)
In-Reply-To: <20040901122752.E40B678C2E@deneb.localdomain>
On Wed, 2004-09-01 at 06:27, Mark Salter wrote:
> >>>>> =?big5?B?V2lsbGlhbSBDaGVuICizr6n6rHUp?= writes:
>
> > Hi all,
> > I'm trying to run the little-endian RedBoot on GRG board.
> > I downloaded RedBoot 1.94 Pre-Built Binaries (includes NPE Ethernet support) from Intel, in that contains both big-endian and little-endian RedBoot binaries.
> > It runs successfully when i update the big-endian RedBoot binary to my GRG board, but it's fail to run when i update the little-endian binary.
> > I've tried to install the little-endian binary to GRG board by using flash programmer and updating from RedBoot and both case are failed.
> > If any one has experience about running little-endian RedBoot on GRG board ?
>
> If it is not running at all, then I suspect that you are programming
> the flash with a reversed byte order image. The toolchain will produce
> a little-endian image for a little-endian RedBoot. However, the GRG
> (and IXDP425) require the image programmed into flash to be big-endian.
> So, you need to take the little-endian redboot.bin and swap the byte
> order of all the 32-bit words before programming into flash. Another
> problem I have seen is that a number of GRG boards use A-step cpu
> which does not fully support little-endian. In that case, everything
> works except the NPE support.
>
> BTW, look for the GRG and IXDP425 little-endian support to be merged
> into CVS this week...
That's encouraging :-) Have you any word on the Copyright transfer?
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next parent reply other threads:[~2004-09-01 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19270553E4E629468D00357B1541AE67325402@earth.moxa.com.tw>
[not found] ` <20040901122752.E40B678C2E@deneb.localdomain>
2004-09-01 13:14 ` Gary Thomas [this message]
2004-09-01 13:41 ` Mark Salter
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=1094044494.10166.563.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=msalter@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).