Skip to content

Commit 47c6c96

Browse files
committed
boot-watchdog: Describe the new boot-watchdog for Pi4 / Pi5
1 parent fae9204 commit 47c6c96

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

documentation/asciidoc/computers/raspberry-pi/eeprom-bootloader.adoc

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -146,6 +146,29 @@ The `BOOT_ORDER` property defines the sequence for the different boot modes. It
146146
| Try NVMe first, followed by USB-MSD then repeat
147147
|===
148148

149+
150+
[[BOOT_WATCHDOG_TIMEOUT]]
151+
==== `BOOT_WATCHDOG_TIMEOUT`
152+
153+
If set to a non-zero value (in seconds), enables a hardware watchdog timer in the bootloader. If the OS is not started within the specified time, the watchdog will reset the system.
154+
155+
The bootloader watchdog is automatically cancelled as soon as the ARM CPU is started. It does **not** monitor the OS after the handover from the bootloader.
156+
157+
This is useful for unattended or remote systems to ensure recovery from failed boots (e.g., if the OS never loads).
158+
159+
Default: `0` (disabled)
160+
161+
[[BOOT_WATCHDOG_PARTITION]]
162+
==== `BOOT_WATCHDOG_PARTITION`
163+
164+
If the bootloader watchdog triggers, this property specifies the partition number to boot from after the reset. This allows for automatic failover to a recovery or alternate partition.
165+
166+
If not set, the bootloader will retry the default partition (0).
167+
168+
You can use this in conjunction with the xref:config_txt.adoc#the-expression-filter[expression filter] to apply different settings or select a different boot flow when the watchdog triggers a reboot to a specific partition.
169+
170+
Default: `0`
171+
149172
[[MAX_RESTARTS]]
150173
==== `MAX_RESTARTS`
151174

0 commit comments

Comments
 (0)