bug_report template: Be more precise about the UART pins

Increase the delays to compensate for an (unlikely) retry loop
if flashrom reports an error.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -80,7 +80,7 @@ body:
   attributes:
     label: Bootloader logs
     description: |
-       If the problem can't be diagnosed from the bootloader HDMI diagnostics screen then we'll normally need to see more detailed logs to diagnose the problem. The bootloader and GPU firmware can be configured to enable log output to the UART pins `14` and `15` on the [40-pin GPIO header](https://www.raspberrypi.com/documentation/computers/os.html#gpio-and-the-40-pin-header)
+       If the problem can't be diagnosed from the bootloader HDMI diagnostics screen then we'll normally need to see more detailed logs to diagnose the problem. The bootloader and GPU firmware can be configured to enable log output to the UART (GPIOs `14` and `15`, pins `8` and `10` on the [40-pin GPIO header](https://www.raspberrypi.com/documentation/computers/os.html#gpio-and-the-40-pin-header, or on the Debug header on a Pi 5)
          * To enable UART logging from the bootloader specify [BOOT_UART=1](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_UART) in the EEPROM config
          * To enable UART logging from the `start.elf` GPU firmware stage add [uart_2ndstage=1](https://www.raspberrypi.com/documentation/computers/config_txt.html#uart_2ndstage) to `config.txt`.
          * If you are familiar with using Wireshark then it's also possible to use [NETCONSOLE](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#NETCONSOLE) write logs to UDP packets.

README.md

@@ -11,5 +11,5 @@ To reset the bootloader back to factory defaults use [Raspberry Pi Imager](https
 * [Config.txt boot options](https://www.raspberrypi.com/documentation/computers/config_txt.html#boot-options)
 * [Bootloader EEPROM](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-boot-eeprom)
 * [Bootloader configuration](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-bootloader-configuration)
-* [Updating the Compute Module 4 bootloader](https://www.raspberrypi.com/documentation/computers/compute-module.html#cm4bootloader)
+* [Updating the Compute Module 4 bootloader](https://www.raspberrypi.com/documentation/computers/compute-module.html#update-the-compute-module-bootloader)
 * [Releases and release notes](releases.md)

firmware-2711/old/critical/pieeprom-2020-04-16.bin

@@ -1 +0,0 @@
-../beta/pieeprom-2020-04-16.bin

firmware-2711/old/critical/vl805-000137ad.bin

@@ -1 +0,0 @@
-../beta/vl805-000137ad.bin

firmware-2711/old/stable/pieeprom-2020-04-16.bin

@@ -1 +0,0 @@
-../beta/pieeprom-2020-04-16.bin

firmware-2711/old/stable/vl805-000137ad.bin

@@ -1 +0,0 @@
-../beta/vl805-000137ad.bin

firmware-2711/release-notes.md

@@ -1,9 +1,58 @@
 # Raspberry Pi4 bootloader EEPROM release notes
 
+## 2024-12-07: Enable banklow (and so NUMA) by default (latest)
+
+* Enable banklow (and so NUMA) by default
+  banklow=1 (2712) and banklow=3 (2711) give the best performance.
+
+## 2024-10-21: Fix PCIe BAR issue for some switches  (latest)
+
+* Boot-menu improvements
+  Remain in the forced boot mode until the menu is used to select a different
+  boot-mode or reset to the original boot-order.
+
+## 2024-10-10: Use soft-reset to preseve SDRAM contents after ramoops (latest)
+
+* SD card high-speed/low-voltage mode can only be exited by powercycling.
+  Pi 4s before rev 1.4 lack the power switch required to do this, so must
+  resort to a global reset that turns off many things, including SDRAM.
+
+  To ensure correct operation, the bootloader checks that the SD I/O
+  voltage is the expected 3.3V, forcing a power cycle if it isn't.
+  However, this doesn't take advantage of presence of the dedicated SD
+  power switch, always forcing a global reset, a consequence of which can
+  be the loss of SDRAM content - including any ramoops dump of the crash
+  logs.
+
+  Make the bootloader more SD_PWR_ON aware, only triggering a global reset
+  if one isn't found.
+  See: https://github.com/raspberrypi/linux/issues/5298
+* Remove requirement for GPT ptable array  to be at LBA-2
+  See: https://github.com/raspberrypi/rpi-eeprom/issues/585
+* Introduce a new boot-menu feature where pressing SPACE at power on
+  gives the user a one-shot option to select a different boot mode.
+  e.g. Select USB boot if the default SD card is corrupted or unavailable.
+* Display the bootloader network-install UI for longer on a cold boot to make
+  this feature more visible to first time users.
+  To revert to the previous behaviour remove NET_INSTALL_AT_POWER_ON=1
+  from the bootloader config.
+* Default to 2GB start for PCI bus addresses on 2711 and 2712
+  This change also constrains the window size to 2GB, so all PCI bus address
+  assignments fall below 4GB, avoiding a potential bug with 32-bit BARs in
+  esoteric bus topologies (e.g. lots of GPUs).
+
+## 2024-09-05: Fix self-update if EEPROM is write-protected (latest)
+* arm_dt: Consult the hat_map for all HATs
+* USB boot - ignore RP2 / RP3 MSD device in BOOTSEL mode.
+* recovery.bin - Fix erase_eeprom to not block reboot_recovery
+* Fix self-update to continue to boot instead of retrying forever
+  if the EEPROM is write protected.
+  https://github.com/raspberrypi/rpi-eeprom/issues/597
+
 ## 2024-08-14 (recovery.bin) -  Add support for OTP metadata (latest)
 * Update to recovery.bin to output metadata about OTP during rpiboot
 
-## 2024-07-30 - USB boot fixes for CM4-S and interop improvments (latest)
+## 2024-07-30 - USB boot fixes for CM4-S and interop improvements (latest)
   * Resolve USB boot regression in 2024-04-17 relase on CM4S
     See https://github.com/raspberrypi/rpi-eeprom/issues/588
   * Improve compatibility for booting from some USB SD card readers