Date: Mon, 5 Aug 2019 12:21:18 +0900 From: Denis Polygalov <dpolyg@gmail.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm@freebsd.org Subject: Re: Booting FreeBSD on Rock64 Message-ID: <668cc179-4f33-091e-d0b8-1c2fa52dbbaf@gmail.com> In-Reply-To: <20190728164619.7f40eccb59717d18996164b1@bidouilliste.com> References: <169de7cf-32f2-7b7b-c12e-a86a4b6a9e87@gmail.com> <20190715200127.4b649877d8baefeb5282df64@bidouilliste.com> <878b15d5-92a5-5137-121c-5a5038323857@gmail.com> <20190718145840.c4487d2174930374300a0d7d@bidouilliste.com> <300bcdce-1471-e9a6-e332-84d3f822a65c@gmail.com> <20190728164619.7f40eccb59717d18996164b1@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> BTW there is a new u-boot-rock64 port that you might want to use, you
> can boot from sdcard now.
>
I can confirm that the /usr/ports/sysutils/u-boot-rock64
works for me. The only thing I've noticed is that the u-boot
from ports does not read real MAC address from my board and
assign random one during each boot instead.
I'm not sure is this a bug or a future...
So my complete set of commands to manually boot ROCK64 is:
=> env set ethaddr 82:d6:05:XX:XX:XX
=> dhcp
=> tftpboot ${kernel_addr_r} boot/loader.efi
=> tftpboot ${fdt_addr_r} boot/dtb/rockchip/rk3328-rock64.dtb
=> fdt addr ${fdt_addr_r}
=> bootefi ${kernel_addr_r} ${fdt_addr_r}
Note that seems like the 'fdt addr' is essential here,
as distinct of ayufun's u-boot where it had no effect (for me at least).
You also need to connect pin 21 to GND in order to prevent
execution of the SPI (wrong one) u-boot.
Thanks a lot!
Denis.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?668cc179-4f33-091e-d0b8-1c2fa52dbbaf>