From owner-freebsd-arm@freebsd.org Wed Jul 5 20:31:00 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 8984CD90FED for ; Wed, 5 Jul 2017 20:31:00 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 6DA8C6F70F for ; Wed, 5 Jul 2017 20:30:59 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d871a72f-61c0-11e7-bfcf-afd4446ba3af 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 outbound1.ore.mailhop.org (Halon) with ESMTPSA id d871a72f-61c0-11e7-bfcf-afd4446ba3af; Wed, 05 Jul 2017 20:30:55 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v65KUpCR001791; Wed, 5 Jul 2017 14:30:51 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1499286651.4402.40.camel@freebsd.org> Subject: Re: HummingBoard-i2 does not boot from install image From: Ian Lepore To: Yoshiro MIHIRA , freebsd-arm Date: Wed, 05 Jul 2017 14:30:51 -0600 In-Reply-To: References: 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.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 20:31:00 -0000 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. -- Ian