All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Machalek <adam.machalek@astc-design.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: X-loader / U-Boot query
Date: Thu, 08 Oct 2009 09:46:42 -0500	[thread overview]
Message-ID: <4ACDFB52.2080100@astc-design.com> (raw)
In-Reply-To: <4ACDE1DF.1010303@mlbassoc.com>

The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c

Function do_sdrc_init()

There is an assumption that the RAM size on each CS is maximum of 128M.  
See this line:

writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY |
      RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 |
      DEEPPD | DDR_SDRAM, &sdrc_base->cs[cs].mcfg);


Adam

Gary Thomas wrote:
> I have a new board - OMAP 3530 with 512MB DRAM & NAND
> I've build X-loader and U-Boot for it and it mostly comes
> up.  The sources I used (based on recommendations from the
> BeagleBoard pages) were:
>   http://git.gitorious.org/x-load-omap3/mainline.git
>   git://git.denx.de/u-boot.git
>
> I had to make a small change to get it to recognize the
> larger NAND FLASH device.
>
> The problem I have now is that it's only seeing 1/2 (256MB)
> of the available DRAM.
>
> * Does anyone know how to get it to see all 512MB?
> * Is there a better place to ask/discuss these questions?
>   A cursory look around did not point to anything fresh (most
>   of the web pages & Wikis I looked are are _years_ old)
>
> Thanks for any help/pointers
>


  parent reply	other threads:[~2009-10-08 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 12:58 X-loader / U-Boot query Gary Thomas
2009-10-08 13:52 ` shankarGanesh
2009-10-08 14:46 ` Adam Machalek [this message]
2009-10-08 14:48   ` Gary Thomas
2009-10-08 15:14   ` Menon, Nishanth
2009-10-08 15:17     ` Gary Thomas
2009-10-08 15:19       ` Menon, Nishanth
2009-10-08 15:54       ` Syed Mohammed, Khasim
2009-10-08 16:09         ` Gary Thomas
2009-10-08 16:17           ` Syed Mohammed, Khasim
2009-10-08 16:45 ` Dirk Behme

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=4ACDFB52.2080100@astc-design.com \
    --to=adam.machalek@astc-design.com \
    --cc=gary@mlbassoc.com \
    --cc=linux-omap@vger.kernel.org \
    /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.