Date: Mon, 23 Dec 2019 20:00:20 -0800 From: Mark Millard <marklmi@yahoo.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Attempt to update Rock64 to head -r355976 failed to boot afterwards, anyone have a recent FreeBSD booting a Rock64? Message-ID: <4119BA31-2BE1-41AF-B075-D6D6C488B43D@yahoo.com> In-Reply-To: <87E3B152-D7A1-4E9D-9710-3535F92B4DD2@yahoo.com> References: <78081E30-3758-46F3-A228-02B29CDAA6A6.ref@yahoo.com> <78081E30-3758-46F3-A228-02B29CDAA6A6@yahoo.com> <20191222113844.9385de125afd10e86358bc98@bidouilliste.com> <3C550401-A5BF-441E-81E6-29D5D917302B@yahoo.com> <FF778D08-0C49-4181-98B8-371003663F22@yahoo.com> <0AADC2F5-9867-40E7-B4C0-139CA16A3974@yahoo.com> <20191223153816.4e532acede0605a0c868a8e4@bidouilliste.com> <87E3B152-D7A1-4E9D-9710-3535F92B4DD2@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Dec-23, at 08:29, Mark Millard <marklmi at yahoo.com> wrote: > On 2019-Dec-23, at 06:38, Emmanuel Vadot <manu at bidouilliste.com> wrote: > >> On Sun, 22 Dec 2019 15:06:08 -0800 >> Mark Millard <marklmi@yahoo.com> wrote: >> >>> . . . >>> >>> The following forced the desired .dtb to be used: >>> >>> # more /boot/loader.conf >>> . . . >>> rk3328_rock64_load="YES" >>> rk3328_rock64_type="dtb" >>> rk3328_rock64_name="/boot/dtb/rockchip/rk3328-rock64.dtb" >>> . . . >> >> You need to put the dtb in the ESP partition under /efi/dtb/rockchip >> U-Boot dtb is sometimes different than the one we use for the kernel. >> > > I'll experiment with such, likely later today, thanks. > > . . . > Thanks for the notes. The results were . . . Putting the .dtb in the msdosfs file system as dtb/rockchip/rk3328-rock64.dtb worked the same as the loader.conf way for overall behavior, but no _load/_type/_name in /boot/loader.conf involved. Still, I supposed that having u-boot use the same DTB material that FreeBSD does might appropriate, at least if the u-boot is of an appropriate vintage relative to the kernel's DTB handling. I'm not clear on if there is a solid reason to prefer one way over the other. _load/_type/_name use automatically references updated files from the install operations, no extra copy operation needed. (But how risky is such automatic updating vs. not doing so?) I still see that my non-debug kernel build fails to complete a power-on boot for plain boot but works for "boot -v". I've not thought of a good way to gather information for the failure. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4119BA31-2BE1-41AF-B075-D6D6C488B43D>