aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPali Rohár <pali@kernel.org>2023-04-13 22:57:47 +0200
committerStefan Roese <sr@denx.de>2023-05-03 08:39:23 +0200
commit4ee99d9ff98ba9b57b65fb895504f767dfe14d82 (patch)
tree0890d5347a8f635e2cebde6069512f2f6029ae79
parent30f6305e0cdcf59b0247b057f04374818d7c76e6 (diff)
downloadu-boot-4ee99d9ff98ba9b57b65fb895504f767dfe14d82.zip
u-boot-4ee99d9ff98ba9b57b65fb895504f767dfe14d82.tar.gz
u-boot-4ee99d9ff98ba9b57b65fb895504f767dfe14d82.tar.bz2
tools: kwboot: Fix MMC partitions documentation
Boot configuration stored in EXT_CSD_PART_CONF register is completely ignored by BootROM. Fixes: fa03279e198d ("tools: kwboot: Add image type documentation") Signed-off-by: Pali Rohár <pali@kernel.org>
-rw-r--r--tools/kwboot.c9
1 files changed, 6 insertions, 3 deletions
diff --git a/tools/kwboot.c b/tools/kwboot.c
index 6bef461..550d249 100644
--- a/tools/kwboot.c
+++ b/tools/kwboot.c
@@ -119,9 +119,12 @@
* 1024 bytes long sector sizes and also can be changed at runtime.
*
* For MMC-compatible devices, image can be stored at offset 0 or at offset
- * 2 MB. If MMC device supports HW boot partitions then image must be stored
- * on the HW partition as is configured in the EXT_CSC register (it can be
- * either boot or user data).
+ * 2 MB. If eMMC device supports HW/boot partitions then image is read from
+ * partitions in following order: Boot 1, Boot 2, RPMB, GP 1, GP 2, GP 3,
+ * GP 4, User Data, Boot 1, Boot 2. (Boot 1 and Boot 2 are really repeated).
+ * Boot configuration stored in EXT_CSD_PART_CONF eMMC register is completely
+ * ignored by the BootROM. But it sets PARTITION_ACCESS bits of that register
+ * to the selected partition from which it loaded image.
*
* Note that source address for SDIO image is stored in byte unit, like for
* any other images (except SATA). Marvell Functional Specifications for