raspberrypi / firmware

This repository contains pre-compiled binaries of the current Raspberry Pi kernel and modules, userspace libraries, and bootloader/GPU firmware.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

rpi400 boot regression

nullr0ute opened this issue · comments

When booting the RPi 400 on Fedora with U-Boot we're seeing a regression with commit 2a1e5bf (the bump to 6.6 kernel). The regression is very early as I don't see any U-Boot output on serial console. The issue is still there with the last time the firmware was updated with commit dc94391 (Feb 29th). Not seeing the issue with RPi4B (4Gb rev1.1, 8Gb rev1.4).

Do you have an issue with latest firmware?
Three was a uboot related fix(*) a few weeks back

See: #1868

(*) I believe technically the issue was in uboot rather than firmware, and was fixed in uboot v2024.04.

Do you have an issue with latest firmware?

Yes.

Three was a uboot related fix(*) a few weeks back

The RPi4B works fine with the latest U-Boto, the RPi400 does not.

(*) I believe technically the issue was in uboot rather than firmware, and was fixed in uboot v2024.04.

Possibly, but if I change the firmware from 93d3f79 to 2a1e5bf without changing anything else the rpi400 stops booting. Neither b208f8c (Feb 14th) nor dc94391 (Feb 29th) work either.

The RPi4Bs (4Gb rev1.1, 8Gb rev1.4) work with the later Feb 14th+ firmwares, but the rpi400 does not.

Going to play around with uart_2ndstage=1 from one of the comments on that other bug.

When booting the RPi 400 on Fedora with U-Boot we're seeing a regression with commit 2a1e5bf (the bump to 6.6 kernel).

Just to confirm - are you just using the firmware (start*.elf/fixup*.dat) from that repo and not other files (the pre-built kernel/device trees etc)?

When booting the RPi 400 on Fedora with U-Boot we're seeing a regression with commit 2a1e5bf (the bump to 6.6 kernel).

Just to confirm - are you just using the firmware (start*.elf/fixup*.dat) from that repo and not other files (the pre-built kernel/device trees etc)?

No, we're also using the DT, U-Boot will load the Linux DT for kernel by default but we're not even getting to U-Boot to do that.

Can you confirm if updating the firmware (start*.elf/fixup*.dat) or other files (dtbs or anything else) caused the issue?