summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2020-02-27 14:29:24 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2020-03-02 09:11:08 +0100
commit1a26c1d36bdcd23b90bfa6f36774878e7fa8fb95 (patch)
treeb6439324ec4527f305c9ac43dfc37ab06163a6b4
parent9044ad7c2cf78a2963c9ddc3c4b9bf2054f46e95 (diff)
downloadbarebox-1a26c1d36bdcd23b90bfa6f36774878e7fa8fb95.tar.gz
barebox-1a26c1d36bdcd23b90bfa6f36774878e7fa8fb95.tar.xz
Documentation: boards: stm32mp: document eMMC partition layout
For eMMC, the boot partitions are used for FSBL instead of having these two partitions in the user area, like with SD-Cards. Document this. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r--Documentation/boards/stm32mp.rst19
1 files changed, 17 insertions, 2 deletions
diff --git a/Documentation/boards/stm32mp.rst b/Documentation/boards/stm32mp.rst
index 6d97b0d6d4..de793ab3c9 100644
--- a/Documentation/boards/stm32mp.rst
+++ b/Documentation/boards/stm32mp.rst
@@ -35,7 +35,7 @@ The resulting images will be placed under ``images/``:
Flashing barebox
----------------
-An appropriate image for the boot media can be generated with following
+An appropriate image for a SD-Card can be generated with following
``genimage(1)`` config::
image @STM32MP_BOARD@.img {
@@ -61,7 +61,22 @@ An appropriate image for the boot media can be generated with following
}
}
-Image can then be flashed on e.g. a SD-Card.
+For eMMC, the boot partitions are used as the FSBL partitions and so the user
+partitions may look like this:
+
+ image @STM32MP_BOARD@.img {
+ partition ssbl {
+ image = "barebox-@STM32MP_BOARD@.img"
+ size = 1M
+ }
+ partition barebox-environment {
+ image = "/dev/null"
+ size = 1M
+ }
+ }
+
+The fsbl1 and fsbl2 can be flashed by writing to barebox ``/dev/mmcX.boot0`` and
+``/dev/mmcX.boot1`` respectively or from a booted operating system.
Boot source selection
---------------------