public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Ying-Chun Liu <grandpaul@gmail.com>
Cc: u-boot@lists.denx.de, "Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>
Subject: Re: [RFC 0/2] A/B firmware update based in eMMC boot partition.
Date: Tue, 25 Jan 2022 15:43:29 +0100	[thread overview]
Message-ID: <3678646.1643121809@gemini.denx.de> (raw)
In-Reply-To: <20220125135535.224061-1-grandpaul@gmail.com>

Dear Ying-Chun Liu,

In message <20220125135535.224061-1-grandpaul@gmail.com> you wrote:
>
> 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.

We have been doing software updates using U-Boot scripts etc. for
many, many years.  But during that time a large number of
restrictions and shortcomings became clear.  this is why projects
like SWUpdate [1] came into life, and U-Boot supports this only with
very basic features:

- watchdog support to reset a hanging system
- boot counter to switch to an alternate boot command in case of too
  many failed boot attempts

That's all. Not more is needed, and not more should be used in
U-Boot.

I'm not sure if you know SWUpdate - if not, you should definitely
look into it.  I strongly recommend not to try to reinvent that
wheel - poorly - in U-Boot.  We have been there before, and got rid
of this approach for a pretty long list of good reasons.


[1] https://sbabic.github.io/swupdate/


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"More software projects have gone awry for lack of calendar time than
for all other causes combined."
                         - Fred Brooks, Jr., _The Mythical Man Month_

  parent reply	other threads:[~2022-01-25 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 13:55 [RFC 0/2] A/B firmware update based in eMMC boot partition Ying-Chun Liu
2022-01-25 13:55 ` [RFC 1/2] drivers: mmc: write protect active boot area after mmc init Ying-Chun Liu
2022-01-26 23:25   ` Jaehoon Chung
2022-01-27  1:23     ` Paul Liu
2022-01-27  1:45       ` Jaehoon Chung
2022-01-25 13:55 ` [RFC 2/2] drivers: dfu: flash firmware to inactive boot area and active it Ying-Chun Liu
2022-01-25 14:43 ` Wolfgang Denk [this message]
2022-01-26  8:28   ` [RFC 0/2] A/B firmware update based in eMMC boot partition Alexander Dahl
2022-02-03 18:19   ` Tom Rini

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=3678646.1643121809@gemini.denx.de \
    --to=wd@denx.de \
    --cc=grandpaul@gmail.com \
    --cc=paul.liu@linaro.org \
    --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