bug_report template: Be more precise about the UART pins

firmware-2712/release-notes.md

@@ -1,88 +1,5 @@
 # Raspberry Pi5 bootloader EEPROM release notes
 
-## 2025-01-22: Promote 2025-01-22 to default release (default)
-
-## 2025-01-22: Add DT /chosen property signed-boot boot.img hash (latest)
-
-* Add DT /chosen property signed-boot boot.img hash
-  Make the sha256 hash of the boot.img file available via
-  device-tree /proc/device-tree/chosen/bootloader/boot_img_sha256 if
-  signed boot is enabled.
-* filesystem: GPT autoboot/reboot partition number fixes for Pi4 and older
-* Fix problems when setting arm_freq_min=arm_freq and display clocks
-  if performance governor is not enabled.
-
-## 2025-01-14: Add set_reboot_order API (latest)
-
-* Add set_reboot_order API and config.txt properties
-  If set_reboot_order is defined in config.txt or set via vcmailbox
-  then this will override the bootloader config BOOT_ORDER property
-  on the next reboot. The parameter is stored in a reset safe register
-  and is cleared by the bootloader after reading it.
-  Typically, the config.txt value only be used via rpiboot to
-  override the boot-order on the next reboot. Otherwise, it should
-  reside in a conditional section so that the boot order is not
-  overridden on every reboot.
-  Example, test network boot
-  sudo vcmailbox 0x0003808b 4 4 0xf4612; sudo reboot
-
-## 2025-01-13: Improved SDRAM refresh timings for Pi5 16GB (latest)
-
-* Improved SDRAM refresh timings for Pi5 - 16GB
-* Add an option to wait for the power button to be pressed before booting.
-  If POWER_OFF_ON_HALT=1 and WAIT_FOR_POWER_BUTTON=1 in the bootloader
-  config then the bootloader will wait for either the power button
-  to be pressed or an RTC alarm before booting. The wait state
-  switches the PMIC to STANDBY mode which is the lowest possible
-  power state.
-
-## 2025-01-08: Update SDRAM refresh timings for BCM2712D0 products (latest)
-
-* Update SDRAM timings for BCM2712D0 products.
-
-## 2025-01-07: Fixup M.2 HAT+ detection (latest)
-
-* Fix a potential timing issue introduced in the 2025-01-06
-  release when enabling PCIE_PWR when booting from SD/USB.
-
-## 2025-01-06: Stop the fan after after fan-probe (latest)
-
-* Stop the fan after after fan-probe
-  After the fan-probe has completed drive the fan PWM GPIO
-  to high if a fan was detected and let the OS take over.
-* Add SD_QUIRKS for hardware bringup / workarounds
-  Add a new SD_QUIRKS flags property which can be used to
-  disable high-speed mode (bit 0). Other bits are reserved for
-  future use.
-* Change uart_2ndstage default to 1 on Pi5
-  Change the default to 1 because this gives useful diagnostics
-  for device-tree loading with minimal overhead. Set uart_2ndstage=0
-  or BOOT_UART=0 to disable this.
-* Move M.2 HAT+ detection to early boot.
-  Initialse M.2 HAT+ detection before DDR init to give NVMe
-  drive firmware more time to boot.
-
-## 2024-12-19: Disable fan PWM before shutdown (latest)
-
-* Disable fan PWM before shutdown
-  Drive the RP1 fan PWM GPIO high before entering the VPU
-  sleep (POWER_OFF_ON_HALT=0) to stop the fan spinning.
-* Disable fan PWM GPIO between RP1 init and fan probe
-  Drive fan PWM GPIO high during early boot to disable the fan
-  until it is probed during the device-tree setup stage.
-  This stops the spinning at max rpm during network-install.
-* arm_dt: enable_uart defaults to 0 on 2712
-  The default value of enable_uart on 2712 is 0, regardless of the
-  presence of the debug UART cable, so guarantee that the default is
-  always set correctly.
-
-## 2024-12-15: Add net install to boot menu (latest)
-
-* Add net install to boot menu
-  Press N (or shift).
-* enable_uart: Require enable_uart=1 to enable RP1 UART console
-  See: https://github.com/raspberrypi/rpi-eeprom/issues/643
-
 ## 2024-12-07: Enable banklow (and so NUMA) by default (latest)
 
 * Enable banklow (and so NUMA) by default

imager/make-imager-release

@@ -8,4 +8,4 @@ script_dir=$(cd "$(dirname "$0")" && pwd)
 ${script_dir}/make-release critical 2023-01-11 000138c0 "${script_dir}/2711-config" release-2711 rpi-boot-eeprom-recovery 2711
 
 # Pi5
