All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Enhanced SDRAM tests with u-boot
Date: Tue, 21 Oct 2003 02:17:13 +0200	[thread overview]
Message-ID: <20031021001718.86AC9C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 20 Oct 2003 19:03:22 +0200." <FIEJJAKAABLMHFKFECNJGEKOGPAA.tschaefer@giga-stream.de>

In message <FIEJJAKAABLMHFKFECNJGEKOGPAA.tschaefer@giga-stream.de> you wrote:
> 
> I have problems with the Bringup of a custom MPC8280 board and I assume
> that SDRAM could be the reason. When performing memory tests on the
> complete SDRAM with the test routines included with u-boot 0.4.5,
> everything is working fine. Also, u-boot is running without problems.
> But when booting a (known to work) linux kernel (2.4.18, MontaVista
> 3.0), I get exceptions after decompressing the kernel (alignment, 0x600)
> and when executing the initial scripts (program, 0x700). So I would like
> to perform more sophisticated SDRAM tests with u-boot, including burst
> tests. Is there anybody who has done this before? Any hints are
> appreciated.

I think it makes little sense  to  spend  effort  on  additional  RAM
tests.  From  the symptoms you describe you can be SURE that your RAM
initialization sequence is broken.

Better invest the time in fixing this.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
There is a time in the tides of men, Which, taken at its flood, leads
on to success. On the other hand, don't count on it.   - T. K. Lawson

      reply	other threads:[~2003-10-21  0:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 17:03 [U-Boot-Users] Enhanced SDRAM tests with u-boot Thomas Schäfer
2003-10-21  0:17 ` Wolfgang Denk [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=20031021001718.86AC9C59E4@atlas.denx.de \
    --to=wd@denx.de \
    --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.