From: Steve Williams <steve@parsonscroft.plus.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MPC8548 L2 Cache
Date: Sun, 27 Aug 2006 11:54:09 +0100 [thread overview]
Message-ID: <44F179D1.7020208@parsonscroft.plus.com> (raw)
Hi,
I am porting u-boot to our new 8548 based board. Using a Vision Click
probe from Windriver as our debug tool.
Has anybody used the Vision Probe to flash an MPC8548 based system?
I am trying to use the L2 cache as RAM for the flash algorithm, all the
RAM tests that are provided by the Windriver stuff say the RAM is OK but
the system fails to flash hinting (error messages are not really a
strong point here) that it can't reliably write into the RAM.
Windriver suggest that the MPC8548 L2 cache, when used as RAM does not
work properly!
Has anybody used the L2 cache on an 8548 with any other probe (BDI2000?)
and had the flash algorithm run form L2 cache as RAM?
I can run code from this RAM to set stuff up like TLB's etc so I know it
works OK to that extent.
I find it hard to accept that a processor at this stage of development
would have such a fundamental problem.
I have used this technique with an 8560 based system and the Vision
Probe and it all works OK.
Any light that anybody can throw on this would be much appreciated, even
just to say which tool you used to flash a system with an MPC8548 in.
Regards
Steve Williams
reply other threads:[~2006-08-27 10:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44F179D1.7020208@parsonscroft.plus.com \
--to=steve@parsonscroft.plus.com \
--cc=u-boot@lists.denx.de \
/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