Hi,
On Tue, May 5, 2015 at 6:55 AM, Craig McQueen
craig.mcqu...@innerrange.com wrote:
I’m working on this for a BeagleBone Black type system, which uses eMMC
snip
Just sharing some information that I found interesting:
One such approach for firmware upgrade is implemented in this meta layer:
Hi
On Tue, May 5, 2015 at 6:55 AM, Craig McQueen
craig.mcqu...@innerrange.com wrote:
I’m working on this for a BeagleBone Black type system, which uses eMMC
(i.e. disk partitions). I’m considering:
snip
The BeagleBone Black U-Boot implements an incrementing ‘bootcount’, stored
in RTC
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Chris Morgan
On Saturday, May 2, 2015, Patrick Doyle
wpds...@gmail.commailto:wpds...@gmail.com wrote:
Rather than inventing this from scratch yet again, I would like to ask
what the Yocto-ish best practice
On Sun, May 3, 2015 at 3:58 PM, Chris Morgan chmor...@gmail.com wrote:
We thought about the rescue/recovery approach as well. The issue was how the
system would recover in the field and how updates were handled.
Consider that to update the full system image you'd have to download and
store
On Saturday, May 2, 2015, Patrick Doyle wpds...@gmail.com wrote:
Rather than inventing this from scratch yet again, I would like to ask
what the Yocto-ish best practice is for deploying an embedded system
that has to support in-place upgrades.
It seems to me that this should be a fairly
On Sun, May 3, 2015 at 5:51 AM, Chris Morgan chmor...@gmail.com wrote:
Is there a standard way? We've seen a few different approaches between
android systems (phones), Linux distributions, and things like chromebook.
In our case we are using two uboot, two kernel, and two root file system
On Sunday, May 3, 2015, Patrick Doyle wpds...@gmail.com wrote:
On Sun, May 3, 2015 at 5:51 AM, Chris Morgan chmor...@gmail.com
javascript:; wrote:
Is there a standard way? We've seen a few different approaches between
android systems (phones), Linux distributions, and things like
Rather than inventing this from scratch yet again, I would like to ask
what the Yocto-ish best practice is for deploying an embedded system
that has to support in-place upgrades.
It seems to me that this should be a fairly common scenario:
I have (or, rather am in the process of developing yet
