[opensuse-arm] Tumbleweed on Raspberry Pi 400
Hi folks, I've just got a Raspberry Pi 400 (https://www.raspberrypi.org/products/raspberry-pi-400/), which is essentially a Raspberry Pi 4 built into a keyboard. I've attempted to boot the 20201111 Tumbleweed snapshot (http://download.opensuse.org/ports/aarch64/tumbleweed/appliances/openSUSE-Tu...) on it but seem to run into some issues. I've hooked up to the serial console to capture some output of boot attempts. Without HDMI detached, I get the following output and then the device hangs: U-Boot 2020.10 (Oct 14 2020 - 09:48:25 +0000) DRAM: 3.9 GiB RPI: Board rev 0x13 outside known range RPI Unknown model (0xc03130) MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0 Loading Environment from FAT... ** No partition table - mmc 0 ** In: serial Out: serial Err: serial Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ERROR : memory not allocated With HDMI attached, I get the following output and then the device reboots: U-Boot 2020.10 (Oct 14 2020 - 09:48:25 +0000) DRAM: 3.9 GiB RPI: Board rev 0x13 outside known range RPI Unknown model (0xc03130) MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0 Loading Environment from FAT... ** No partition table - mmc 0 ** In: serial Out: vidconsole Err: vidconsole Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device "Synchronous Abort" handler, esr 0x96000044 elr: 000000000009c0f8 lr : 0000000000091e30 (reloc) elr: 000000003df6c0f8 lr : 000000003df61e30 x0 : 000000003dbdd880 x1 : 000000003dbdd800 x2 : 7473696c70766564 x3 : 000000003dfd1da0 x4 : 000000003dbdd890 x5 : 000000000000005c x6 : 000000003dfd1da0 x7 : 0000000000000000 x8 : fffffffffffffff0 x9 : 0000000000000008 x10: 00000000ffffffd0 x11: 000000000000000a x12: 0000000000000006 x13: 000000000001869f x14: 000000003db3fd30 x15: 0000000000000002 x16: 000000003df6e23c x17: 0000000000000000 x18: 000000003db4bd90 x19: 0000000000000020 x20: 000000003dfd17e0 x21: 000000003dbdee90 x22: 000000000000000b x23: 00000000ffffffff x24: 0000000000000001 x25: 000000003dfe3854 x26: 000000003dfbd687 x27: 000000003dfc6092 x28: 000000000000003b x29: 000000003db3ede0 Code: b2400021 f9000481 f9400c01 f8410c02 (f9000c41) Resetting CPU ... resetting ... I've not had to debug something like this before, so if anyone has any pointers, that would be helpful. I'm also happy to provide any additional output/try other things to help others debug. Thanks, James
Hi James, On Mon, 2020-11-16 at 09:54 +0000, James Wheatley wrote:
Hi folks,
I've just got a Raspberry Pi 400 (https://www.raspberrypi.org/products/raspberry-pi-400/), which is essentially a Raspberry Pi 4 built into a keyboard. I've attempted to boot the 20201111 Tumbleweed snapshot (http://download.opensuse.org/ports/aarch64/tumbleweed/appliances/openSUSE-Tu...) on it but seem to run into some issues. I've hooked up to the serial console to capture some output of boot attempts. Without HDMI detached, I get the following output and then the device hangs:
U-Boot 2020.10 (Oct 14 2020 - 09:48:25 +0000)
DRAM: 3.9 GiB RPI: Board rev 0x13 outside known range RPI Unknown model (0xc03130) MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0 Loading Environment from FAT... ** No partition table - mmc 0 ** In: serial Out: serial Err: serial Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ERROR : memory not allocated
With HDMI attached, I get the following output and then the device reboots:
U-Boot 2020.10 (Oct 14 2020 - 09:48:25 +0000)
DRAM: 3.9 GiB RPI: Board rev 0x13 outside known range RPI Unknown model (0xc03130) MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0 Loading Environment from FAT... ** No partition table - mmc 0 ** In: serial Out: vidconsole Err: vidconsole Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device "Synchronous Abort" handler, esr 0x96000044 elr: 000000000009c0f8 lr : 0000000000091e30 (reloc) elr: 000000003df6c0f8 lr : 000000003df61e30 x0 : 000000003dbdd880 x1 : 000000003dbdd800 x2 : 7473696c70766564 x3 : 000000003dfd1da0 x4 : 000000003dbdd890 x5 : 000000000000005c x6 : 000000003dfd1da0 x7 : 0000000000000000 x8 : fffffffffffffff0 x9 : 0000000000000008 x10: 00000000ffffffd0 x11: 000000000000000a x12: 0000000000000006 x13: 000000000001869f x14: 000000003db3fd30 x15: 0000000000000002 x16: 000000003df6e23c x17: 0000000000000000 x18: 000000003db4bd90 x19: 0000000000000020 x20: 000000003dfd17e0 x21: 000000003dbdee90 x22: 000000000000000b x23: 00000000ffffffff x24: 0000000000000001 x25: 000000003dfe3854 x26: 000000003dfbd687 x27: 000000003dfc6092 x28: 000000000000003b x29: 000000003db3ede0
Code: b2400021 f9000481 f9400c01 f8410c02 (f9000c41) Resetting CPU ...
resetting ...
I've not had to debug something like this before, so if anyone has any pointers, that would be helpful. I'm also happy to provide any additional output/try other things to help others debug.
It's a known issue and which I'm trying to fix at the moment. In the meantime, as a workaround, you can replace the 'u-boot.bin' file in your SD's EFI partition with the one I attached. The board should boot alright. Feel free to contact me if it doesn't. Regards, Nicolas
participants (2)
-
James Wheatley -
Nicolas Saenz Julienne