From mboxrd@z Thu Jan  1 00:00:00 1970
From: himbA <goavr@email.si>
Date: Fri, 02 Apr 2004 14:03:49 +0200
Subject: [U-Boot-Users] mtest
In-Reply-To: <20040402112139.B7352C109F@atlas.denx.de>
References: <20040402112139.B7352C109F@atlas.denx.de>
Message-ID: <406D56A5.2090102@email.si>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:

> Sorry, my crystal ball is in dire need of an ectoplasmic upgrade. :-)
> 

:)

OK, I did some more research - my SDRAM config is
PHYS_SDRAM_1            0xa0000000
PHYS_SDRAM_1_SIZE       0x04000000
CFG_DRAM_BASE           0xa0000000
CFG_DRAM_SIZE           0x04000000

those memory errors mentioned in earlier post do 
not appear if I change CFG_MEMTEST_END from 
0xa3efffff (- 63M) to 0xa3dfffff (- 62M). 
CFG_MEMTEST_START = 0xa0100000 (1M -). In 
config.mk TEXT_BASE = 0xa3f00000.

at bootup uboot displays
U-Boot code: A3F00000 -> A3F177B8  BSS: -> A3F1BAD8

Is there some uboot relevant stuff between 
0xa3efffff - 0xa3dfffff that I run over when doing 
mtest on all 63Mb? Code and stack seem to be safe.

regards, himba
-- 
..because under Linux "if something is possible in 
principle,
then it is already implemented or somebody is 
working on it".
							--LKI