Yocto concept and support for dual version firmware upgrad and boot


JH
 

Hi,

Are there any Yocto recipes to support dual version control for
firmware image upgrade and boot?

The scenario is to make 2 partitions, one partition to install a work
version of image, say v1.0, another partition to install a development
version of image, say v1.1, the boot process should pick up the
highest the version v1.1 first, if it fails to boot, it retreats back
to boot old version v1.0.

Appreciate any tips or reference for that implementation in Yocto.

Thank you.

Kind regards,

- jupiter


Henrik Nymann Jensen (HNJE) <hnje@...>
 

On 2019-05-03 03:55, JH wrote:
Hi,

Are there any Yocto recipes to support dual version control for
firmware image upgrade and boot?
This is not something Yocto comes with out of the box, but both rauc and
swupdate
provides a meta layer you could use.

https://github.com/rauc/meta-rauc
https://github.com/sbabic/meta-swupdate

The scenario is to make 2 partitions, one partition to install a work
version of image, say v1.0, another partition to install a development
version of image, say v1.1, the boot process should pick up the
highest the version v1.1 first, if it fails to boot, it retreats back
to boot old version v1.0.

Appreciate any tips or reference for that implementation in Yocto.

Thank you.

Kind regards,

- jupiter


Jaquier Cyril <Cyril.Jaquier@...>
 

Hi,

I've been experimenting with mender a bit lately. Works great so far and it's fully integrated into yocto:

https://mender.io/

There are a few other solutions available for Yocto:

https://wiki.yoctoproject.org/wiki/System_Update#Comparison

Regards,
Cyril

________________________________________
From: yocto-bounces@... [yocto-bounces@...] on behalf of JH [jupiter.hce@...]
Sent: Friday, May 03, 2019 03:55
To: Yocto discussion list
Subject: [yocto] Yocto concept and support for dual version firmware upgrad and boot

Hi,

Are there any Yocto recipes to support dual version control for
firmware image upgrade and boot?

The scenario is to make 2 partitions, one partition to install a work
version of image, say v1.0, another partition to install a development
version of image, say v1.1, the boot process should pick up the
highest the version v1.1 first, if it fails to boot, it retreats back
to boot old version v1.0.

Appreciate any tips or reference for that implementation in Yocto.

Thank you.

Kind regards,

- jupiter
--
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


JH
 

Thanks Jaquier, did you run mender in an embedded system?

On 5/3/19, Jaquier Cyril <Cyril.Jaquier@...> wrote:
Hi,

I've been experimenting with mender a bit lately. Works great so far and
it's fully integrated into yocto:

https://mender.io/

There are a few other solutions available for Yocto:

https://wiki.yoctoproject.org/wiki/System_Update#Comparison

Regards,
Cyril

________________________________________
From: yocto-bounces@... [yocto-bounces@...] on
behalf of JH [jupiter.hce@...]
Sent: Friday, May 03, 2019 03:55
To: Yocto discussion list
Subject: [yocto] Yocto concept and support for dual version firmware upgrad
and boot

Hi,

Are there any Yocto recipes to support dual version control for
firmware image upgrade and boot?

The scenario is to make 2 partitions, one partition to install a work
version of image, say v1.0, another partition to install a development
version of image, say v1.1, the boot process should pick up the
highest the version v1.1 first, if it fails to boot, it retreats back
to boot old version v1.0.

Appreciate any tips or reference for that implementation in Yocto.

Thank you.

Kind regards,

- jupiter
--
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Burton, Ross <ross.burton@...>
 

On Fri, 3 May 2019 at 07:46, Jaquier Cyril <Cyril.Jaquier@...> wrote:
There are a few other solutions available for Yocto:

https://wiki.yoctoproject.org/wiki/System_Update#Comparison
That list needs updating as there's a few more available now such as
Balena and UpdateHub, but both Mendor and swupdate are both still
going strong and have supported integration. I've heard good things
about swupdate, and it can be used to implement your design:
https://sbabic.github.io/swupdate/overview.html#double-copy-with-fall-back

Ross


Jaquier Cyril <Cyril.Jaquier@...>
 

Only on a Raspberry Pi 3 so far (uboot supported is already present for it).


________________________________________
From: JH [jupiter.hce@...]
Sent: Friday, May 03, 2019 11:16
To: Jaquier Cyril
Cc: Yocto discussion list
Subject: Re: [yocto] Yocto concept and support for dual version firmware upgrad and boot

Thanks Jaquier, did you run mender in an embedded system?

On 5/3/19, Jaquier Cyril <Cyril.Jaquier@...> wrote:
Hi,

I've been experimenting with mender a bit lately. Works great so far and
it's fully integrated into yocto:

https://mender.io/

There are a few other solutions available for Yocto:

https://wiki.yoctoproject.org/wiki/System_Update#Comparison

Regards,
Cyril

________________________________________
From: yocto-bounces@... [yocto-bounces@...] on
behalf of JH [jupiter.hce@...]
Sent: Friday, May 03, 2019 03:55
To: Yocto discussion list
Subject: [yocto] Yocto concept and support for dual version firmware upgrad
and boot

Hi,

Are there any Yocto recipes to support dual version control for
firmware image upgrade and boot?

The scenario is to make 2 partitions, one partition to install a work
version of image, say v1.0, another partition to install a development
version of image, say v1.1, the boot process should pick up the
highest the version v1.1 first, if it fails to boot, it retreats back
to boot old version v1.0.

Appreciate any tips or reference for that implementation in Yocto.

Thank you.

Kind regards,

- jupiter
--
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto