summaryrefslogtreecommitdiffstats
path: root/Documentation/user/bootchooser.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/user/bootchooser.rst')
-rw-r--r--Documentation/user/bootchooser.rst12
1 files changed, 10 insertions, 2 deletions
diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index 1680ea78ed..1a2ce70bb2 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -83,7 +83,7 @@ The bootchooser algorithm aborts when all enabled targets (priority > 0) have
no remaining attempts left.
To prevent ending up in an unbootable system after a number of failed boot
-attempts, there is a also a built-in mechanism to reset the counters to their defaults,
+attempts, there is also a built-in mechanism to reset the counters to their defaults,
controlled by the ``global.bootchooser.reset_attempts`` variable. It holds a
list of space-separated flags. Possible values are:
@@ -92,6 +92,12 @@ list of space-separated flags. Possible values are:
(``$global.system.reset="POR"``) is detected, the ``remaining_attempts``
counters of all enabled targets are reset to their defaults.
This means after a power cycle all boot targets will be tried again for the configured number of retries.
+- ``reset``: When the bootchooser starts and a generic reset
+ (``$global.system.reset="RST"``) is detected, the ``remaining_attempts``
+ counters of all enabled targets are reset to their defaults.
+ This means that, if the systems reports a generic restart, the
+ ``remaining_attempts`` counters of all enabled targets are reset to
+ their defaults.
- ``all-zero``: When the bootchooser starts and the ``remaining_attempts``
counters of all enabled targets are zero, the ``remaining_attempts``
counters of all enabled targets are reset to their defaults.
@@ -112,7 +118,9 @@ In case only the booted system itself knows when it is in a good state,
it can report this to the bootchooser from Linux userspace using the
*barebox-state* tool from the dt-utils_ package.::
- barebox-state -s bootstate.<target>.remaining_attemps <reset-value>
+ barebox-state [-n <state variable set>] -s [<prefix>.]<target>.remaining_attempts=<reset-value>
+ barebox-state -n system_state -s bootstate.system1.remaining_attempts=3
+ barebox-state -s system1.remaining_attempts=3
If instead the bootchooser can detect a failed boot itself using the
:ref:`reset reason <reset_reason>` (WDG), one can mark the boot successful