From: Jon Loeliger <jdl@freescale.com>
To: Pieter <phenning@vastech.co.za>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Trouble moving custom MPC8548 board to U-boot 1.3
Date: Tue, 06 Jan 2009 10:52:48 -0600 [thread overview]
Message-ID: <1231260769.21398.5.camel@ld0161-tx32> (raw)
In-Reply-To: <49635C62.5090307@vastech.co.za>
On Tue, 2009-01-06 at 15:28 +0200, Pieter wrote:
> Hi all,
>
> I have spent quite some time trying to move from U-Boot 1.2 to a newer
> version.. I am stuck at the initialization of the ram. The ram checksum
> fails and gives me a "total memory of 0". (the board has 512MB and work
> when booting uboot 1.2)
>
> can anyone pls. point me in the right direction?
>
> My console output is as follows:
>
> U-Boot 2008.10-00334-g90665e3-dirty-svn1154 (Jan 6 2009 -
> 13:40:47)
>
>
> CPU: 8548E, Version: 1.1,
> (0x80390011)
> Core: E500, Version: 1.0,
> (0x80210010)
> Clock
> Configuration:
>
> CPU:990 MHz, CCB:396
> MHz,
> DDR:198 MHz (396 MT/s data rate), LBC:49.500
> MHz
> L1: D-cache 32 kB
> enabled
> I-cache 32 kB
> enabled
> Board: Equus
> MPC8548
> PCI1: 64 bit, 66 MHz,
> sync
> I2C:
> ready
>
> DRAM:
> Initializing
>
> fsl_ddr_sdram
>
> starting at step 1
> (STEP_GET_SPD)
> SPD checksum unexpected. Checksum in SPD = 27, computed SPD =
> 74
> DIMM 0: failed
This is your root cause: Unable to get the SPD information
for the DDR DIMM in slot 0 of controller 0.
What part are you using? Does it support SPD?
Is your I2C to it hooked up correctly?
Can you dump the SPD information that is read?
Does it match the part specs?
HTH,
jdl
next prev parent reply other threads:[~2009-01-06 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 13:28 Trouble moving custom MPC8548 board to U-boot 1.3 Pieter
2009-01-06 16:52 ` Jon Loeliger [this message]
2009-01-09 13:32 ` Pieter
2009-01-09 13:32 ` Pieter
2009-01-09 15:38 ` Kumar Gala
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=1231260769.21398.5.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=phenning@vastech.co.za \
/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).