From: Andrew Lunn <andrew@lunn.ch>
To: Mike Pashea <mpashea@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Update on Axiom CME555 Redboot FLASH Memory Problems
Date: Fri, 31 Aug 2007 06:51:00 -0000 [thread overview]
Message-ID: <20070831065144.GV19659@lunn.ch> (raw)
In-Reply-To: <BAY117-F3761D356A0FD58CDC6D8E4ACCD0@phx.gbl>
On Thu, Aug 30, 2007 at 12:15:34PM -0500, Mike Pashea wrote:
> Hi All,
>
> I have an update to report on the Axiom CME-555 Redboot crash that I posted
> about last week.
>
> I am certain that this is the same crash that Miguel Vega reported in
> earlier posts. However, I haven?t seen any follow-up postings where he
> described any permanent solution.
>
> Newer Axiom CME-555 boards have twice as much FLASH as the older boards
> because 29LV400?s are used instead of the 29LV200?s that were used when
> eCOS was ported to the CME-555. Modifying am29xxxxx_parts.inl to add the
> LV400 is pretty straightforward, but Redboot will crash with a segmentation
> fault on startup when it tries to run load_flash_config()located in
> flash.c.
>
> I found that in addition to adding the LV400 description, you also have to
> change the OR1 mask in line 89 of cme555.S:
>
> lwi r4, 0xfff80032
>
> should be changed to:
>
> lwi r4, 0xfff00032
>
> The new mask prevents the MPC555 memory unit from generating a fault when
> the upper half of the 29LV400 is accessed.
>
> One stray bit can sure cause a lot of problems?
Please could you submit a patch.
Thanks
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-08-31 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 17:15 Mike Pashea
2007-08-31 6:51 ` Andrew Lunn [this message]
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=20070831065144.GV19659@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mpashea@hotmail.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).