From: "Vince Asbridge" <vasbridge@sanblaze.com>
To: "'Fillod Stephane'" <stephane.fillod@thomson.net>,
"'linuxppc-embedded'" <linuxppc-embedded@ozlabs.org>
Cc: u-boot@lists.denx.de, 'Stephen Shirron' <sshirron@sanblaze.com>
Subject: RE: [PATCH] RE: Some memory (DDR2 ECC Dual Rank) just doesn't work! Can anyone pointme to how to debug this hang?
Date: Thu, 14 Aug 2008 12:05:00 -0400 [thread overview]
Message-ID: <0b1f01c8fe27$81d6b250$4b01a8c0@sanblaze.com> (raw)
In-Reply-To: <0B45E93C5FF65740AEAE690BF3848B7AD38359@rennsmail04.eu.thmulti.com>
Stephane,
Thanks so much for your prompt reply.
We will pursue your suggestions, and let the forum know what we find. =
We're
at 1.3.0 uboot version.
Vince
> -----Original Message-----
> From: Fillod Stephane [mailto:stephane.fillod@thomson.net]=20
> Sent: Thursday, August 14, 2008 8:06 AM
> To: Vince Asbridge; linuxppc-embedded
> Cc: u-boot@lists.denx.de
> Subject: [PATCH] RE: Some memory (DDR2 ECC Dual Rank) just=20
> doesn't work! Can anyone pointme to how to debug this hang?
>=20
> Vince Asbridge wrote:
> > We have an 8548 design, which implements a DDR2 on a SODIMM=20
> We have an=20
> > issue with dual rank memory (specific part number Viking=20
> VR5DR287218EBSS1), which is a 1G ECC Registered SODIMM part,=20
> with two ranks.
> > Our platform wires CS0 and CS1 to the SODIMM slot.=20
> > At uBoot, all is well.=A0 Memory is discovered as ECC 533, 1G=20
> DDR2 64Bit 4 beat bursts, and mtest can read and write all 1G=20
> of the SODIMM.
> [...]
> > Other DDR2s (identical except for vendor and # of ranks),=20
> work perfectly!=20
> > Anyone got a clue what I could look at to try to figure this out?=20
> > We've tried enable / disable ECC at uboot We've tried=20
> enable / disable=20
> > Interleaving at uboot uboot always works (and can read/write entire=20
> > DDR), Linux always hangs on boot!
>=20
> U-Boot is too gentle when testing SDRAM. Make sure the caches=20
> are enabled under U-Boot, and put on heavy stress with DMA,=20
> pipelined prefetch's, etc.
> This is what your CPU is enduring under Linux.=20
>=20
> Your question is definitely a question for the U-Boot mailing list.
> BTW, what is the version of U-Boot in use? U-Boot is still=20
> missing the following patch:
>=20
> MPC85xx BA bits not set for 3-bit bank address DIMM of CS1
>=20
> The current implementation set the number of bank address bits
> (BA) in the processor for CS0 but not for CS1.=20
>=20
> Signed-off-by: Stephane Fillod <stephane.fillod@thomson.net>
>=20
> --- u-boot/cpu/mpc85xx/spd_sdram.c
> +++ u-boot/cpu/mpc85xx/spd_sdram.c
> @@ -365,6 +365,7 @@
> ddr->cs1_config =3D ( 1<<31
> | (odt_rd_cfg << 20)
> | (odt_wr_cfg << 16)
> + | (ba_bits << 14)
> | (spd.nrow_addr - 12) << 8
> | (spd.ncol_addr - 8) );
> debug("DDR: cs1_bnds =3D 0x%08x\n", ddr->cs1_bnds);
>=20
>=20
>=20
> Otherwise, recompile with -DDEBUG and CFG_CMD_SDRAM, grab the=20
> Viking datasheet and a scope, and a full cup of coffee/tea=20
> much needed during cross-checking :-)
>=20
> Cheers
> --
> Stephane
>=20
>=20
>=20
next prev parent reply other threads:[~2008-08-14 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 12:05 [PATCH] RE: Some memory (DDR2 ECC Dual Rank) just doesn't work! Can anyone pointme to how to debug this hang? Fillod Stephane
2008-08-14 16:05 ` Vince Asbridge [this message]
2008-08-14 16:31 ` Jon Loeliger
2008-08-26 21:28 ` Wolfgang Denk
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='0b1f01c8fe27$81d6b250$4b01a8c0@sanblaze.com' \
--to=vasbridge@sanblaze.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sshirron@sanblaze.com \
--cc=stephane.fillod@thomson.net \
--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;
as well as URLs for NNTP newsgroup(s).