Skip to content

bootloader: Remove redudant date information #2431

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Feb 16, 2022
Merged

bootloader: Remove redudant date information #2431

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a9f3ba9
Merge pull request #2397 from raspberrypi/develop
Feb 3, 2022
d36c341
Merge pull request #2400 from raspberrypi/develop
Feb 3, 2022
e63d19e
Merge pull request #2401 from raspberrypi/develop
Feb 3, 2022
c06f8a6
Merge pull request #2408 from raspberrypi/develop
Feb 7, 2022
4fe9977
Merge pull request #2411 from raspberrypi/develop
Feb 8, 2022
68812bb
bootloader: Remove redudant date information
timg236 Feb 16, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

=== Editing the Configuration

Before editing the bootloader configuration, xref:os.adoc#updating-and-upgrading-raspberry-pi-os[update your system] to get the latest version of the `rpi-eeprom` package. Releases prior to the 2020-09-03 default/critical release will not support all features listed here.
Before editing the bootloader configuration, xref:os.adoc#updating-and-upgrading-raspberry-pi-os[update your system] to get the latest version of the `rpi-eeprom` package.

To view the current EEPROM configuration: +
`rpi-eeprom-config`
Expand All @@ -28,7 +28,7 @@ Default: `0`

If `1` then `sudo halt` will run in a lower power mode until either GPIO3 or GLOBAL_EN are shorted to ground.

Default: `1` (`0` in original version of bootloader 2019-05-10)
Default: `1`

[[POWER_OFF_ON_HALT]]
==== POWER_OFF_ON_HALT
Expand All @@ -44,7 +44,6 @@ Default: `0`

The `BOOT_ORDER` setting allows flexible configuration for the priority of different boot modes. It is represented as 32bit unsigned integer where each nibble represents a boot mode. The boot modes are attempted in lowest significant nibble to highest significant nibble order.

The minimum supported bootloader version for custom boot modes is 2020-09-03.

[discrete]
====== `BOOT_ORDER` fields
Expand Down Expand Up @@ -76,7 +75,7 @@ The BOOT_ORDER property defines the sequence for the different boot modes. It is

| 0x5
| BCM-USB-MSD
| USB 2.0 boot from USB Type C socket (CM4: USB type A socket on CM IO board, using bootloader EEPROM from 2020-12-14 onwards).
| USB 2.0 boot from USB Type C socket (CM4: USB type A socket on CM IO board).

| 0x6
| NVME
Expand Down Expand Up @@ -267,10 +266,10 @@ If self update is enabled then the bootloader will look for the update files (.s
Notes:-

* Self-update is not enabled in SD boot; the ROM can already load recovery.bin from the SD card.
* Before self-update can be used the bootloader must have already been updated to a version which supports self update. The recommended approach would be to use the Raspberry Pi Imager and a spare SD card to update to pieeprom-2020-09-03 then use self-update for subsequent updates.
* Bootloader release prior to 2021 do not support `self-update`.
* For network boot make sure that the TFTP `boot` directory can be mounted via NFS and that `rpi-eeprom-update` can write to it.

Default: `1` (`0` in versions prior to 2020-09-03)
Default: `1`

[[FREEZE_VERSION]]
==== FREEZE_VERSION
Expand Down