From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Cc: Michael Walle <michael@walle.cc>
Subject: [PATCH v3 5/5] board: sl28: add update image documentation
Date: Wed, 29 Sep 2021 13:39:13 +0200 [thread overview]
Message-ID: <20210929113913.43407-5-michael@walle.cc> (raw)
In-Reply-To: <20210929113913.43407-1-michael@walle.cc>
Document the update image and how to use the EFI UpdateCapsule.
Signed-off-by: Michael Walle <michael@walle.cc>
---
changes since v2:
- none
changes since v1:
- new patch
doc/board/kontron/sl28.rst | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/doc/board/kontron/sl28.rst b/doc/board/kontron/sl28.rst
index 07431986d8..c7b18bed10 100644
--- a/doc/board/kontron/sl28.rst
+++ b/doc/board/kontron/sl28.rst
@@ -52,6 +52,21 @@ Disable the builtin watchdog
- power-cycle the board
+Update image
+------------
+
+After the build finished, there will be an update image called
+u-boot.update. This can either be used in the DFU mode (which isn't
+supported yet) or encapsulated in an EFI UpdateCapsule.
+
+To build the capsule use the following command
+
+ $ tools/mkeficapsule -f u-boot.update -i 1 UpdateUboot
+
+Afterward you can copy this file to your ESP into the /EFI/UpdateCapsule/
+folder. On the next EFI boot this will automatically update your
+bootloader.
+
Useful I2C tricks
-----------------
--
2.30.2
prev parent reply other threads:[~2021-09-29 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 11:39 [PATCH v3 1/5] board: sl28: enable EFI_SET_TIME support Michael Walle
2021-09-29 11:39 ` [PATCH v3 2/5] board: sl28: generate FIT update image Michael Walle
2021-09-29 11:39 ` [PATCH v3 3/5] board: sl28: enable EFI UpdateCapsule support Michael Walle
2021-09-29 11:39 ` [PATCH v3 4/5] doc: board: kontron: sl28: Reduce section levels and change title Michael Walle
2021-09-29 11:39 ` Michael Walle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210929113913.43407-5-michael@walle.cc \
--to=michael@walle.cc \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).