Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b
Hey, On Fri, 2023-01-06 at 16:36 +0100, Andreas Henriksson wrote: > On Tue, Jan 03, 2023 at 11:56:51PM +0100, Andreas Henriksson wrote: > > On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote: > > > On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian > > > wrote: > > > > rpi_4 > > > > rpi_4_32b > [...] > > Hello again, > > While I only have the earliest rpi 4B rev A0 (1.1) it has come to > my attention that apparently there's a revision C0 (1.4) that > has problems booting with u-boot. > > Apparently in 1.4 revision they changed the hardware in > an incompatible way and then cover this up by having the > proprietary firmware modify the dtb in ram to change nodes > as needed. Yes that revision has a newer version of the SoC same/similar as in the rpi 400 > The issue has been discussed on the rpi forums: > https://forums.raspberrypi.com/viewtopic.php?t=315662 > > There has been seemingly two indenpendent attempts at submitting > (very similar) patches upstream to adress this in u-boot: > https://lists.denx.de/pipermail/u-boot/2021-November/468322.html > https://lists.denx.de/pipermail/u-boot/2021-September/462020.html > ... but apparently they've never been merged. Fwiw this came up on the u-boot list again today: https://lists.denx.de/pipermail/u-boot/2023-January/504038.html Lets see if things move forward this year.. Fwiw the latest upstream attempt i saw was Antoine's patch series: https://lists.denx.de/pipermail/u-boot/2022-August/491455.html Which resent my patch + added some additional tweaks. > > NixOS are carrying patches: > https://github.com/NixOS/nixpkgs/tree/master/pkgs/misc/uboot > which includes some revision of Sjoerds patch. > > Some info on board revisions can be found at: > https://www.raspberrypi-spy.co.uk/2012/09/checking-your-raspberry-pi-board-version/ > > This issue probably deserves it's own separate bug report, > but since I don't have the hardware in question I'm leaving that > to who ever else cares and just share the info I have. > > It might be useful to consider just include NixOS/Sjoerds patch > or documenting that RPi 4B hw rev 1.4 will not work. > (Hardware revision is visible in /proc/cpuinfo under the Revision: > field.) > However it maybe best trying to find someone who has the affected > hardware revision that can confirm the problem exists and that > the patch actually resolves it. I can confirm both the problem and the patch solving it :) -- Sjoerd Simons
Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b
On Tue, Jan 03, 2023 at 11:56:51PM +0100, Andreas Henriksson wrote: > On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote: > > On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote: > > > rpi_4 > > > rpi_4_32b [...] Hello again, While I only have the earliest rpi 4B rev A0 (1.1) it has come to my attention that apparently there's a revision C0 (1.4) that has problems booting with u-boot. Apparently in 1.4 revision they changed the hardware in an incompatible way and then cover this up by having the proprietary firmware modify the dtb in ram to change nodes as needed. The issue has been discussed on the rpi forums: https://forums.raspberrypi.com/viewtopic.php?t=315662 There has been seemingly two indenpendent attempts at submitting (very similar) patches upstream to adress this in u-boot: https://lists.denx.de/pipermail/u-boot/2021-November/468322.html https://lists.denx.de/pipermail/u-boot/2021-September/462020.html ... but apparently they've never been merged. NixOS are carrying patches: https://github.com/NixOS/nixpkgs/tree/master/pkgs/misc/uboot which includes some revision of Sjoerds patch. Some info on board revisions can be found at: https://www.raspberrypi-spy.co.uk/2012/09/checking-your-raspberry-pi-board-version/ This issue probably deserves it's own separate bug report, but since I don't have the hardware in question I'm leaving that to who ever else cares and just share the info I have. It might be useful to consider just include NixOS/Sjoerds patch or documenting that RPi 4B hw rev 1.4 will not work. (Hardware revision is visible in /proc/cpuinfo under the Revision: field.) However it maybe best trying to find someone who has the affected hardware revision that can confirm the problem exists and that the patch actually resolves it. Regards, Andreas Henriksson
Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b
On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote: > On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote: > > rpi_4 > > rpi_4_32b > > I dug up my old dusty rpi4 which I probably haven't touched > since last time we spoke about u-boot on it. > > > I've tested only the 64bit (arm64) version so far. [...] > I upgraded only u-boot.bin from bookworm/sid/experimental [...] > The unstable and experimental versions both caused a reset > after run bootcmd and before "Starting Linux...". [...] After upgrading rpi firmware files to latest release/tag also the unstable and experimental u-boot seemed to boot fine (no reset, garbage on console after linux started). ### unstable u-boot with rpi firmware-1.20221104.tar.gz U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +) DRAM: 3.9 GiB RPI 4 Model B (0xc03111) Core: 209 devices, 16 uclasses, devicetree: board MMC: mmcnr@7e30: 1, mmc@7e34: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In:serial Out: serial Err: serial Net: eth0: ethernet@7d58 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 U-Boot> U-Boot> U-Boot> U-Boot> U-Boot> U-Boot> U-Boot> U-Boot> run bootcmd switch to partitions #0, OK mmc0 is current device Scanning mmc 0:2... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf U-Boot menu 1: Debian GNU/Linux 5.7.0-1-arm64 2: Debian GNU/Linux 5.7.0-1-arm64 (rescue target) Enter choice: 1:Debian GNU/Linux 5.7.0-1-arm64 Retrieving file: /boot/initrd.img-5.7.0-1-arm64 Retrieving file: /boot/vmlinuz-5.7.0-1-arm64 append: root=LABEL=root ro rootwait console=ttyS1,115200 Retrieving file: /usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260896e Starting kernel ... [... garbage characters...] ### experimental u-boot with rpi firmware-1.20221104.tar.gz U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +) DRAM: 948 MiB (effective 3.9 GiB) RPI 4 Model B (0xc03111) Core: 209 devices, 16 uclasses, devicetree: board MMC: mmcnr@7e30: 1, mmc@7e34: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In:serial Out: serial Err: serial Net: eth0: ethernet@7d58 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 U-Boot> U-Boot> U-Boot> U-Boot> run bootcmd switch to partitions #0, OK mmc0 is current device Scanning mmc 0:2... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf U-Boot menu 1: Debian GNU/Linux 5.7.0-1-arm64 2: Debian GNU/Linux 5.7.0-1-arm64 (rescue target) Enter choice: 1:Debian GNU/Linux 5.7.0-1-arm64 Retrieving file: /boot/initrd.img-5.7.0-1-arm64 Retrieving file: /boot/vmlinuz-5.7.0-1-arm64 append: root=LABEL=root ro rootwait console=ttyS1,115200 Retrieving file: /usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Working FDT set to 260 Using Device Tree in place at 0260, end 0260896e Working FDT set to 260 Starting kernel ... [...garbage characters...] Regards, Andreas Henriksson
Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b
On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote: > rpi_4 > rpi_4_32b I dug up my old dusty rpi4 which I probably haven't touched since last time we spoke about u-boot on it. I've tested only the 64bit (arm64) version so far. The version that was on the sd-card since last time: U-Boot> ver U-Boot 2020.07+dfsg-1 (Jul 08 2020 - 23:29:02 +) gcc (Debian 9.3.0-14) 9.3.0 GNU ld (GNU Binutils for Debian) 2.34.90.20200706 U-Boot> I upgraded only u-boot.bin from bookworm/sid/experimental on the firmware partition (nothing else touched, and I'm not really sure what state it was in since last time but probably a bootable system atleast). Testing/bookworm u-boot.bin seems to boot fine (although serial console became garbage after Linux started, but it seemed to run but I didn't investigate much). The unstable and experimental versions both caused a reset after run bootcmd and before "Starting Linux...". U-Boot itself seemed to run fine though, it was running bootcmd that caused the reset. Maybe I need to upgrade the rpi firmware, or maybe it's related to what else is on the old sd-card that was in the box. # testing u-boot U-Boot> ver U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +) gcc (Debian 11.3.0-1) 11.3.0 GNU ld (GNU Binutils for Debian) 2.38 U-Boot> # unstable u-boot U-Boot> ver U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +) gcc (Debian 12.2.0-10) 12.2.0 GNU ld (GNU Binutils for Debian) 2.39.50.20221208 U-Boot> U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +) DRAM: 3.9 GiB RPI 4 Model B (0xc03111) Core: 135 devices, 14 uclasses, devicetree: board MMC: mmcnr@7e30: 1, emmc2@7e34: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In:serial Out: serial Err: serial Net: eth0: genet@7d58 PCIe BRCM: link up, 5.0 Gbps x1 (!SSC) starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller Port not available. Hit any key to stop autoboot: 0 "Synchronous Abort" handler, esr 0x9644 elr: 0009f3a8 lr : 0009572c (reloc) elr: 3b36c3a8 lr : 3b36272c x0 : 3af52610 x1 : 3af52680 x2 : 0051 x3 : 6964003b6963765f x4 : 3b3d0890 x5 : 3b3d0890 x6 : 005b x7 : 3b3d0e30 x8 : 3b3d0820 x9 : 0008 x10: fff0 x11: 0006 x12: 0001869f x13: 3af3e708 x14: 3af3e810 x15: x16: 3b36d548 x17: 596fcb0297bbddff x18: 3af48d70 x19: 0071 x20: 3b3d0880 x21: x22: 0005 x23: 000a x24: 0001 x25: 3b3e4cd8 x26: x27: 3b3c4851 x28: 006d x29: 3af3d9e0 Code: a9410803 8b130001 b2400273 f9000413 (f9000c62) Resetting CPU ... resetting ... # experimental u-boot U-Boot> ver U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +) gcc (Debian 12.2.0-10) 12.2.0 GNU ld (GNU Binutils for Debian) 2.39.50.20221208 U-Boot> U-Boot> run bootcmd "Synchronous Abort" handler, esr 0x9644 elr: 0009f7e0 lr : 00095e0c (reloc) elr: 3b36c7e0 lr : 3b362e0c x0 : 3af59470 x1 : 3af59490 x2 : 30636d6d x3 : 5f646d63746f6f00 x4 : 0070 x5 : 3b3d0e08 x6 : 005b x7 : 3b3d13a8 x8 : 0050 x9 : 0008 x10: fff0 x11: 0006 x12: 0001869f x13: 3af3e708 x14: 3af3e810 x15: x16: 3b36d994 x17: d9ff4b22fffbdcff x18: 3af48d70 x19: 0021 x20: 3b3d0df8 x21: 3af59d80 x22: 3af59b20 x23: 0010 x24: 0008 x25: 3b3e5258 x26: 0002 x27: 3b3c4e54 x28: 0073 x29: 3af3da10 Code: a9410803 8b130001 b2400273 f9000413 (f9000c62) Resetting CPU ... resetting ... U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +) [...]
Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b
On 2022-12-28, Vagrant Cascadian wrote: > On 2022-12-22, Vagrant Cascadian wrote: >> On 2022-08-20, Vagrant Cascadian wrote: >>> On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status > > I have not received many test results for current or even remotely > recent u-boot platforms in Debian, and u-boot has been blocked from > migration to testing partly because of this. > > As the bookworm freeze approaches, this is getting to be... worrysome! > > If you have access to any of these boards, please consider testing > u-boot versions as packaged in debian for versions from debian stable > (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental > (2023.01-rc*) and updating the wiki page if successful and/or replying > to 1016...@bugs.debian.org with a positive confirmation... > > ...and if not successful, filing bugs against the relevent u-boot-* > packages and marking them as blocking 1016963. rpi_4 rpi_4_32b live well, vagrant signature.asc Description: PGP signature
