Re: FreeBSD network boot on Raspberry Pi 4

Thank you for your suggestions.
I switched my FreeBSD source code tree to the head:
$ svn info
Path: .
Working Copy Root Path: /usr/home/denis/freebsd/base/head/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 363886
Node Kind: directory
Schedule: normal
Last Changed Author: mjg
Last Changed Rev: 363886
Last Changed Date: 2020-08-05 16:34:45 +0900 (Wed, 05 Aug 2020)

then rebuild everything. Result is exactly the same, no boot,
here is serial console output:

 >>Start PXE over IPv4.
   Station IP address is 192.168.10.201

   Server IP address is 192.168.10.10
   NBP filename is boot/loader.efi
   NBP filesize is 695808 Bytes
  Downloading NBP file...

   NBP file downloaded successfully.
Consoles: serial port
     Reading loader env vars from /efi/freebsd/loader.env
FreeBSD/arm64 EFI loader, Revision 1.1
(Wed Aug  5 18:14:26 JST 2020 denis@buildarm)

    Command line arguments: loader.efi
    Image base: 0x33841000
    EFI version: 2.70
    EFI Firmware: https://github.com/pftf/RPi4 (rev 1.00)
    Console: comconsole (0)
    Load Path:
    Load Device: MAC(DCA632932BAB,0x1)/IPv4(0.0.0.0)
    BootCurrent: 0003
    BootOrder: 0000 0001 0002 0003[*] 0004 0005 0006
    BootInfo Path: MAC(DCA632932BAB,0x1)/IPv4(0.0.0.0)
Ignoring Boot0003: Only one DP found
Setting currdev to net0:
bootp: no reply
No response for RARP request
net_open: RARP failed
Unable to open network interface 0 for exclusive access: 15
netboot: couldn't probe efinet0
net_open: netif_open() failed
Failed to find bootable partition

<-- here UEFI restarts if I understand correctly.

Initialising SDRAM 'Micron' 16Gb x2 total-size: 32 Gbit
Loading recovery.elf hnd: 0x00000000
Failed to read recovery.elf error: 3
Loading start4.elf hnd: 0x00000104
Loading fixup4.dat hnd: 0x00000103
MEM GPU: 76 ARM: 948 TOTAL: 1024
FIXUP src: 128 256 dst: 948 1024
Starting start4.elf @ 0xfec00200

NOTICE:  BL31: v2.3():v2.3
NOTICE:  BL31: Built : 10:40:51, Apr 21 2020
UEFI firmware (version UEFI Firmware v1.17 built at 16:07:05 on Jul 14 2020)

Regards,
Denis.


On 5/08/2020 2:12 am, Robert Crowston wrote:
> You’ll need 13-CURRENT. Things are gradually coming together. I think the only show stopper is a serious bug in the way we handle PCI-E DMA on models with >= 4 GB of RAM.
> 
> — RHC.
> 
> On Tue, Aug 4, 2020 at 15:27, Ronald Klop <[email protected]> wrote:
> 
>> On Tue, 04 Aug 2020 15:57:29 +0200, Denis Polygalov <[email protected]>
>> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to boot FreeBSD 12.1-RELEASE over network
>>> on Raspberry Pi 4 Model B.
>>> Well, the '12.1-RELEASE' doesn't matter here because
>>> seems like loader.efi cannot find and load kernel yet.
>>
>> Other people know more details than I do. But... RPI4 is very new. All
>> development to get it up and running is in 13-CURRENT.
>> You can try a snapshot build.
>>
>> More information can be found here:
>> https://wiki.freebsd.org/arm/Raspberry%20Pi
>> Latest snapshot can be found here:
>> https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/13.0/
>>
>> Regards,
>> Ronald.
>>
>>>
>>> I'm using RPi4 UEFI v 1.17:
>>> https://github.com/pftf/RPi4/releases/tag/v1.17
>>>
>>> and here is what I see on a serial console:
>>>
>>> ESC (setup), F1 (shell), ENTER (boot)..
>>>>> Start PXE over IPv4.
>>> Station IP address is 192.168.10.201
>>>
>>> Server IP address is 192.168.10.10
>>> NBP filename is boot/loader.efi
>>> NBP filesize is 610056 Bytes
>>> Downloading NBP file...
>>>
>>> NBP file downloaded successfully.
>>> Consoles: EFI console
>>> FreeBSD/arm64 EFI loader, Revision 1.1
>>>
>>> Command line arguments: loader.efi
>>> EFI version: 2.70
>>> EFI Firmware: https://github.com/pftf/RPi4 (rev 1.00)
>>> Console: efi (0)
>>> Load Path:
>>> (few minutes time delay here)
>>> bootp: no reply
>>> No response for RARP request
>>> net_open: RARP failed
>>> bootp: no reply
>>>
>>> Seems like the loader.efi is get executed but not all
>>> necessary parameters are passed to it...
>>>
>>> The host machine I'm using for testing is designated for
>>> network boot of various ARM based boards and I'm quite
>>> sure tftpd/dhcpd/nfsd configuration is correct.
>>> Here is relevant output of Nanopi-NEO2 board
>>> network boot performed on the same host machine:
>>>
>>> ... skipped ...
>>> ## Starting EFI application at 40080000 ...
>>> Consoles: EFI console
>>> Reading loader env vars from /efi/freebsd/loader.env
>>> FreeBSD/arm64 EFI loader, Revision 1.1
>>>
>>> Command line arguments: loader.efi
>>> EFI version: 2.70
>>> EFI Firmware: Das U-Boot (rev 8217.1024)
>>> Console: efi (0)
>>> Load Path: /dtb\allwinner\sun50i-h5-nanopi-
>>> Load Device:
>>> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/MAC(0201579f3216,0x1)
>>> Setting currdev to net0:
>>> net0: cannot set rx. filters (status=3)
>>> Loading /boot/defaults/loader.conf
>>> Loading /boot/device.hints
>>> Loading /boot/loader.conf
>>> Loading /boot/loader.conf.local
>>> Autoboot in 8 seconds, hit [Enter] to boot or any other key to stop
>>> Loading kernel...
>>> /boot/kernel/kernel text=0x93a61c data=0x1914c8+0x84ab1c
>>> syms=[0x8+0x138810+0x8+0x124a28]
>>> Loading configured modules...
>>> ... skipped ...
>>>
>>> is there anything I can do in order to get my RPi 4 booted over network?
>>>
>>> Best Regards,
>>> Denis.
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> [email protected] mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>>> To unsubscribe, send any mail to "[email protected]"
>> _______________________________________________
>> [email protected] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "[email protected]"
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"