Merge pull request #264 from XECDesign/debian/buster

Debian/buster

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,15 +1,21 @@
 ---
 name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: ''
+about: Create a bug report for the bootloader EEPROM or rpi-eeprom-update scripts. Please use the Raspberry Pi General Discussion forum for general questions about the bootloader.
 
 ---
 
-For general boot questions please check the read the [Boot Problems](https://www.raspberrypi.org/forums/viewtopic.php?t=58151) sticky post on the forums.  
+This repository tracks bugs for the Raspberry Pi 4 bootloader EEPROM and Linux update scripts.
 
-N.B The bootloader does not persist in memory and if the rainbow splash screen has been displayed the issue is likely to be in the firmware or Linux. If so, it's better to target the bug in the [Firmware](https://github.com/raspberrypi/firmware/) or [Linux](https://github.com/raspberrypi/linux/) repositories first e.g. NFS, USB or dmesg logs would be Linux issues.
+* If you suspect a hardware problem then please read the [Boot Problems](https://www.raspberrypi.org/forums/viewtopic.php?p=437084) post first before contacting the reseller.
+* Support questions or should be posted on the Raspberry Pi [General Discussion](https://www.raspberrypi.org/forums/viewforum.php?f=63)**
+
+
+**Mandatory information**
+* Raspberry Pi model
+* Board revision (cat /proc/cpuinfo | grep Revision)
+* Operating system version .
+* Details of any hardware attached e.g. links to USB 
+* Photo of the HDMI diagnostics screen, UART trace.
 
 **Describe the bug**
 A clear and concise description of what the bug is.
@@ -20,27 +26,25 @@ Steps to reproduce the behavior:
 **Expected behaviour**
 A clear and concise description of what you expected to happen.
 
-**Screenshots**
-If applicable, add a photograph of the bootloader HDMI diagnostics screen.
-
 **Bootloader version and configuration**
-If you have modified the default bootloader release or configuration then please attach the bootloader configuration (vcgencmd bootloader_config) and version (vcgencmd bootloader_version)
+If you have modified the default bootloader release or configuration then please attach the bootloader configuration vcgencmd bootloader_config and version (vcgencmd bootloader_version)
 
 **SD card boot (please complete the following information):**
- - OS e.g. Raspbian
  - SD card type
- - Partition information (fdisk -l) if you are able to obtain this from another computer.
+ - Partition information (sudo fdisk -l) if you are able to obtain this from another computer.
 
 **Network boot (please complete the following information):**
-Network boot configuration can get very complicated. To get started we recommend using [PiServer](https://github.com/raspberrypi/piserver) and this is the official test/reference configuration. For other configurations, packet capture or a UART log is nearly always required because setting up custom network configurations to investigate bugs is extremely time-consuming and error-prone.
+Network boot bug normally require one or more of the following log types. [PiServer](https://github.com/raspberrypi/piserver) is the officially supported network boot server.
 
  - DHCP server configuration files e.g. dnsmasq.conf
  - Wireshark binary packet capture
  - UART logs
 
 **USB boot (please complete the following information):**
-For issues booting with specific USB devices please verify that the system boots from an SD-card with the same devices connected and attach the results of 'lsusb -vvv'. This helps to rule out USB HUB power issues.
-In the beta release it's likely that a UART or NetConsole boot trace will be required.
+Verify that the the USB device works correctly when hot-plugged under Linux and attache the output of 'lsusb -vvv'
 
 **Additional context**
-Add any other context about the problem here.
+Add any other context about the problem here. 
+
+The [Bootloader configuration](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md) page describes how to enable UART or NETCONSOLE logs. For complex USB boot issues NETCONSOLE logs are recommended.
+

debian/changelog

@@ -1,3 +1,11 @@
+rpi-eeprom (10.4-1) buster; urgency=medium
+
+  [ Tim Gover ]
+  * Update bug_report.md
+  * pieeprom-2020-12-11: CM4/PI400 conditional filters - BETA
+
+ -- Serge Schneider <serge@raspberrypi.com>  Fri, 11 Dec 2020 13:43:26 +0000
+
 rpi-eeprom (10.3-1) buster; urgency=medium
 
   [ andrum99 ]

firmware/release-notes.md

@@ -3,6 +3,16 @@
 USB MSD boot also requires the firmware from Raspberry Pi OS 2020-08-20 or newer.
 https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md
 
+## 2020-12-11 - CM4/PI400 conditional filters - BETA
+   * Add support for [cm4] and [pi400] config conditionals filters.
+   * Tidyup RPIBOOT USB descriptors.
+   * Add a gap before displaying LED error pattern and change the default state
+     to off after displaying the first error pattern.
+   * Generate 0xffff instead of 0x0 if the checksum of the UDP packet to be
+     transmitted is 0x0.
+   * Rename USB-DEV to RPIBOOT in boot-mode strings. Bootmode was renamed to
+     avoid confusion with USB MSD boot.
+
 ## 2020-11-24 BCM2711 xHC boot support - BETA
    * Add support for booting from the BCM2711 XHCI controller which is the
      USB-C socket on Pi 4B / Pi 400 and the type A sockets on Compute Module 4