Date: Wed, 20 May 2020 10:15:54 +0200 From: "Herbert J. Skuhra" <herbert@gojira.at> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: rpi4 headless experience Message-ID: <87367vuimd.wl-herbert@gojira.at> In-Reply-To: <C2603B3E-69D6-45E7-B206-B5745C091F92@yahoo.com> References: <DBC7D277-D2B9-4B30-A1BE-7362F7AC54EB.ref@yahoo.com> <DBC7D277-D2B9-4B30-A1BE-7362F7AC54EB@yahoo.com> <alpine.GSO.2.20.2005192128330.14202@localhost.local> <C2603B3E-69D6-45E7-B206-B5745C091F92@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 May 2020 05:56:37 +0200, Mark Millard wrote: > I just realized that your original message said: > > "Just tried the latest FreeBSD on RPI image on my rpi4-4GB system." > > There is no such image for the RPi4. Looking at: > > https://lists.freebsd.org/pipermail/freebsd-snapshots/2020-May/000698.html > > shows: > > o 13.0-CURRENT aarch64 GENERIC > o 13.0-CURRENT aarch64 RPI3 > o 13.0-CURRENT aarch64 PINE64 > o 13.0-CURRENT aarch64 PINE64-LTS > o 13.0-CURRENT aarch64 PINEBOOK > o 13.0-CURRENT aarch64 ROCK64 > o 13.0-CURRENT aarch64 ROCKPRO64 > > Treating an RPi4 as a RPi3 is not going to > make everything work: it does not have > the right variant of u-boot, for example. > > The following lists installed files from ports: > > sysutils/u-boot-rpi[34] > sysutils/rpi-firmware > > The installations of the 2 prots only puts the files > someplace so they (or some) can later be copied to the > msdos file system involved. > > # ls -ldT /usr/local/share/u-boot/u-boot-rpi[34]/* > -rw-r--r-- 1 root wheel 124 Apr 25 00:16:57 2020 /usr/local/share/u-boot/u-boot-rpi3/README > -rw-r--r-- 1 root wheel 37 Apr 25 00:16:55 2020 /usr/local/share/u-boot/u-boot-rpi3/metadata > -rw-r--r-- 1 root wheel 499824 Apr 25 00:16:54 2020 /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin > -rw-r--r-- 1 root wheel 124 Apr 25 13:28:34 2020 /usr/local/share/u-boot/u-boot-rpi4/README > -rw-r--r-- 1 root wheel 37 Apr 25 13:28:34 2020 /usr/local/share/u-boot/u-boot-rpi4/metadata > -rw-r--r-- 1 root wheel 506360 Apr 25 13:28:34 2020 /usr/local/share/u-boot/u-boot-rpi4/u-boot.bin > > If you replaced the u-boot.bin in the msdos file system > with the rpi4 one the memory might well show correctly. > > There is also: > > # ls -ldT /usr/local/share/rpi-firmware/* > . . . > -rw-r--r-- 1 root wheel 89 Jan 30 13:26:19 2020 /usr/local/share/rpi-firmware/config.txt > -rw-r--r-- 1 root wheel 147 Jan 30 13:26:19 2020 /usr/local/share/rpi-firmware/config_rpi3.txt > -rw-r--r-- 1 root wheel 135 Jan 30 13:26:20 2020 /usr/local/share/rpi-firmware/config_rpi4.txt > -rw-r--r-- 1 root wheel 110 Jan 30 13:26:19 2020 /usr/local/share/rpi-firmware/config_rpi_0_w.txt > . . . > > where you would need to copy the config_rpi4.txt content > to the config.txt in use on the msdos file system. > > There are other files for the RPi4 from the list as well. > I've not checked a rpi3 snapshot do know if the snapshot > has copies of RPi4 specific files: > > -rw-r--r-- 1 root wheel 5888 Jan 30 13:26:31 2020 /usr/local/share/rpi-firmware/armstub8-gic.bin > -rw-r--r-- 1 root wheel 40659 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/bcm2711-rpi-4-b.dtb > -rw-r--r-- 1 root wheel 6193 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/fixup4.dat > -rw-r--r-- 1 root wheel 3089 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/fixup4cd.dat > -rw-r--r-- 1 root wheel 9181 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/fixup4db.dat > -rw-r--r-- 1 root wheel 9183 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/fixup4x.dat > -rw-r--r-- 1 root wheel 2775076 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/start4.elf > -rw-r--r-- 1 root wheel 775872 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/start4cd.elf > -rw-r--r-- 1 root wheel 4582664 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/start4db.elf > -rw-r--r-- 1 root wheel 3536680 Nov 22 09:06:45 2019 /usr/local/share/rpi-firmware/start4x.elf > > in the msdosfs file system. > > Note (where config.txt is a copy/variant of > config_rpi4.txt by content): > > # more /boot/efi/config.txt > arm_control=0x200 > arm_64bit=1 > dtoverlay=disable-bt > dtoverlay=mmc > device_tree_address=0x4000 > kernel=u-boot.bin > armstub=armstub8-gic.bin > > So, without armstub8-gic.bin being present > in the msdos file system, the RPi4 config.txt > content would then specify a missing file. > Similarly for u-boot.bin . The files listed above are all included on the RPI3 aarch64 image (e.g.: FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20200514-r361019.img) and I think I have also tried to replace u-boot.bin. -- Herbert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87367vuimd.wl-herbert>