From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx0.itk-engineering.de ([212.121.145.30]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dBI0A-0000Oi-Sx for RAUC@pengutronix.de; Thu, 18 May 2017 11:45:47 +0200 Received: from vwexchange001.itk.local (vwexchange001.itk.local [10.61.0.114]) by mx0.itk-engineering.de (8.14.7/8.14.7) with ESMTP id v4I9jWXr030529 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=FAIL) for ; Thu, 18 May 2017 11:45:32 +0200 From: Martin Hollingsworth Date: Thu, 18 May 2017 09:45:42 +0000 Message-ID: <4a0389f5ec894cac88bd34a17893fc26@itk-engineering.de> Content-Language: de-DE MIME-Version: 1.0 Subject: [RAUC] Bootloader updates List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1301266800==" Errors-To: rauc-bounces@pengutronix.de Sender: "RAUC" To: "RAUC@pengutronix.de" --===============1301266800== Content-Language: de-DE Content-Type: multipart/alternative; boundary="_000_4a0389f5ec894cac88bd34a17893fc26itkengineeringde_" --_000_4a0389f5ec894cac88bd34a17893fc26itkengineeringde_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello RAUC Team, I am currently implementing software update on my embedded target and evalu= ating the usage of RAUC. But I have trouble finding a solution for the foll= owing scenario, which needs a little explanation, but can be summerized as:= "How does Rauc handle Bootloader Updates?" Here is what I want to achieve: A software release is a combination of multiple software components in spec= ific versions, that have been tested and defined fit for usage together on = an embedded target. Lets say a simple example would be a bootloader and a r= ootFS (which includes linux and some custom software pre-installed). When I update my system, I secure my linux operating system using a symmetr= ic A/B setup. If the update fails, I can always jump back to the last slot = and continue regular device operation. But when I update my bootloader AND my linux system together, after exchang= ing the bootloader I cannot jump back to the last running linux, because no= w the bootloader configuration might not match the configuration expected f= rom the previous bootloader. How does RAUC approach this issue? Thanks in advance and greetings, Martin --_000_4a0389f5ec894cac88bd34a17893fc26itkengineeringde_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello RAUC Team,

I am currently implementing sof= tware update on my embedded target and evaluating the usage of RAUC. But I = have trouble finding a solution for the following scenario, which needs a l= ittle explanation, but can be summerized as: „How does Rauc handle Bootloader Updates?”

 

Here is what I want to achieve:=

 

A software release is a combina= tion of multiple software components in specific versions, that have been t= ested and defined fit for usage together on an embedded target. Lets say a = simple example would be a bootloader and a rootFS (which includes linux and some custom software pre-installed)= .

 

When I update my system, I secu= re my linux operating system using a symmetric A/B setup. If the update fai= ls, I can always jump back to the last slot and continue regular device ope= ration.

 

But when I update my bootloader= AND my linux system together, after exchanging the bootloader I cannot jum= p back to the last running linux, because now the bootloader configuration = might not match the configuration expected from the previous bootloader.

 

How does RAUC approach this iss= ue?

 

Thanks in advance and greetings= ,

Martin

 

--_000_4a0389f5ec894cac88bd34a17893fc26itkengineeringde_-- --===============1301266800== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUkFVQyBtYWls aW5nIGxpc3Q= --===============1301266800==--