Alastair Cota

From past experience, if a Watchdog Timer is throwing more errors than it solves, it should be switched off and a redundant always-on machine or dedicated power management circuit should...

The Watchdog Timeout can be considered like setting an Alarm Clock, of which there are Raspberry Pi EEPROM/Firmware settings to set the values for: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#DHCP_TIMEOUT As for the priority levels,...

https://github.com/tianocore/edk2-non-osi/blob/master/Platform/RaspberryPi/Drivers/LogoDxe/Logo.bmp

It can be changed but UEFI in its current state needs recompiling after you change it in the repository. I have changed mine in this way. In the RPI_EFI.fd archive...

The Pi usually boots from one of 3 places: 0x80000 (Aarch64 kernel EL2), 0x8000 (Aarch32 kernel) or 0x0 (armstub EL3). You can specify where it starts from in config.txt with...

It will still need to boot from address 0x0. Have you tried a sequence of `fatload`, `nm` and `go` for that? All the Pi has to do is a single...

It would be something like what's written on this page to fill memory from 0x0 with RPI_EFI.fd before branching to it: https://www.denx.de/wiki/DULG/UBootCmdGroupMemory A better approach may be to branch from...

Branching/Jumping/Calling changes the address of the next instruction (with optional `link` to specify an address to `return` to). This is address 0x0 for when RPI_EFI.fd is loaded (copied) to address...

https://github.com/raspberrypi/windows-drivers/tree/master/drivers/gpio/bcm2836 - This is the driver for GPIO, and https://github.com/raspberrypi/windows-drivers/tree/master/drivers/i2c/bcm2836 - This is the driver for I2C for HATS. Most of this predates the Pi4 by a couple of generations...

The only adjustments in UEFI involve changing PinMux routing to a known state at boot, nothing that can't be then changed at runtime within the OS. Debian being Linux-based also...