Date: Mon, 24 Oct 2022 11:50:11 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Klaus K??chemann <maciphone2@googlemail.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: EDK2 on RPi3 was: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <DBA8B2E1-D596-4664-A6F3-893C43265317@yahoo.com> In-Reply-To: <20221024174930.GA79381@www.zefox.net> References: <1560695E-4D99-40A1-8D62-29EAB24C7997@yahoo.com> <20221005160737.GA15227@www.zefox.net> <136B9190-4C73-45FB-8B41-FEEF7C38A253@yahoo.com> <3A76826B-B4E6-4837-915E-C9E1172BEA20@yahoo.com> <DC32CA76-5072-4521-BCD8-CDF1512420D4@yahoo.com> <20221021175142.GA62386@www.zefox.net> <B90AA192-17B4-4FE3-8050-1E7889432ED4@yahoo.com> <0697DE1F-C626-4289-894A-4141CDF1B91B@yahoo.com> <71AB9FAC-EB00-48F0-B0DD-0629C2D3C8C0@googlemail.com> <5719632F-8A92-4784-88D8-EAE3F20F2FA3@yahoo.com> <20221024174930.GA79381@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Oct-24, at 10:49, bob prohaska <fbsd@www.zefox.net> wrote: > I'd like to thank both of you for the light you've shed on the > boot problems encountered with RPi.=20 >=20 > For the moment I'll go back to my original goal of getting > Pi2's to boot from the JMS-based usb-serial bridges presently > on-hand. Preliminary experiments using a JMS561 bridge and > a Pi2 using the version of bootcode.bin located at > https://github.com/raspberrypi/firmware/raw/master/boot/bootcode.bin > [referring page = https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#spec= ial-bootcode-bin-only-boot-mode] > seem to be promising under -current. bootcode.bin is only likely to help stages before u-boot.bin starts. If it makes to to u-boot.bin starting, bootcode.bin is then likely irrelevant from then on. In fact bootcoce.bin is what loads the start*.elf that is used. If the start*.elf starts, bootcode.bin is likely irrelevant past that point. [The purpose of bootcode.bin is the special boot mode, more recent versions having more adjustments. There is no special version of bootcode.bin that I'm aware of.] > The interest I expressed in EDK2 appears to have been misguided, > or at least premature. I was hoping it might be a more tractable > replacement for u-boot, but it's equally inscrutable to an amateur. > Worse, only the macciatobin flavor builds under poudriere and > my attempts at a plain "make" build using FLAVOR=3Drpi3 have so far=20 > failed on the same host. Was this based on mina ports before vs. after: QUOTE author Mark Millard <marklmi26-fbsd@yahoo.com> 2022-10-21 21:47:14 = +0000 committer Lorenzo Salvadore <salvadore@FreeBSD.org> = 2022-10-21 22:00:03 +0000 commit 819bf69c15605e1e31998c91fb3fd02d5bc9fa0f (patch) tree eb19abc8a6fc47da2072bcd9847e3431c4c9ec93 /sysutils/edk2 parent bf7a619316b5b24fe6a20df07881d7f2bce821d7 (diff) download ports-819bf69c15605e1e31998c91fb3fd02d5bc9fa0f.tar.gz ports-819bf69c15605e1e31998c91fb3fd02d5bc9fa0f.zip sysutils/edk2: Fix build on aarch64 Build on aarch64 was failing with the following error: ld-elf.so.1: /lib/libgcc_s.so.1: version GCC_4.5.0 required by /usr/local/lib/gcc11/libstdc++.so.6 not found Fix by using /usr/local/lib/gcc*/libgcc_s.so.1 instead. While here, also define WWW variable. END QUOTE I'll note that quarterly did not get the update yet. = http://ampere3.nyi.freebsd.org/build.html?mastername=3D131arm64-default&bu= ild=3D5bb856165324 shows sysutils/edk2@rpi4 as having successfully built: =3D>> Building sysutils/edk2 build started at Mon Oct 24 00:09:06 UTC 2022 port directory: /usr/ports/sysutils/edk2 package name: edk2-rpi4-g202202_1 building for: FreeBSD 131arm64-default-job-04 13.1-RELEASE-p2 FreeBSD = 13.1-RELEASE-p2 arm64 maintained by: uboot@FreeBSD.org Makefile ident:=20 Poudriere version: 3.2.8-21-g883afb07 Host OSVERSION: 1400063 Jail OSVERSION: 1301000 . . . =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<phas= e: package >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D> Building package for edk2-rpi4-g202202_1 = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D>> Cleaning up wrkdir =3D=3D=3D> Cleaning for edk2-rpi4-g202202_1 build of sysutils/edk2@rpi4 | edk2-rpi4-g202202_1 ended at Mon Oct 24 = 00:16:06 UTC 2022 build time: 00:07:00 (So built under 13.1-RELEASE.) It also shows sysutils/edk2@fvp has having built just fine. @rpi3 and the default build have not started building yet. 4 flavors (bhve, xen, and 2 qemu variants) are amd64 only and so are ignored. (sysutils/uefi-edk2-bhyve-csm is something separate.) =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DBA8B2E1-D596-4664-A6F3-893C43265317>