FreeBSD on the RaspberryPi 3

[Erik Moe]

Nice!  That fixed the serial console issues.  It gets as far as loading the kernel, but that’s about it.

U-Boot 2015.04 (Feb 17 2016 - 10:41:14)

DRAM:  944 MiB
WARNING: Caches not enabled
RPI: Board rev 8 outside known range
RPI Unknown model
MMC:   bcm2835_sdhci: 0
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

In:    serial
Out:   lcd
Err:   lcd
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0
Booting from: mmc 0 ubldr
reading ubldr
262739 bytes read in 330 ms (777.3 KiB/s)
## Starting application at 0x02000094 ...
Consoles: U-Boot console
Compatible U-Boot API signature found @3ab4a4c8

FreeBSD/armv6 U-Boot loader, Revision 1.2
(root at releng2.nyi.freebsd.org, Wed Feb 17 11:04:47 UTC 2016)

DRAM: 944MB
Number of U-Boot devices: 1
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=0x5f7ee4+0xf011c syms=[0x4+0x820c0+0x4+0x9490f]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by U-Boot at address 0x100.
Kernel entry at 0x2200100...
Kernel args: (null)

> On Mar 5, 2016, at 2:54 PM, Andrew Turner <andrew at fubar.geek.nz> wrote:
> 
> Try setting "init_uart_clock=3000000".
> 
> Andrew
> 
> On Sat, 5 Mar 2016 14:49:43 -0600
> Erik Moe <e.moe at rcn.com> wrote:
> 
>> My RaspberryPi 3 arrived last night.  I’ve taken the latest RPI-2
>> snapshot and updated to the latest firmware.  I can tell it’s booting
>> up, but it’s getting hung up somewhere.  I can’t tell where because
>> the serial console is spitting out gibberish.  The serial console
>> issue is not specific to FreeBSD.  I had the same issue trying to get
>> the serial console working on Raspbian.  There is a thread discussing
>> the problem here:  https://github.com/RPi-Distro/repo/issues/22.  On
>> Raspbian I was able to get around the serial console issue by adding
>> "force_turbo=1” to the config.txt, but that doesn’t seem to work on
>> FreeBSD.
>> 
>> Erik
>> 
>> 
>>> On Mar 4, 2016, at 7:58 AM, Andrew Turner <andrew at fubar.geek.nz>
>>> wrote:
>>> 
>>> On Wed, 2 Mar 2016 11:57:48 -0700
>>> Warner Losh <imp at bsdimp.com> wrote:
>>> 
>>>> I suspect that we'll need an aarch64 kernel and userland, at the
>>>> very least, to make this work. Plus there's likely some dragons
>>>> hiding in uboot / ubldr.  
>>> 
>>> Someone should try updating the firmware on the RPI2 image, and
>>> teaching the kernel about the Cortex-A53 in cpufunc.c. I suspect
>>> with these two FreeBSD will boot in AArch32.
>>> 
>>> Andrew
>>> _______________________________________________
>>> 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"  
>> 
>