From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Ann Date: Wed, 6 Apr 2005 21:52:13 +0900 Subject: [U-Boot-Users] get_ram_size() returns wrong value In-Reply-To: <20050406104259.A79F8C108D@atlas.denx.de> References: <9b7ca65705040603187af7aa9c@mail.gmail.com> <20050406104259.A79F8C108D@atlas.denx.de> Message-ID: <9b7ca65705040605525c3317b5@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Apr 6, 2005 7:42 PM, Wolfgang Denk 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