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 forYosemite-likePPC440EP board.
Date: Tue, 24 Oct 2006 09:09:49 +0200	[thread overview]
Message-ID: <200610240909.49584.sr@denx.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C58AA6A@ehost011-3.exch011.intermedia.net>

On Tuesday 24 October 2006 06:14, Leonid wrote:
> Now I pass sdram0_mcsts status check (our HW folks said there was some
> clock marginality they fixed

Hopefully no further "marginality" problems are hidden.

> ) and proceed to program_tr1() function 
> which fails:
>
> U-Boot 1.1.4 (Oct 23 2006 - 20:28:01)
>
> CPU:   AMCC PowerPC 440EP Rev. B at 333.333 MHz (PLB=133, OPB=66, EBC=33
> MHz)
>        I2C boot EEPROM disabled
>        Internal PCI arbiter disabled, PCI async ext clock used
>        32 kB I-Cache 32 kB D-Cache
> Board: Yosemite - AMCC PPC440EP Evaluation Board
> I2C:   ready
> DRAM:  get_spd_info banks 1 Addresses: 0x51
> DIMM: slot 0: populated, bytes 128 size 8
> DIMM: slot 0: DDR SDRAM detected
> DIMM: 0 voltage level supported.
> DIMM: sdram0_cfg0 0x02000000 -> 0x00000000 -> 0x04000000.
> DIMM: sdram0_cfg1 0x00000000 -> 0x00000000.
> DIMM: sdram0_rtr 0x04100000.
> DIMM: sdram0_tr0 0x00894012 -> 0x00000000 -> 0x408A4012.
> DIMM: sdram0_b0cr 0x000C6001 base 0x00000000 size 0x10000000.
> DIMM: sdram0_b1cr 0x100C6001 base 0x10000000 size 0x10000000.
> DIMM: total size 0x20000000
> Starting memory test ....
> ERROR: Cannot determine a common read delay.
> ### ERROR ### Please RESET the board ###
>
> I tried several hardcoded tr1 values, it doesn't work either - code
> crashes on read/write attempts - I must investigate where exactly by
> reviewing assembler - GDB debugging on C level was not very helpful. But
> I believe it still same HW problem - situation became better, yet not
> good enough...

Did you try different DDR modules? I would suggest to start with small 
modules, perhaps only with one bank. For bigger modules you have to make sure 
that enough TLB entries are set up.

Best regards,
Stefan

      reply	other threads:[~2006-10-24  7:09 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
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 [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=200610240909.49584.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