From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ppc440epx : memory extention]
Date: Tue, 16 Sep 2008 15:51:46 +0200 [thread overview]
Message-ID: <200809161551.46350.sr@denx.de> (raw)
In-Reply-To: <000001c91802$31a15e30$94e41a90$@com>
On Tuesday 16 September 2008, sean wrote:
> I'd like to extend capacity of DDR2 memory from 256MB to 512MB on my
> custumn board.
So you have a custom board port for your specific board, correct? Is the DDR2
hardware design similar to the one on Sequoia? What are the differences here?
> EV Board(SEQUOIA) has 256MB DDR2 memory.
>
>
>
> When I reset the U-Boot program, U-boot show me the SDRAM test fail message
> like below.
>
>
>
> DRAM: 512MB
>
> SDRAM test fails at : 00000000
>
>
>
> What should I do to upgrade DDR2 memory??
>
> I have only modified follow sessions of U-Boot Code. Is it right??
>
> 1) Sequoia.h
>
> #define CFG_MBYTES_SDRAM (512)
Yes.
> 2) Sdram.c
>
> /* For 512M DDR Registers */
>
> mtsdram(DDR0_02, 0x00000000);
<snip>
Can't comment here. This is really complex and pretty board/DDR2 specific.
> And should I modify on table entry(in init.s)
>
> tlbentry( CFG_SDRAM_BASE, SZ_256M, CFG_SDRAM_BASE, 0, AC_R|AC_W|AC_X|SA_G)
Yes, you need to add another TLB entry for the 2nd 256MB. Or you could remove
those entries completely and use program_tlb() to add the TLB(s).
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2008-09-16 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 13:43 [U-Boot] [ppc440epx : memory extention] sean
2008-09-16 13:51 ` 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=200809161551.46350.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.