mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Charles Steinkuehler <charles@steinkuehler.net>
To: rauc@pengutronix.de
Subject: [RAUC] Initial rauc.status file
Date: Tue, 25 Jan 2022 07:11:29 -0600	[thread overview]
Message-ID: <7f363e23-fa86-59f7-96dd-ea24d3d459e8@steinkuehler.net> (raw)

In my Buildroot+RAUC example (https://github.com/cdsteinkuehler/br2rauc) 
by default the slots are not writable so I am using a rauc.status file 
on the partition used for storing state and configuration data.

The issue is when I create a new image the rauc.status file is empty 
although the created uSD image includes valid data for all of the slots.

My image build process is roughly:

Create vfat bootfs
-> Write bootfs to boot-mbr-switch uSD primary slot
-> Write bootfs to boot-mbr-switch uSD secondary slot
-> Create RAUC bundle using bootfs

Create rootfs image
-> Write rootfs image to uSD primary slot
-> Write rootfs image to uSD secondary slot
-> Create RAUC bundle using rootfs

Create empty writable data partition (where rauc.status lives)

Questions:
Is there a suggested method of getting from update bundles to a disk 
image that includes the proper contents in rauc.status?

Can I use the rauc command to "cross install", eg: use rauc to write the 
aarch64 contents to the loopback image file on my x86 development system 
and update the rauc.status file in the process, or do I need to do this 
on the target system?

-- 
Charles Steinkuehler
charles@steinkuehler.net

_______________________________________________
RAUC mailing list


                 reply	other threads:[~2022-01-25 13:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7f363e23-fa86-59f7-96dd-ea24d3d459e8@steinkuehler.net \
    --to=charles@steinkuehler.net \
    --cc=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