From owner-freebsd-arm@freebsd.org Sun Dec 17 17:29:42 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA907E8FA1B for ; Sun, 17 Dec 2017 17:29:42 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D48B77717 for ; Sun, 17 Dec 2017 17:29:42 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d6d4a100-e34f-11e7-93a5-cd02e7dc7692 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id d6d4a100-e34f-11e7-93a5-cd02e7dc7692; Sun, 17 Dec 2017 17:29:30 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id vBHHTenK003509; Sun, 17 Dec 2017 10:29:40 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1513531780.95072.29.camel@freebsd.org> Subject: Re: ubldr vs ubldr.bin? From: Ian Lepore To: Sergey Manucharian , freebsd-arm@freebsd.org Date: Sun, 17 Dec 2017 10:29:40 -0700 In-Reply-To: <20171111015041.GC1974@dendrobates.araler.com> References: <1436978285.1334.335.camel@freebsd.org> <20171111015041.GC1974@dendrobates.araler.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 17:29:42 -0000 On Fri, 2017-11-10 at 18:50 -0700, Sergey Manucharian wrote: > Excerpts from Ian Lepore's message from Wed 15-Jul-15 10:38: > > > > On Wed, 2015-07-15 at 15:04 +0200, Ronald Klop wrote: > > > > > > Hello, > > > > > > What is the difference between ubldr and ubldr.bin? > > > > > > [root at sheeva ~]# ls -l /boot/ubldr* > > > -r--r--r--  1 root  wheel  283086 Jul 11 00:34 /boot/ubldr > > > -r--r--r--  1 root  wheel  235212 Jul 11 00:34 /boot/ubldr.bin > > > -r-xr-xr-x  1 root  wheel  214432 Jan  8  2015 /boot/ubldr.old > > > > > > > > > Regards, > > > Ronald. > > ubldr is an elf binary that must be loaded at the address it was built > > for (the UBLDR_LOADADDR address).  ubldr.bin is a raw executable image > > (no elf headers) which is self-relocating and can be loaded at any > > address.  ubldr is launched with the bootelf command, and thus requires > > CONFIG_ELF in u-boot.  ubldr.bin is launched with "go ${loadaddr}". > > > > So all in all, ubldr.bin is the new way of things, and ubldr is still > > being built only for compatibility with people that have older u-boot > > installed.  (Right now that's pretty much everybody, because I haven't > > actually updated any of the u-boot ports yet to use ubldr.bin, because > > I've been too busy with $work.) > > > > The big thing ubldr.bin gets us is a common armv6[hf] userland that runs > > on any board.  Previously the single userland difference between various > > arm boards is that UBLDR_LOADADDR was different for each board. > > > > -- Ian > Sorry for the resurrection of this old thread. > > Why the mainstream u-boot cannot run ubldr.bin? Or am I missing > something? > > I tried with BeagleBone Black and it doesn't work, resets CPU when > trying: > > load mmc 0:1 0x82000000 ubldr.bin > go 0x82000000 > > -S > Some bug fixes from PR 224008 were applied recently (about a week ago), I wonder if they might fix the problem you're seeing? -- Ian