Skip to content

RFC A/B firmware update based in eMMC boot partition.

Ying-Chun Liu u-boot 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 6 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2drivers: mmc: write protect active boot area after mmc init.drivers/mmc/Kconfig drivers/mmc/mmc.c+68 -03 replies
2/2drivers: dfu: flash firmware to inactive boot area and active itdrivers/dfu/dfu_mmc.c include/dfu.h+30 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC 0/2] A/B firmware update based in eMMC boot partition.

From: "Ying-Chun Liu (PaulLiu)" <[email protected]>

Hi all,

I've implemented A/B firmware update based on eMMC hw partitions. Normally we have 2 boot partitions on eMMC. One is active and another is inactive. We can then flash the firmware to the inactive one and make it active.

Also when booting we can write protect the current active one. And left the inactive partition still writable.

So I make 2 commits that implements the following features:
1. Write protect "active" boot area when board init.
2. flash firmware to inactive boot area.
3. Change the inactive boot area after firmware update.

Thanks.

Ying-Chun Liu (PaulLiu) (2):
drivers: mmc: write protect active boot area after mmc init.
drivers: dfu: flash firmware to inactive boot area and active it

 drivers/dfu/dfu_mmc.c | 32 +++++++++++++++++++++---
 drivers/mmc/Kconfig   | 10 ++++++++
 drivers/mmc/mmc.c     | 58 +++++++++++++++++++++++++++++++++++++++++++
 include/dfu.h         |  1 +
 4 files changed, 98 insertions(+), 3 deletions(-)
Signature · 1 line
2.34.1