public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Ann <ktdann@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] get_ram_size() returns wrong value
Date: Wed, 6 Apr 2005 21:52:13 +0900	[thread overview]
Message-ID: <9b7ca65705040605525c3317b5@mail.gmail.com> (raw)
In-Reply-To: <20050406104259.A79F8C108D@atlas.denx.de>

On Apr 6, 2005 7:42 PM, Wolfgang Denk <wd@denx.de> wrote:

Thanks for the hint. You are right I left out configuring memory controller.
Okay, now I've configured it, but it's still playing up on me.

> How is maxsize defined in your configuration?

maxsize is configured as,
#define CFG_MAX_RAM_SIZE    0x08000000  /* 0 .. 128 MB of (S)DRAM */

> How is your memory controller configured (address masks) ?

#define CFG_BANK0_START     0x00000000
#define CFG_BANK0_END       (CFG_MAX_RAM_SIZE/2 - 1)
#define CFG_BANK0_ENABLE    1
#define CFG_BANK1_START     (CFG_MAX_RAM_SIZE/2)
#define CFG_BANK1_END       (CFG_MAX_RAM_SIZE - 1)
#define CFG_BANK1_ENABLE    1

Rest is all disabled.

It gets to DRAM: 128MB, but soon after that, it wants to access
0x7FDEEB0, where there's no data. Looks like its configuration issue.
Guess I should look into it.

BTW, is it right by simply halving the MAX value ? I sort of guessed
this part. Looked at schemetics and they used 2 chip selects. So, I
figured halving it. Is it cool ?

-- 
Daniel

  reply	other threads:[~2005-04-06 12:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 10:18 [U-Boot-Users] get_ram_size() returns wrong value Daniel Ann
2005-04-06 10:42 ` Wolfgang Denk
2005-04-06 12:52   ` Daniel Ann [this message]
2005-04-06 13:20     ` Wolfgang Denk
2005-04-07  4:33       ` Daniel Ann
2005-04-07 22:21         ` Wolfgang Denk
2005-04-06 12:27 ` Jerry Van Baren
2005-04-06 13:05   ` Daniel Ann

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=9b7ca65705040605525c3317b5@mail.gmail.com \
    --to=ktdann@gmail.com \
    --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