-${script_dir}/make-release critical 2025-01-22 "" "${script_dir}/2712-config" release-2712 rpi-boot-eeprom-recovery 2712
+${script_dir}/make-release critical 2024-11-12 "" "${script_dir}/2712-config" release-2712 rpi-boot-eeprom-recovery 2712

rpi-eeprom-config

@@ -171,6 +171,8 @@ def apply_update(config, eeprom=None, config_src=None):
     sys.stdout.write("Updating bootloader EEPROM\n image: %s\nconfig_src: %s\nconfig: %s\n%s\n%s\n%s\n" %
                      (eeprom_image, config_src, config, '#' * 80, config_str, '#' * 80))
 
+    sys.stdout.write("\n*** To cancel this update run 'sudo rpi-eeprom-update -r' ***\n\n")
+
     # Ignore APT package checksums so that this doesn't fail when used
     # with EEPROMs with configs delivered outside of APT.
     # The checksums are really just a safety check for automatic updates.

rpi-eeprom-update

@@ -14,8 +14,6 @@ LOCAL_MODE=0
 if [ -n "$FIRMWARE_ROOT" ]; then
    # Provided by environment
    true
-elif [ -d /usr/lib/firmware/raspberrypi/bootloader ] || [ -d /usr/lib/firmware/raspberrypi/bootloader-2711 ] || [ -d /usr/lib/firmware/raspberrypi/bootloader-2712 ]; then
-   FIRMWARE_ROOT=/usr/lib/firmware/raspberrypi/bootloader
 elif [ -d /lib/firmware/raspberrypi/bootloader ] || [ -d /lib/firmware/raspberrypi/bootloader-2711 ] || [ -d /lib/firmware/raspberrypi/bootloader-2712 ]; then
    FIRMWARE_ROOT=/lib/firmware/raspberrypi/bootloader
 else
@@ -904,11 +902,6 @@ checkVersion()
 
    if [ "${ACTION_UPDATE_BOOTLOADER}" = 1 ] || [ "${ACTION_UPDATE_VL805}" = 1 ]; then
       echo "*** UPDATE AVAILABLE ***"
-      echo ""
-      echo "Run \"sudo rpi-eeprom-update -a\" to install this update now."
-      echo
-      echo "To configure the bootloader update policy run \"sudo ${RPI_EEPROM_UPDATE_CONFIG_TOOL}\""
-      echo ""
       printVersions
       write_status_info "EXIT_UPDATE_REQUIRED"
       exit ${EXIT_UPDATE_REQUIRED}

rpi-eeprom-update-default

@@ -1,5 +1,5 @@
 
-FIRMWARE_ROOT=/usr/lib/firmware/raspberrypi/bootloader
+FIRMWARE_ROOT=/lib/firmware/raspberrypi/bootloader
 FIRMWARE_RELEASE_STATUS="default"
 FIRMWARE_BACKUP_DIR="/var/lib/raspberrypi/bootloader/backup"
 EEPROM_CONFIG_HOOK=

test/install

@@ -20,14 +20,14 @@ CONFIG="/etc/default/rpi-eeprom-update"
 [ "$(id -u)" = "0" ] || die "$0 Must be run as root - try 'sudo $0 [-b]'"
 
 # Clear out the old firmware
-rm -rf /usr/lib/firmware/raspberrypi/bootloader
-rm -rf /usr/lib/firmware/raspberrypi/bootloader-2711
-rm -rf /usr/lib/firmware/raspberrypi/bootloader-2712
+rm -rf /lib/firmware/raspberrypi/bootloader
+rm -rf /lib/firmware/raspberrypi/bootloader-2711
+rm -rf /lib/firmware/raspberrypi/bootloader-2712
 
-mkdir -p /usr/lib/firmware/raspberrypi/bootloader-2711
-rsync -alv "${FIRMWARE_DIR}-2711"/* /usr/lib/firmware/raspberrypi/bootloader-2711 || echo "Failed"
-mkdir -p /usr/lib/firmware/raspberrypi/bootloader-2712
-rsync -alv "${FIRMWARE_DIR}-2712"/* /usr/lib/firmware/raspberrypi/bootloader-2712 || echo "Failed"
+mkdir -p /lib/firmware/raspberrypi/bootloader-2711
+rsync -alv "${FIRMWARE_DIR}-2711"/* /lib/firmware/raspberrypi/bootloader-2711 || echo "Failed"
+mkdir -p /lib/firmware/raspberrypi/bootloader-2712
+rsync -alv "${FIRMWARE_DIR}-2712"/* /lib/firmware/raspberrypi/bootloader-2712 || echo "Failed"
 
 cp -fv "${script_dir}/../rpi-eeprom-config" /usr/bin
 cp -fv "${script_dir}/../rpi-eeprom-digest" /usr/bin