Date: Thu, 12 Jul 2018 20:20:07 +0300 From: Greg V <greg@unrelenting.technology> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm@freebsd.org Subject: Re: Netbooting ROCK64 Message-ID: <1531416007.1431.0@hraggstad.unrelenting.technology> In-Reply-To: <20180712160051.ab6447bad4d97395552c3a5d@bidouilliste.com> References: <1531333209.1596.0@hraggstad.unrelenting.technology> <20180712120405.a16a2733473400e899f34d2f@bidouilliste.com> <1531392570.1456.0@hraggstad.unrelenting.technology> <20180712160051.ab6447bad4d97395552c3a5d@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 12, 2018 at 5:00 PM, Emmanuel Vadot <manu@bidouilliste.com> wrote: > On Thu, 12 Jul 2018 13:49:30 +0300 > Greg V <greg@unrelenting.technology> wrote: > >> >> >> On Thu, Jul 12, 2018 at 1:04 PM, Emmanuel Vadot >> <manu@bidouilliste.com> >> wrote: >> > On Wed, 11 Jul 2018 21:20:09 +0300 >> > Greg V <greg@unrelenting.technology> wrote: >> >> >> >> FreeBSD/arm64 EFI loader, Revision 1.1 >> >> (Mon Jul 9 18:05:19 UTC 2018 root@releng3.nyi.freebsd.org) >> >> Load Path: loader.efi >> >> Load Device: MAC(06d4ce39aa76,0x0) >> >> BootCurrent: 0000 >> >> BootOrder: 0008 0000[*] 0000[*] 0000[*] 2f10 0000[*] 0000[*] >> >> 0000[*] >> >> 0000[*] 0000[*] 2f30 0000[*] 3b50 fcf0 0000[*] 0000[*] 4ddc fef4 >> >> 0000 >> >> [*] 0000[*] 3b10 fcf0 0000[*] 0000[*] 4da8 fef4 0000[*] 0000[*] >> 3ba0 >> >> fcf0 0000[*] 0000[*] 2d40 fef4 0000[*] 0000[*] 8cf7 dffe b6f3 >> 7f3d >> >> 39b0 >> >> 5d06 b2e7 17d8 3b80 fcf0 0000[*] 0000[*] 0c30 fef7 0000[*] >> 0000[*] >> >> 0000[*] 0000[*] 0000[*] 0000[*] 0003 0000[*] 0000[*] 0000[*] >> 06e8 >> >> fefa >> >> 000 >> >> 0[*] 0000[*] 3be8 fcf0 0000[*] 0000[*] a108 fef6 0000[*] 0000[*] >> >> 57dc >> >> 5baf d956 2fed d6a0 fcf4 0000[*] 0000[*] 5fe3 ff37 62bf 9568 >> 3c90 >> >> fcf0 >> >> 0000[*] 0000[*] a25c fef6 0000[*] 0000[*] 06e8 fefa 0000[*] >> 0000[*] >> >> 0000[*] 0820 0000[*] 0000[*] >> >> Can't find device by handle >> >> Failed to find bootable partition >> > >> > ^^^^ >> > >> > This is your problem. >> > Do you have a nfs export serving the freebsd files ? >> >> Yeah, of course. >> >> And the u-boot script is explicitly configured to use it: >> >> env set serverip 192.168.1.2 >> env set baudrate 115200 > > This is a wrong baudrate, RK SoC is using 1.5Mbps It's using 1.5 Mbps by default, but I'm changing it here to 115200 because my UART dongle (CP2102) is not capable of 1.5Mbps, at least not without some firmware modification (http://www.olliw.eu/storm32bgc-wiki/How_to_configure_CP2102_USB_adapters_for_high_baud_rates) that I haven't done. The change works fine, it does actually switch to 115200 when starting the loader, and when it quits I get the U-Boot shell with the low baud rate :) >> env set bootargs boot.nfsroot.server=${serverip} >> boot.nfsroot.path=<PATH> comconsole_speed=${baudrate} >> tftpboot ${kernel_addr_r} loader.efi >> bootefi ${kernel_addr_r} ${fdtcontroladdr} > > I've never used nfs with loader like this, do you control the dhcp ? > If so just set the correct rootpath in it and in uboot just do : > setenv boot_targets dhcp > saveenv I have separate servers for DHCP and TFTP, so I use manual paths because U-Boot does not respect any of the "next-server" style DHCP options and always overwrites the TFTP IP with the DHCP server's IP. All the auto discovery things are starting the payload the same way anyway.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1531416007.1431.0>