mail archive of the meta-rauc mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: Llewellyn Fernandes <llewellyn.fernandes@evologics.de>
Cc: meta-rauc@pengutronix.de
Subject: Re: [meta-rauc] Queries about rauc
Date: Wed, 11 Dec 2019 09:20:25 +0100	[thread overview]
Message-ID: <2bd7dd9c-80f4-b08f-b1bf-95c7215d81d6@pengutronix.de> (raw)
In-Reply-To: <77113ccf-44fb-45e9-a65d-2d9ecc444b1b@evologics.de>

Hi Llewellyn,

Am 10.12.19 um 19:07 schrieb Llewellyn Fernandes:
> Hi,
> 
> I am a system engineer in Evologics Gmbh and we are planning to
> integrate rauc in our marine robotics products for ease of update .

ouh, that sounds like a really interesting application for RAUC!

> I have a query regarding the update process
> We have a board based on imx6 with emmc flash .
> I have created symmetric A B partitioning .
> 
> Kernel + dtb partition 1
> Rootfs.         Partition 2
> Kernel + dtb partition 3
> Rootfs.         Partition 4
> 
> I have managed to create the bundle for this .
> 
> My question is since there are 2 files ie kernel and dtb in one
> partition will this create a problem while installing the 2nd file .
> Does it format the partition and then install each file ?

As RAUC aims to perform 'image' updates, the straight solution to your
use case would be to provide a file system image containing both the
kernel and the dtb.
This should simply be possible by splitting up rootfs using wic or
genimage tool in a Yocto file system image recipe.

The other (quite similar similar) option would be to provide the two
files in a tar archive.  Then RAUC will perform file system creation and
unpacking of that tar. From the integration point of view this should
only differ from the first case in sense of image type.


Going a step backwards I would like to ask if there is really a need for
having the rootfs and the kernel being separate. With bootloader
supporting freescale boot spec files (such as barebox does), you can
easily store both the dtb and the kernel in the rootfs and the boot spec
file will tell the loader where to find it. This also potentially
enables you having the same rootfs for different machines/dtbs.


RAUC itself is currently not designed to install multiple individual
files to a slot.


Does that already help you a little?


Best regards, Enrico


P.S: Please consider subscribing to the mailing list as non-member
request will end up in the moderator queue first by default.

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
meta-rauc mailing list

  reply	other threads:[~2019-12-11  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 18:07 Llewellyn Fernandes
2019-12-11  8:20 ` Enrico Jörns [this message]
2019-12-11 16:02   ` llewellyn

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=2bd7dd9c-80f4-b08f-b1bf-95c7215d81d6@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=llewellyn.fernandes@evologics.de \
    --cc=meta-rauc@pengutronix.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