From owner-freebsd-arm@FreeBSD.ORG Sat Jan 21 23:29:11 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2477A106566B; Sat, 21 Jan 2012 23:29:11 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id D07868FC12; Sat, 21 Jan 2012 23:29:10 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q0LNT9cK093368; Sat, 21 Jan 2012 23:29:09 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.119] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id viirbjvg6jfnbekexwyvbdqxin; Sat, 21 Jan 2012 23:29:09 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Sat, 21 Jan 2012 15:29:08 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <101D3416-6B61-4840-A89E-4CF91B0BB8BC@kientzle.com> References: <23CB6C35-9450-40BA-9FA3-37C44B328CA8@freebsd.org> <8042D895-3B3D-431E-ADCC-A150BDC838ED@kientzle.com> <7E53112E-DE29-4145-B597-D39AA77252C5@kientzle.com> To: Rafal Jaworowski X-Mailer: Apple Mail (2.1251.1) Cc: arm@freebsd.org Subject: Re: FreeBSD and BeagleBone X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 23:29:11 -0000 On Jan 21, 2012, at 2:13 AM, Rafal Jaworowski wrote: >=20 > On 2012-01-21, at 08:34, Tim Kientzle wrote: >=20 >> On Jan 20, 2012, at 7:26 AM, Mark Murray wrote: >>=20 >>>> For the moment, I'm more curious about just how far I can push this >>>> using FreeBSD tools only. >>>=20 >>=20 >> But ubldr still won't run: >>=20 >> U-Boot# fatload mmc 0 0x80008000 ubldr >> U-Boot# bootelf 0x80008000 >> >>=20 >> Anyone else used U-Boot to run ubldr on Arm? >=20 > Looking at memory addresses you use for loading etc. the problem you = might be hitting is with a linking address range: ubldr by default is = linked against 0x1000000, and the bootelf command would follow this = while parsing ELF and placing code/data in memory. If your system config = does not allow available RAM in this range it would crash / hang. If = this is the case, please try to adjust linking addr range in = sys/boot/arm/uboot/ldscript.arm to fit your layout and see if this = helps. That certainly does help. Setting the ELF linking address to 0x80001000 gets this far: U-Boot# fatload mmc 0 0x82000000 ubldr U-Boot# bootelf 0x82000000 ## Starting application at 0x80001054 Consoles: U-Boot console Compatible API signature found @8ff760c0 I think I need to track down some more information on the memory layout U-Boot uses on this board. I haven't checked yet, but I presume the last lines above are actually being printed by ubldr through the U-Boot console routine. If so, that means I've gotten far enough to use printf debugging to trace through ubldr and start understanding how it works and where it's stopping. Thanks much! Tim P.S. Is it worth trying to generalize the ubldr Makefile to accept some form of link address specification?