public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Russell McGuire <rmcguire@videopresence.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 83xx DDR2 667Mhz memory
Date: Thu, 24 Apr 2008 12:32:21 -0700	[thread overview]
Message-ID: <000001c8a641$eac1beb0$e505a8c0@absolutdaddy> (raw)
In-Reply-To: <mailman.128014.1209064835.5026.u-boot-users@lists.sourceforge.net>

All,

Just curious if anyone has done any work with this near past.
I have had an 8360E board up for several months now and been happily working
away with different types of Kingston S0-DIMM DDR2 memory.

512MB, 1204MB, DDR2 533Mhz memory. All work well, with U-boot.
Using the SPD detectetion, things have just been automatically detected and
worked wonderful.

Yesterday I went down and purchased two additional sticks of 1024MB DDR2
Crucial 667Mhz memory, as 533Mhz is in short supply. SPD detect still works
in U-boot and everything is detected correctly. However, the u-boot will now
hang when it tries to transfer execution into RAM. At first I figured this
was a memory speed issue, since 667Mhz is not technically supported on the
8360E yet <Rev 2... I might be wrong on this?>, So I patched in a quick line
of code to force the spd detection to limit to 533Mhz.  Still doesn't work.

Any ideas? Again, same exact u-boot just different memory. SPD sees it all
just fine, just can't use the RAM after its setup. Currently using a
slightly older version of U-boot 1.3.0-dirty.

-Russ
 

       reply	other threads:[~2008-04-24 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.128014.1209064835.5026.u-boot-users@lists.sourceforge.net>
2008-04-24 19:32 ` Russell McGuire [this message]
2008-04-25 20:41   ` [U-Boot-Users] 83xx DDR2 667Mhz memory Jerry Van Baren
2008-04-30  1:53   ` Bruce_Leonard at selinc.com

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='000001c8a641$eac1beb0$e505a8c0@absolutdaddy' \
    --to=rmcguire@videopresence.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