From owner-freebsd-arm@freebsd.org Mon Jul 24 13:00:59 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 7D4E2C7DC66 for ; Mon, 24 Jul 2017 13:00:59 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (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 3449967A81; Mon, 24 Jul 2017 13:00:59 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: by mail-ua0-x22d.google.com with SMTP id f9so77785417uaf.4; Mon, 24 Jul 2017 06:00:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rDOSurjC5Rnr2nqdwYoSYFJWtYGF6RTKVyMzr3XvoRY=; b=HO+ldmR1HnQyTvv7/lQ5ITaZYIn8uQPf6NLfpEylMxR+YYmNB7N0vUkYLUGJsqCv5h KLm0IMnRDuNctgGoo/PyyASBTCL2EqOR+FlF+3Aeel1J5fhkhRO88o5kWSiskpK+yhkn kufEqnz0cYPXtgKIc0VqQMsLH+Oec4s/fBheGO3h8lI598fa4f0jFWrHo7JQQmxaPVsv mcUMHSkmfbxd8FRfoNSHmxLKfo5T9/isuh5nK0Zsvbcy9pACHIbscaV35qGwfmnnotfl IvXxZhN2BYyWMpiAhRmMjSvGcAMKpTc4m3AVMU0AioUpVxWOIoDhbMiFeaJwvzIJhPhi YPzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rDOSurjC5Rnr2nqdwYoSYFJWtYGF6RTKVyMzr3XvoRY=; b=NGdcch9mtT0RT95w2fq30tTo/LecfFn9+VaNRoOkEFZPstEXqOieAsKXzCSeYE+Og2 N03nubH2wFHzYkyLxJYpZXzhiG1VJFjhxm+RnKMkfgmtLy/SIr6k9U8BZ7KgwgFkdVlz JiOOdI/+S5SZ5fwvpPinIdVDb+Wn4OpHMXxLZhigRS5hAr+l7dOBm6k+un5wlbehtPea R1YvtXNsTAA9QwJcFa/g8x43P/kzCg35IoWmuqNZ21TYZ7kUjyzMdlbLbxNUSaofn9Mi uVc0V7R8mXE+iOgBBo2zwBpTEbQc1S6ttkED+jFpND40tforJOOLb4e8Kx6MwK073f/I Tmpw== X-Gm-Message-State: AIVw112elUlhi3lyKtilXdnAHVq+xFEyM84nkcSAy6u1KkAoAG7mqoRk Fbaz/vzPxuXkLbOPx7M1Tjbb+IFrYQ== X-Received: by 10.31.52.78 with SMTP id b75mr8704568vka.153.1500901257882; Mon, 24 Jul 2017 06:00:57 -0700 (PDT) MIME-Version: 1.0 References: <1499286651.4402.40.camel@freebsd.org> In-Reply-To: From: Yoshiro MIHIRA Date: Mon, 24 Jul 2017 13:00:47 +0000 Message-ID: Subject: Re: HummingBoard-i2 does not boot from install image To: Russell Haley , Ian Lepore Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Mon, 24 Jul 2017 13:00:59 -0000 Hi Russell, Thank you for your information. Temporary I could installed FreeBSD-12.0-current into my hummingboard-i2 with mixed image. 1. use u-boot of 11.0-RELEASE (U-Boot 2013.10-rc4 (Sep 29 2016 - 10:50:56)) 2. use kernel and userland from latest current image FreeBSD-12.0-CURRENT-arm-armv6-CUBOX-HUMMINGBOARD-20170717-r321072.img I will write the detailed steps to create mixed image in my blog. http://sanpeisbllog.blogspot.jp/2016/10/freebsdsolidrun-hummingboard-i2.htm= l If I have a time, I will try to solve this issue. Thanks Yoshiro MIHIRA 2017=E5=B9=B47=E6=9C=886=E6=97=A5(=E6=9C=A8) 7:04 Russell Haley : > 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=3D'mmc 0' > >> Found U-Boot device: disk > >> Checking unit=3D0 slice=3D partition=3D... good. > >> Booting from disk0s2a: > >> /boot/kernel/kernel data=3D0x6ec964+0x14b69c > >> syms=3D[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 >