Date: Sat, 11 Aug 2018 23:48:40 +0300 From: Greg V <greg@unrelenting.technology> To: Ganbold Tsagaankhuu <ganbold@gmail.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Rockchip RK3399 (ROCKPro64) boots to multiuser Message-ID: <1534020520.35460.1@hraggstad.unrelenting.technology> In-Reply-To: <CAGtf9xPB2Rc-8L9fJuKLRRFgfA6hzcf3z6G-nALj4f6jX%2BKn1g@mail.gmail.com> References: <1533577708.4175.0@hraggstad.unrelenting.technology> <CAGtf9xPB2Rc-8L9fJuKLRRFgfA6hzcf3z6G-nALj4f6jX%2BKn1g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 11, 2018 at 3:09 PM, Ganbold Tsagaankhuu <ganbold@gmail.com> wrote: > > > On Tue, Aug 7, 2018 at 1:48 AM, Greg V <greg@unrelenting.technology> > wrote: >> Hi, >> >> I managed to boot FreeBSD on the Rockchip RK3399 SoC (Pine64 >> ROCKPro64 board): >> >> https://gist.github.com/myfreeweb/5f5b9e56f9a0fd1d63a46c34886f5ad1 >> > > Very nice. I have NanoPC-T4 board and will test your patch. > Did you try to load kernel via tftp at u-boot prompt? like: > > tftpboot 0x02000000 kernel.bin, go 0x02000000 > > Does it work for you that way? kernel.bin?? EFI has always been the way to go with aarch64 (and I think it's even recommended on armv7/6 too). I do it like this: env set serverip 192.168.1.2 env set bootargs boot.nfsroot.server=${serverip} boot.nfsroot.path=/some/path comconsole_speed=${baudrate} tftpboot ${kernel_addr_r} loader.efi tftpboot ${fdt_addr_r} dtb/rockchip/rk3328-rock64.dtb bootefi ${kernel_addr_r} ${fdt_addr_r} But the more-automated way (fully configured by dhcp) should work too, at least if you don't have dhcp and tftp on different servers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1534020520.35460.1>