From mboxrd@z Thu Jan 1 00:00:00 1970 From: himbA Date: Fri, 02 Apr 2004 17:46:55 +0200 Subject: [U-Boot-Users] mtest In-Reply-To: <20040402124435.3ECD2C109F@atlas.denx.de> References: <20040402124435.3ECD2C109F@atlas.denx.de> Message-ID: <406D8AEF.5010301@email.si> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > In message <406D56A5.2090102@email.si> you wrote: > >>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. > > > What do you think where the stack and the malloc arena is in your > configuration? > I thought code starts at _TEXT_BASE (0xA3F00000) and stack is from 0xA3F177B8 to 0xA3F1BAD8 (u-boot header display suggested so). Your question was in place and I checked the start.S once again to find out that after reset and relocate we setup stack below _TEXT_BASE and not above. I corrected the CFG_MEMTEST_END to be just below malloc and stack. Thanks! regards, himba -- ..because under Linux "if something is possible in principle, then it is already implemented or somebody is working on it". --LKI