Raspberry PI 400 does not boot #109
Comments
nsa666666
changed the title
|
i let it run for a while on the green cursor (i didnt keep track of how long) and it suddenly started booting (at least the UEFI part). ill give it a bootable AARCH64 OS (Linux-based) and report if it boots. if it boots, ill let my other system log the UART for debugging i did update the DTBs, start4.elf and fixup4.dat from the current (as of writing) commit from the Raspberry PI repo |
|
it took around 60 min to start, and it rebooted around the time it normally started booting the OS |
|
@jeroenbrons after it booted, all the things worked like on the pi 4 b? |
|
no, it got back to the raspi rainbow-boot screen and the green cursor |
|
Seems to be some watchdog timer. It does not realy boot. |
|
Still not booting correctly here on the v1.21 release. It sits on the green cursor like everyone else reported for ~25 seconds, and then shows the UEFI splash screen. USB is never activated, so not able to boot past this point or enter into the UEFI menu. After the 5-second countdown on the splash screen, the whole device reboots. Tested with 2 different SD cards, same results. Both tested on a Pi4-4GB, and it entered UEFI instantly with USB working there. |
|
i compiled a debug-binary without XHCI to test (because it stalls for a while there), keyboard doesnt work, but i can get into the menu with the UART (al least with aforementioned custom build) however, USB2 doesnt work either |
|
It is at least some improvemend. It comes to the UEFI splash screen, but keyboard does not work and then it just reboots. |
|
@jeroenbrons an USB-C OTG adapter should work. |
|
I have a similar issue on Pi4-8GB. USB Keyboard input is ignored at the splash screen. The same SDcard and keyboards (I've tried several) work fine if the SDcard is reimaged with stock pi OS. |
RIGHT! I always forget that the Pi's power port is OTG! I tried that just now. Obviously, still has the ~25 second stall out, but was able to get it to somewhat boot from USB, and have a working external keyboard. The 1800MHz clock speed is recognized. However, the 4GB of RAM is wonky. UEFI reports it in menu, but only shows 3GB to the OS. I know this is normal and usually configurable, however, the configuration option is inaccessible on this board. The Pi 400 also shows up as "Unknown Raspberry Pi Model"
|
|
i am also affected by this bug. my rpi-400 boots to uefi raspberry pi logo but can't enter setup as the keyboard does not respond. so it just keeps rebooting. |
To clarify. This is not a bug. This is new HW bringup/support. The RPi 400 has a newer SoCs revision than the RPi4, and requires changes to how the UEFI FW initializes the PCIe and XHCI subsystems for it to work properly |
|
ok sorry and thanks for the explanation! |
|
@andreiw made some progress and reported an issue in the RPi FW raspberrypi/firmware#1495 . Adding here to link the two issues |
Could it happens that my Rpi4 8GB be using a new SoC revition too? |
|
Yes it is possible that the new SoC revision is being used in some newer RPi4 models, in addition to the CM4 and RPi400. |
|
thanks for replying @samerhaj |
In fact, it's not just possible, but pretty much confirmed. http://www.raspberry-pi-case.com/pictures/rpi4b/RPi4B_8GB.jpg The text on the die isn't readable, but the location of the corner dot matches the CM4 and 400. Unless Broadcom is making B0 silicon with the new markings specifically for the "plain" Pi 4, this is C0 silicon. Note that the 3GB PCIE address space bug (and possibly also the 64-bit addressing bug) is fixed in the C0 revision, so PCIE can actually access the whole 8GB address space now. The 1GB limit still applies to legacy BCM2835 peripherals. |
So I guess that when this be fixed for CM4 and 400 It will be also fixed for new 4 8gb models right? |
|
And Now I'm not sure what to think. https://pbs.twimg.com/media/EZ1FLZcVAAIZ5V4.jpg:orig This is clearly the new marking style on the chip, but it's marked 2711ZPKFSB06B0T. So, either Broadcom is in fact still producing B0 silicon alongside the newer C0 (to ensure full backwards compatibility?), or the Pi Foundation treated the "B0T" as part of the serial number, and asked for "B0T" markings for all chips to be installed on Model B boards, regardless of actual silicon revision. |
|
Well, but what about Raspberry PI 400 not booting with UEFI bios? Still an unsolved issue ... any progress on that? |
|
I think we are waiting on: raspberrypi/firmware#1518 (comment) |
|
as weird as it may sounds, removing the line "gpu_mem=16" worked for me |
from where did you remove that? And what does work for you now? |
|
i couldn't find a line "gpu_mem=16" (or any other gpu_mem line), but it started trying to PXE-boot (there was no ARM64-UEFI bootable device attached, i will try with one soon) |
well, in every youtube video i found, they are suggesting to add this line at the end of config.txt to "improve" memory usage |
|
i put the current ZIP in the boot-partition of a Windows-on-Raspberrypi SD-card and let it run, it boots (my PI400 is running the sysprep phase as i'm writing this). i will report back whether it completes the setup. |
|
It actually boots! But USB and Keyboard does not work. |
The UEFI-Firmware does not boot on Raspberry PI 400. It shows only a green dash on screen.
Here is the boot log:
The text was updated successfully, but these errors were encountered: