From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Matthias_Wei=DFer?= <m.weisser.m@googlemail.com>
Date: Fri, 23 Dec 2011 16:03:10 +0100
Subject: [U-Boot] testing u-boot on virtual environment
In-Reply-To: <CAG1KTJdVFD5ObWHxeRotcrn88crAsxM98FTd+3o07Rd2ivR2pA@mail.gmail.com>
References: <CAG1KTJeMNtkBoq0ALnqcEZQGpxSQ-Yhe5XVDTk98Z4awb_YKEg@mail.gmail.com>
	<4EF47AA9.4020802@gmail.com>
	<CAG1KTJdVFD5ObWHxeRotcrn88crAsxM98FTd+3o07Rd2ivR2pA@mail.gmail.com>
Message-ID: <4EF4982E.9030908@googlemail.com>
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

Hi ?rico

Am 23.12.2011 14:19, schrieb ?rico Porto:
> Thanks!
> 
> Tried to do some memory display commands but got instant segmentation
> fault, and tried to run it as root - but then some bad things
> happened, so now I know no one should run it as root.
> 
> I wanted to tryout a memory test algorithm I developed, but it seem
> u-boot runs with no ram access. If I could findout the ram address
> where it is located, I think then the 8MB it says it has wouldn't give
> me segmentation fault...

You could try to change the address passed to the mmap in
os.c: 92  void *os_malloc(size_t length) from NULL to something known.
0x20000000 worked well for me when I added the RAM simulation. The
approach of a fixed RAM address was nacked for mainline but for tests I
still use this approach.

Matthias