HummingBoard-i2 does not boot from install image

[Russell Haley]

On Mon, Jul 24, 2017 at 6:00 AM, Yoshiro MIHIRA <sanpei.ml at gmail.com> wrote:
> 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.html
>
> If I have a time, I will try to solve this issue.

I had a quick peer at u-boot last week. As of last Tuesday, the port
was pointing at the wrong u-boot version so there is an issue they are
trying to fix with ports. That may play well for you because you could
grab it and try it and see if it works for you(there was a checksum
warning you will need to override). Either way, you could build u-boot
and have a look at the make output (not make install, it's already
assembled at that point). There are two pieces generated, the SPL
mentioned in your boot code is the base piece of u-boot I think. Then
there are board specific pieces you need to 'weld on'.  The old port
had a file that explained how to assemble the SPL and the board
specific parts.

Other non-binary options
- If you can't get your hands on u-boot 2013, you could move over to a
GNU/Linux platform and build u-boot from the solid-run u-boot fork
- Check if the u-boot 2017 build output has the same peices as the
2013 build output so this could be permanently rectified

I saw some comments in #bsdmips about Mr. Warner Losh updating u-boot
so now may be a good time to speak up. I personally would a, contact
Warner directly (imp at freebsd.org) and check bugillza
(https://bugs.freebsd.org/bugzilla/) for this otherwise you're voice
may get lost.

As an aside, I have a working SSD SATA drive on my HB right now too!
Hopefully that won't take too long to get the patch into head.

Good Luck,
Russ

> Thanks
> Yoshiro MIHIRA
>
>
> 2017年7月6日(木) 7:04 Russell Haley <russ.haley at gmail.com>:
>>
>> On Wed, Jul 5, 2017 at 1:30 PM, Ian Lepore <ian at 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 at 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