Date: Sun, 30 Jul 2023 02:30:45 +0800 From: ykla <yklaxds@gmail.com> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-uboot@freebsd.org, FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: Some issues related to the port of Raspberry Pi. Message-ID: <CA%2BPGaYApMXqVtDrgMa2qwo6wQ7SCbR2r1sxxLyDKDv6Vi2YFmw@mail.gmail.com> In-Reply-To: <B2DB655F-49E3-4C52-A971-E1F62D6CD5DE@yahoo.com> References: <CA%2BPGaYA-irqcFFW3K59rSwqwUTFu78XGmq2UiKFsngV=GY-jPg@mail.gmail.com> <B2DB655F-49E3-4C52-A971-E1F62D6CD5DE@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] In https://github.com/FreeBSD-Ask/freebsd-ports/tree/main/sysutils/rpi-firmware we are indeed using the same version of Raspberry Pi firmware i.e. 1.20230405, I am using freebsd 13.2 release of u-boot, which one are you using? Mark Millard <marklmi@yahoo.com> 于 2023年7月30日周日 上午2:07写道： > On Jul 29, 2023, at 09:23, ykla <yklaxds@gmail.com> wrote: > > > > Hi, > > However, strangely, when I replaced the rpi4-firmware in the ports with > the latest version from the official Raspberry Pi source and copied it to a > USB drive, the system started to loop with the following code. > > > > --------------- > > > > Net: eth0:ethernet@7d580000 > > PCIe BRCM: link up, 5.0 Gbps x1 (SSC) > > starting USB…… > > Bus xhci_pci:Reglster 58000420 NbrPorts 5 > > Starting the contorller > > USB XHCI 1.00 > > scanning bug xhci_pci for devices... Unexpected XHCI event TRB, Skipping > > 6a0 000000004 01000000 01008401) > > That output looks like U-Boot output, before FreeBSD's UEFI loader > has been loaded. (I'd be more sure if there was more context.) Of > course the RPi* firmware and .dtb starts being involved before > U-Boot starts and, so, is involved. > > I actually use my own U-Boot build, in part because some of my USB3 > boot media require something like a usb_pgood_delay for U-Boot to > tolerate them. My in-use build is based on 2023.01 : > > # strings /boot/efi/u-boot.bin.2023.01.arm64 | grep "U-Boot 20" > U-Boot 2023.01 (Feb 06 2023 - 08:06:49 +0000) > > (My config.txt references that name.) > > So, the later material below is not based on the same U-Boot that > you are using. > > > --------------- > > The original author seems to have abandoned the project, so I forked a > copy from the ports archive. You can find it here: > https://github.com/FreeBSD-Ask/rpi3-psci-monitor and > https://github.com/FreeBSD-Ask/freebsd-ports/tree/main/sysutils/rpi-firmware > > I don't understand programming very well. Can someone help me with this > problem? > > > > Additionally, the author of raspberrypi-userland (who is the same person > as the firmware's port author) has also deleted the project. There is > currently no upstream for this project > > > > The current Raspberry Pi 4B 8GB version has issues with booting. The > current u-boot booting process gets stuck at the rainbow screen.see also > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272792 > > If someone could provide assistance, I would be very grateful. > > > > I'm not sure if the upstream has made any fixes for this issue. > > > > I expect that you may not be using an officially tagged release > but instead are using a development version of the RPi* firmware. > I avoid the development versions when I can. > > I had no trouble with the firmware-1.20230405 materials, the > most recent tagged release available. The RPi4B context is > the 8 GiByte Rev 1.5 with the "C0T" part number label on the > top of the SOC. > > The tagged versions are available via: > > https://github.com/raspberrypi/firmware/tags/ > > The most recent there is: > > https://github.com/raspberrypi/firmware/releases/tag/1.20230405/ > > I downloaded: > > https://github.com/raspberrypi/firmware/archive/refs/tags/1.20230405.tar.gz > > and did: > > # tar -xf 1.20230405.tar.gz firmware-1.20230405/boot/ > firmware-1.20230405/README.md > # rm ~/firmware-1.20230405/boot/kernel*.img > > to extract the relvent material. > > I updated one of the RPi4B USB3 boot media to have this firmware > (and .dtb's) in its msdosfs file system. > > It booted the 8 GiByte RPi4B Rev 1.5 just fine (based, in > part, on my U-Boot build, however). > > The media I picked to test with has not had its FreeBSD updated > in a while: > > # uname -apKU > FreeBSD CA72_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #90 > main-n261544-cee09bda03c8-dirty: Wed Mar 15 20:25:49 PDT 2023 > root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 > arm64 aarch64 1400082 1400082 > > === > Mark Millard > marklmi at yahoo.com > > [-- Attachment #2 --] <div dir="auto"><div>In <a href="https://github.com/FreeBSD-Ask/freebsd-ports/tree/main/sysutils/rpi-firmware">https://github.com/FreeBSD-Ask/freebsd-ports/tree/main/sysutils/rpi-firmware</a>; we are indeed using the same version of Raspberry Pi firmware i.e. 1.20230405, I am using freebsd 13.2 release of u-boot, which one are you using?<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Mark Millard <<a href="mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> 于 2023年7月30日周日 上午2:07写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Jul 29, 2023, at 09:23, ykla <<a href="mailto:yklaxds@gmail.com" target="_blank" rel="noreferrer">yklaxds@gmail.com</a>> wrote:<br> > <br> > Hi,<br> > However, strangely, when I replaced the rpi4-firmware in the ports with the latest version from the official Raspberry Pi source and copied it to a USB drive, the system started to loop with the following code.<br> > <br> > ---------------<br> > <br> > Net: eth0:ethernet@7d580000<br> > PCIe BRCM: link up, 5.0 Gbps x1 (SSC)<br> > starting USB……<br> > Bus xhci_pci:Reglster 58000420 NbrPorts 5<br> > Starting the contorller<br> > USB XHCI 1.00<br> > scanning bug xhci_pci for devices... Unexpected XHCI event TRB, Skipping<br> > 6a0 000000004 01000000 01008401)<br> <br> That output looks like U-Boot output, before FreeBSD's UEFI loader<br> has been loaded. (I'd be more sure if there was more context.) Of<br> course the RPi* firmware and .dtb starts being involved before<br> U-Boot starts and, so, is involved.<br> <br> I actually use my own U-Boot build, in part because some of my USB3<br> boot media require something like a usb_pgood_delay for U-Boot to<br> tolerate them. My in-use build is based on 2023.01 :<br> <br> # strings /boot/efi/u-boot.bin.2023.01.arm64 | grep "U-Boot 20"<br> U-Boot 2023.01 (Feb 06 2023 - 08:06:49 +0000)<br> <br> (My config.txt references that name.)<br> <br> So, the later material below is not based on the same U-Boot that<br> you are using.<br> <br> > ---------------<br> > The original author seems to have abandoned the project, so I forked a copy from the ports archive. You can find it here: <a href="https://github.com/FreeBSD-Ask/rpi3-psci-monitor" rel="noreferrer noreferrer" target="_blank">https://github.com/FreeBSD-Ask/rpi3-psci-monitor</a>; and <a href="https://github.com/FreeBSD-Ask/freebsd-ports/tree/main/sysutils/rpi-firmware" rel="noreferrer noreferrer" target="_blank">https://github.com/FreeBSD-Ask/freebsd-ports/tree/main/sysutils/rpi-firmware</a><br>; > I don't understand programming very well. Can someone help me with this problem?<br> > <br> > Additionally, the author of raspberrypi-userland (who is the same person as the firmware's port author) has also deleted the project. There is currently no upstream for this project<br> > <br> > The current Raspberry Pi 4B 8GB version has issues with booting. The current u-boot booting process gets stuck at the rainbow screen.see also <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272792" rel="noreferrer noreferrer" target="_blank">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272792</a><br>; > If someone could provide assistance, I would be very grateful.<br> > <br> > I'm not sure if the upstream has made any fixes for this issue.<br> > <br> <br> I expect that you may not be using an officially tagged release<br> but instead are using a development version of the RPi* firmware.<br> I avoid the development versions when I can.<br> <br> I had no trouble with the firmware-1.20230405 materials, the<br> most recent tagged release available. The RPi4B context is<br> the 8 GiByte Rev 1.5 with the "C0T" part number label on the<br> top of the SOC.<br> <br> The tagged versions are available via:<br> <br> <a href="https://github.com/raspberrypi/firmware/tags/" rel="noreferrer noreferrer" target="_blank">https://github.com/raspberrypi/firmware/tags/</a><br>; <br> The most recent there is:<br> <br> <a href="https://github.com/raspberrypi/firmware/releases/tag/1.20230405/" rel="noreferrer noreferrer" target="_blank">https://github.com/raspberrypi/firmware/releases/tag/1.20230405/</a><br>; <br> I downloaded:<br> <br> <a href="https://github.com/raspberrypi/firmware/archive/refs/tags/1.20230405.tar.gz" rel="noreferrer noreferrer" target="_blank">https://github.com/raspberrypi/firmware/archive/refs/tags/1.20230405.tar.gz</a><br>; <br> and did:<br> <br> # tar -xf 1.20230405.tar.gz firmware-1.20230405/boot/ firmware-1.20230405/README.md<br> # rm ~/firmware-1.20230405/boot/kernel*.img<br> <br> to extract the relvent material.<br> <br> I updated one of the RPi4B USB3 boot media to have this firmware<br> (and .dtb's) in its msdosfs file system.<br> <br> It booted the 8 GiByte RPi4B Rev 1.5 just fine (based, in<br> part, on my U-Boot build, however).<br> <br> The media I picked to test with has not had its FreeBSD updated<br> in a while:<br> <br> # uname -apKU<br> FreeBSD CA72_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #90 main-n261544-cee09bda03c8-dirty: Wed Mar 15 20:25:49 PDT 2023 root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400082 1400082<br> <br> ===<br> Mark Millard<br> marklmi at <a href="http://yahoo.com" rel="noreferrer noreferrer" target="_blank">yahoo.com</a><br> <br> </blockquote></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BPGaYApMXqVtDrgMa2qwo6wQ7SCbR2r1sxxLyDKDv6Vi2YFmw>