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] new board SDRAM conf
Date: Mon, 3 Nov 2008 16:02:51 +0100	[thread overview]
Message-ID: <200811031602.51216.sr@denx.de> (raw)
In-Reply-To: <000001c93dc2$c88551e0$598ff5a0$@com>

On Monday 03 November 2008, ??? wrote:
> I create  My own board port(MFT board) . create configuration header and
> init.S But In the sdram.c(sdram_init->get_ram_size is 4 thus )func is
> failed , sdram is not founded . I think init.S is something wrong or
> CFG_MONITOR_BASE is  wrong ... .
>
> maybe you can point me to the right direction.
>
> It's my board init.S

Your init.S is not optimal but at least not the reason for the problem. You 
are programming a 256MB TLB entry for SDRAM. This is more than enough for 
your 128MB. You should fix this at some time but it not the problem right 
now. CFG_MONITOR_BASE is also most likely not the problem.

<snip>

> My SDRAM is  128MB mode 3, 13x10(4)
> And use external DDR_SDRAM Bank_0(BANKSEL_0)

OK.

<snip>

> /*-----------------------------------------------------------------------
>  * DDR SDRAM
>  *----------------------------------------------------------------------*/
> #undef CONFIG_SPD_EEPROM		/* Don't use SPD EEPROM for setup	*/
> #define CONFIG_SDRAM_BANK0	1	/* init onboard DDR SDRAM bank 0*/
> #define	CFG_SDRAM0_TR0		0x410A4012
> #undef CONFIG_SDRAM_ECC		/* enable ECC support		*/
>
> #if 1
> #define CFG_SDRAM_TABLE	{ \
> 		{(128 << 20), 13, 0x000A4001}, /* 128MB mode 3, 13x10(4)*/ \
> 		{(128 << 20), 12, 0x000A2001}, /* 128MB mode 2, 13x10(4)*/ \
> 		{(64 << 20),  13, 0x00084001}, /* 64MB mode 3, 13x9(4)	*/ \
> 		{(64 << 20),  12, 0x00082001}, } /* 64MB mode 2, 13x9(4)	*

Why do you define so many entries in this table? One (128MB mode 3) should be 
enough for you. If get_ram_size() doesn't return 128MB in this init function 
then you need to check whether you have a problems with the timings. Use a 
debugger (or test routines) to see if some bits fail etc.

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@denx.de
=====================================================================

  reply	other threads:[~2008-11-03 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  7:14 [U-Boot] new board SDRAM conf 조기성
2008-11-03  7:47 ` Stefan Roese
2008-11-03  9:51   ` 조기성
2008-11-03 10:11     ` Stefan Roese
2008-11-03 14:45       ` 조기성
2008-11-03 15:02         ` Stefan Roese [this message]
2008-11-04 10:23           ` 조기성
2008-11-04 10:46             ` 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=200811031602.51216.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