Update bug_report.yml

This commit is contained in:
Tim Gover
2022-02-11 09:18:23 +00:00
committed by GitHub
parent a84587a1ba
commit f555eff6e6

View File

@@ -64,8 +64,7 @@ body:
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 pins `14` and `15` on the (40-pin GPIO header)[https://www.raspberrypi.com/documentation/computers/os.html#gpio-and-the-40-pin-header]
* 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 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. * 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.
Please paste the bootloader logs here. Please paste the bootloader logs here.
validations: validations:
required: false required: false