summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoshua Watt <jpewhacker@gmail.com>2023-07-03 18:07:13 +0300
committerTom Rini <trini@konsulko.com>2023-07-17 23:20:08 +0300
commit3430f24bc69d61eadf5b09999d58c468ac67c9fe (patch)
tree2be4c8232f5cb3637da9c7cc501f3c8eb9d8f3f0 /doc
parent55a424437226f9ef50c3e829dafa6b494377d018 (diff)
downloadu-boot-3430f24bc69d61eadf5b09999d58c468ac67c9fe.tar.xz
android_ab: Try backup booloader_message
Some devices keep 2 copies of the bootloader_message in the misc partition and write each in sequence when updating. This ensures that there is always one valid copy of the bootloader_message. Teach u-boot to optionally try a backup bootloader_message from a specified offset if the primary one fails its CRC check. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/android/ab.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/android/ab.rst b/doc/android/ab.rst
index 961895c32e..2adf88781d 100644
--- a/doc/android/ab.rst
+++ b/doc/android/ab.rst
@@ -31,6 +31,12 @@ boot script. This command analyzes and processes A/B metadata stored on a
special partition (e.g. ``misc``) and determines which slot should be used for
booting up.
+If the A/B metadata partition has a backup bootloader_message block that is used
+to ensure one is always valid even in the event of interruption when writing, it
+can be enabled in your board configuration file::
+
+ CONFIG_ANDROID_AB_BACKUP_OFFSET=0x1000
+
Command usage
-------------