From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc8313 SPL, relocate_code, large page NAND
Date: Tue, 20 Apr 2010 14:44:10 +0200 [thread overview]
Message-ID: <4BCDA19A.8050606@aimvalley.nl> (raw)
In-Reply-To: <op.vbgcuif7ke2gvs@tomo.bln.innominate.local>
It sure looks like an mpc8313 problem I once looked into
for quite some time. The solution was:
http://lists.denx.de/pipermail/u-boot/2009-March/049175.html
It could also be your DDR RAM not properly functioning. You
can let u-boot test it with the POST MEM test (which happens
before relocation).
next prev parent reply other threads:[~2010-04-20 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 8:36 [U-Boot] mpc8313 SPL, relocate_code, large page NAND Peter Vollmer
2010-04-20 9:12 ` Peter Vollmer
2010-04-20 9:57 ` Joakim Tjernlund
2010-04-20 12:12 ` Peter Vollmer
2010-04-20 13:30 ` Joakim Tjernlund
2010-04-20 12:44 ` Norbert van Bolhuis [this message]
2010-04-20 17:02 ` Peter Vollmer
2010-04-20 21:43 ` Scott Wood
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=4BCDA19A.8050606@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.