public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] DDR SDRAM in DIMM module for Yosemite-like PPC440EP board.
Date: Fri, 20 Oct 2006 13:59:28 +0200	[thread overview]
Message-ID: <200610201359.28991.sr@denx.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C04385D@ehost011-3.exch011.intermedia.net>

Hi Leonid,

On Friday 20 October 2006 08:30, Leonid wrote:
> I'm trying to port u-boot for "Yosemite-like" board with AMCC PPC440EP
> CPU. The difference between this board and Yosemite itself is that it
> has 4 128M banks of DDR SDRAM instead of 2 and (which is probably more
> important) these chips are on DIMM module.

If you are using DIMM modules, please don't use the board specific DDR init 
code of the Yosemite, but the cpu specific DDR init code f?r DDR DIMM 
modules, like the other 440 AMCC eval boards do (e.g. ocotea, bamboo).

> I think I've configured 
> everything correct, see SDRAM registers block from BDI2000 config file
> below:
>
> ; Setup SDRAM Controller (DDR SDRAM)
> WDCR    0x10    0x00000082      ;Select SDRAM0_CLKTR

<snip>

> However MRSC bit of SDRAM0_MCSTS register never gets set meaning SDRAM
> controller has never successfully completed the Mode Register Set
> Command. Attempts to read memory also fail (from BDI2000 itself and from
> u-boot where I've modified memory configuration of course).

Please modify your U-Boot configuration to use the cpu/ppc4xx/spd_sdram.c 
code. The following lines should be added to your board config file (with the 
correct I2C addresses of course):

/*-----------------------------------------------------------------------
 * DDR SDRAM
 *----------------------------------------------------------------------*/
#define CONFIG_SPD_EEPROM       1        /* Use SPD EEPROM for setup     */
#define SPD_EEPROM_ADDRESS {0x53,0x52}  /* SPD i2c spd addresses        */

> That can be HW problem of course, but may be somebody can suggest any
> configuration problem leading to similar symptoms? Any ideas at all?

Yes, a HW problem is also possible. What termination are you using? Did 
you "clone" the HW design from some IBM/AMCC eval boards?

Best regards,
Stefan

  reply	other threads:[~2006-10-20 11:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  6:30 [U-Boot-Users] DDR SDRAM in DIMM module for Yosemite-like PPC440EP board Leonid
2006-10-20 11:59 ` Stefan Roese [this message]
2006-10-20 15:57   ` Leonid
2006-10-20 16:04     ` Ben Warren
2006-10-20 16:23       ` [U-Boot-Users] DDR SDRAM in DIMM module for Yosemite-likePPC440EP board Leonid
2006-10-20 16:50         ` Ben Warren
2006-10-20 17:46           ` Stefan Roese
2006-10-20 18:02           ` [U-Boot-Users] DDR SDRAM in DIMM module forYosemite-likePPC440EP board Leonid
2006-10-20 18:33             ` Stefan Roese
2006-10-20 18:47               ` Leonid
2006-10-20 21:00                 ` Stefan Roese
2006-10-21 10:18                   ` Stefan Roese
2006-10-22  2:38                     ` Leonid
2006-10-22 11:12                       ` Stefan Roese
2006-10-22 19:43                         ` Leonid
2006-10-24  4:14                         ` Leonid
2006-10-24  7:09                           ` Stefan Roese

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=200610201359.28991.sr@denx.de \
    --to=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox