From owner-freebsd-arm@freebsd.org Sat Nov 11 01:50:44 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 DF5C1E57FCF for ; Sat, 11 Nov 2017 01:50:44 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACFF96D504 for ; Sat, 11 Nov 2017 01:50:44 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: by mail-it0-x234.google.com with SMTP id n134so5166663itg.0 for ; Fri, 10 Nov 2017 17:50:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=WhNMQToH0+KwDSGKT4hQj+7bdMDJb5knzMBX5WpqavA=; b=LI5Nuwk3IYDXkloAF4LNiv0SrC6fcgnQFg35hQmbjDhITNW7jX1EmvKsndVpqfhtw/ Z2DJKupJTASRJVf+lt13kasG84lWaNUv968xlB27/bSItc67dV87oFR0qA6527VyqRan X5kQD44Xynqc9Ussn0kFMqrgVRk7Sxke8xQPzrtxA1gcUFMxG2t0eS3e6dhREEpEg7S9 SngTFM3kWfUV6HEwLV77oyUh6lVoKlpbI8/tQn77Dc43TcgeKlcPFiplWVXpX9f1K0VZ me9EgiM4wfYaDpZ2En1LtnkokHwmJabw88KDRkMl+KR1PAOV6Wdk3Eig9o9H8Lqg7b8n rhrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=WhNMQToH0+KwDSGKT4hQj+7bdMDJb5knzMBX5WpqavA=; b=RKnwc4LX0ASjQSVTkPgM6SwshQMnMC+dT6VN+cIGMaYWR36pYCtUvlaNMm6Xt/sNvm vgaCPHHu2jAAVebcaWRcQmeH0tEdyrtAahDjCyfHmiYIJFJUe/+2kFfC9SKW2g9+uRuh l7GUJv3fFrb7zW5aQUcEtqqjfdtPRNPjvtos/7hvBgGsJHEg/Nx5Bzw+8cljnS/cc4Uh peM8tDG3O8YnVxeiaqonL/2fWHQRsnF8ce/8hOzeoVjh1/ZDObAa/tdVv7+OvhHi4CUh n55ykS+MjoYsABG9FeB92bflCAtr47rYGh6L+HLmSj55nLGQETOBO3PMhPeMQGBieqOo Wgfg== X-Gm-Message-State: AJaThX523gTC4K62hTS/qQyqcvP/SkHyQvOSYvCUifOZN0xAy7JEz07K lzLdAS6OrrI0nVkGHsAvFCeKLRPQ X-Google-Smtp-Source: AGs4zMY4d5qhUNpduamb3XUeWhmwaNA7/fmd2EXoNAN6MrQYGMtOPUh/mUMj3vWg9luoulGHRLXGDg== X-Received: by 10.36.182.2 with SMTP id g2mr2921176itf.72.1510365044032; Fri, 10 Nov 2017 17:50:44 -0800 (PST) Received: from dendrobates.araler.com (174-16-108-74.hlrn.qwest.net. [174.16.108.74]) by smtp.gmail.com with ESMTPSA id 196sm5305400ioe.66.2017.11.10.17.50.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Nov 2017 17:50:43 -0800 (PST) Date: Fri, 10 Nov 2017 18:50:41 -0700 From: Sergey Manucharian To: Ian Lepore , freebsd-arm@freebsd.org Subject: Re: ubldr vs ubldr.bin? Message-ID: <20171111015041.GC1974@dendrobates.araler.com> References: <1436978285.1334.335.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1436978285.1334.335.camel@freebsd.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2017 01:50:45 -0000 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