FreeBSD-12.0-current not booting on hummingboard

[Yoshiro MIHIRA]

Hi all,

I have Hummingboard-i2.
I tested FreeBSD-12.0-RELEASE image.

Unfortunately, I have two issues.

1) u-boot issue.

Maybe latest u-boot does not support Hummingboard-i2. I use old u-boot
which is included 11.0-RELEASE.

>From sysutils/u-boot-cubox-hummingboard/pkg-descr:

>As of this writing,the changes in this fork have not been rolled back into upstream U-Boot.

2) GENERIC kernel issue

GENERIC kernel could not boot[NG]. If I use IMX6 kernel config, I can boot
it.

boot messages as blow:
https://www.sanpei.org/~sanpei/tmp/12.0-RELEASE-with-11.0-uboot-NG

If I have time, I will try to find out the reason and to support GENERIC
kernel on Hummingboard.

Yours
Yoshiro MIHIRA

2018年12月18日(火) 0:40 Ian Lepore <ian at freebsd.org>:

> On Sun, 2018-12-16 at 17:34 +0100, Radovan Ptec wrote:
> > Hi there,
> >
> > I've tried installing FreeBSD-12.0-RELEASE on hummingboard, however
> > it seems to
> > be broken,same problem with RC3. Can't test with earlier RC as I
> > didn’t
> > downloaded one and I can’tfind them anymore.
> >
> > 11.2 armv6 is working as expected, upgrading to 12.0 from source as
> > armv6 is
> > also working asexpected.
> >
> > Sorry, no serial console available, I've managed to fry it some time
> > ago.
> > After connecting HDMI I see following output in loop (adresses
> > change):
> >
> > pc : [<1792640c>] lr : [<4ff9f403>]
> > reloc pc : [<1782640c>] lr : [<17826403>]
> > sp : 4f672d08 ip : 4f59 fp : 4f5769dc
> > r10: 4ffb3f02 r9 : 4f57 r8 : 4ff9f40c
> > r7 : 4f89b250 r6 : 4f89 r5 : 4ffc10e r4 : ffffffff
> > r3 : 9ff01ce5 r2 : 9ff0 r1 : 4ffb3f02 r0 : 0000005e
> > Flags: nzCv IRQs on FIQs on Mode SVC_32
> > Code: f00968a0 b918f866 68e04641 ffb2f7ff (e7ef6824)
> > data abort
> >
> > At this point I'm not sure how to proceed with adressing this issue,
> > or how to debug
> > the problem.Any hints?
> >
> > Thank you!
> > radovan
>
> Nothing in freebsd creates output that looks like that. I think that
> must be u-boot that is crashing and generating that report. But I don't
> have anything useful to add beyond that observation.
>
> -- Ian
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>