Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 Jul 2017 15:04:20 -0700
From:      Russell Haley <russ.haley@gmail.com>
To:        Ian Lepore <ian@freebsd.org>
Cc:        Yoshiro MIHIRA <sanpei.ml@gmail.com>, freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: HummingBoard-i2 does not boot from install image
Message-ID:  <CABx9NuQy50%2BaVoxdFS2AXn4BLgecmriE6Qyh=DU9noXdf_B8Qg@mail.gmail.com>
In-Reply-To: <1499286651.4402.40.camel@freebsd.org>
References:  <CALwmBx3O2Ovc%2B2ixGxoY5CFLe96M1C5tJeLMMR5vO=%2B=HTHSkw@mail.gmail.com> <1499286651.4402.40.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 5, 2017 at 1:30 PM, Ian Lepore <ian@freebsd.org> 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=<auto> partition=<auto>... 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABx9NuQy50%2BaVoxdFS2AXn4BLgecmriE6Qyh=DU9noXdf_B8Qg>