From owner-freebsd-arm@freebsd.org Wed Jul 5 22:04:25 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 7AB23D935CE for ; Wed, 5 Jul 2017 22:04:25 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 0178E73032; Wed, 5 Jul 2017 22:04:25 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id h22so1184858lfk.3; Wed, 05 Jul 2017 15:04:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7ag9G1HzpQz8SW4xKV4sHLclSkPrLVEOIi+Hvg6MXVc=; b=uIk2fgVjqPHKN4tJ+hTvA5K54/lnkMmrlTeBHcg9DdGzrWTU5E7uXt+i8zot2jFpe+ Ya+pp8reX99M06mEd6CIAzwD+p+cMxaCFRZf0hmEKE9WxnP6eYr1R9VAxfmvaXXOwvhy C8bgXiF+JdC+DYXPv9dcTYhK8kUTiA0ZKL5QM2eFy0pYFT0FAaYa0fxusuPx3wsvG7rN VlZSXqYf7M+7N5Q1YEEON0LEo3YUsAReH22TihXEJfXKvjJ4soKcxfSjfHxfUkYIQTBo DLYlheoNfLo5lR2P24KWXa9jiWM4C24EF0rgGL5CxUf2nFWj+/zKlU+Qu4Um1nh0nJ1W go2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7ag9G1HzpQz8SW4xKV4sHLclSkPrLVEOIi+Hvg6MXVc=; b=KboH8YkU/NEALTxMTB5co6CvEAvlCfVlsAHJYBWtzOgzo1BGH/+avzxfQUJavjMWYc Ca7xyM68A2LlwYIYpX13wVwlElD0Tl9K5HnSCF3Yz0plgQaskU6D4aC5XaaCq4mVw7TZ lmowFD7eJpWtWbS93SQNtPhMdKK1jNCkEVyj8BdJy5DUmxb+P2P/RaXDNk5zG6RoMEMf FmImeQxf3YFyOJTIm9BM5K9/XjtwTrqtHSs6hWI3FkX181CQ1DIg1L1j3ux8xcNcV3K5 YUEjFUfgUMmMa6MUyDt97BENQaiEl9DT/xM0ZKkKetnDHKjItCybLFy6Qt8m3NB7Nr13 iWZg== X-Gm-Message-State: AKS2vOxcWk0pElEYF5Bt7cCi2Fb9Qp/iLwSs06A1U+gW+F3BRIOscSF+ g1Iz3K0wfvSiPzaa3oh2MLqDeLWL8w== X-Received: by 10.25.149.71 with SMTP id x68mr15621592lfd.136.1499292261327; Wed, 05 Jul 2017 15:04:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.82.211 with HTTP; Wed, 5 Jul 2017 15:04:20 -0700 (PDT) In-Reply-To: <1499286651.4402.40.camel@freebsd.org> References: <1499286651.4402.40.camel@freebsd.org> From: Russell Haley Date: Wed, 5 Jul 2017 15:04:20 -0700 Message-ID: Subject: Re: HummingBoard-i2 does not boot from install image To: Ian Lepore Cc: Yoshiro MIHIRA , freebsd-arm Content-Type: text/plain; charset="UTF-8" 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: Wed, 05 Jul 2017 22:04:25 -0000 On Wed, Jul 5, 2017 at 1:30 PM, Ian Lepore wrote: > On Wed, 2017-07-05 at 12:01 +0000, Yoshiro MIHIRA wrote: >> I have HummingBoard-i2 and I could not boot 12.0-CURRENT boot image. >> Please let me know to boot 12.0-CURRENT with HummingBoard. >> >> I tested >> FreeBSD-12.0-CURRENT-arm-armv6-CUBOX-HUMMINGBOARD-20170619- >> r320095.img >> >> And it does not boot up with below message[NG]. >> >> U-Boot SPL 2017.01-rc3 (Jun 13 2017 - 02:16:03) >> SPL: Unsupported Boot Device! >> SPL: failed to boot from all boot devices >> ### ERROR ### Please RESET the board ### >> >> I have a old image >> as FreeBSD-11.0-STABLE-arm-armv6-CUBOX-HUMMINGBOARD-20161221- >> r310359.img >> it can boot[OK]. >> >> Consoles: U-Boot console >> Compatible U-Boot API signature found @0x4f7708a8 >> >> FreeBSD/armv6 U-Boot loader, Revision 1.2 >> (root@releng2.nyi.freebsd.org, Wed Dec 21 18:14:05 UTC 2016) >> >> DRAM: 1024MB >> Number of U-Boot devices: 2 >> U-Boot env: loaderdev='mmc 0' >> Found U-Boot device: disk >> Checking unit=0 slice= partition=... good. >> Booting from disk0s2a: >> /boot/kernel/kernel data=0x6ec964+0x14b69c >> syms=[0x4+0x7cef0+0x4+0x90376] >> >> Hit [Enter] to boot immediately, or any other key for command prompt. >> Booting [/boot/kernel/kernel] in 4 seconds... >> >> Thanks >> Yoshiro MIHIRA > > I just downloaded that same 20170619 image and it boots fine on my > Cubox, but its build date/time are different: > > U-Boot SPL 2017.01-rc3 (Jun 19 2017 - 20:54:45) > > I don't have a hummingboard to test, but u-boot has always been able to > use the same image to boot a cubox and a hummingboard. There are different hummingboard baseboards and different hummingboard SOMs and they can be mixed and matched. The SOMs come in single, dual-lite, dual, and quad core configurations. The dual-lite and dual SOMs ARE NOT THE SAME architecture and require different uboot 'stuffs'. I don't remember off the top of my head, but I seem to remember having to build two parts of U-boot and then create one binary? I would wager that you have a dual-lite SOM and there is some 'stuffs' you will need to do with u-boot? I remember thinking I dodged a bullet by buying the dual and not dual-lite SOM so the stock image worked on my board. Sorry, I'm pinned busy right now so I can't look up what 'stuffs' means. It should be on the wiki or in the mailing list archives. Or was it in the u-boot readme in ports? :( Russ