* [RAUC] Initial rauc.status file
@ 2022-01-25 13:11 Charles Steinkuehler
0 siblings, 0 replies; only message in thread
From: Charles Steinkuehler @ 2022-01-25 13:11 UTC (permalink / 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)
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?
RAUC mailing list
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-01-25 13:11 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-25 13:11 [RAUC] Initial rauc.status file Charles Steinkuehler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox