From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 85xx running in RAM problems
Date: Thu, 18 Oct 2007 11:49:24 -0700 [thread overview]
Message-ID: <4717AAB4.6000603@ovro.caltech.edu> (raw)
In-Reply-To: <f87675ee0710181135j1e73d251if7175959f1ca8f3@mail.gmail.com>
Hi Robert,
> On my custom 8548 board I'm getting two different results - with a BDI
> [INIT] config, and without. With the BDI [INIT] config, I can get
> farther by setting the DDR2 ram size to be 256MB instead of what I
> have, 1GB. I have no other SDRAM besides DDR2.
Have you run any sort of memory tests from the BDI prompt?
For example, lets assume your BDI init file setups up
the DDR2 correctly, but there is a short on the board.
If you run some from of memory checks using the BDI
memory read/write commands, you should be able to detect
the short.
Common tests are walking 1's or 0's over the data bus,
and then clearing RAM and writing to one location, and
testing the result can't be read from more than one
location.
I'm not sure whether the BDI has these sorts of functions
built in, but there are people who've use Tcl/Expect to
layer on the BDI to build a test suite.
Unless you can guarantee your RAM is working fine, there's
no point in trying to get code to run.
The other option is writing a very small program you can load
using the BDI - not a stand-along U-Boot program, just
a stand-alone program that takes over from reset.
Hope that helps,
Dave
next prev parent reply other threads:[~2007-10-18 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 18:35 [U-Boot-Users] 85xx running in RAM problems robert lazarski
2007-10-18 18:49 ` David Hawkins [this message]
2007-10-22 14:01 ` robert lazarski
2007-10-22 17:37 ` David Hawkins
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=4717AAB4.6000603@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--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