|
|
This adds recipes for building the RAUC update tool both as a host
tool as well as a target update tool and service.
When using systemd, the package will install a rauc.service that allows
to start RAUC, by default RAUC does not start automatically but uses
D-Bus activation when invoked by your application or by the command line
tool ./rauc.
You will also get a rauc-mark-good.service in your rootfs by default
that is wanted by multi-user.taget and is used to notify the underlying
bootloader implementation about having booted successfully in userspace.
You can also make it depend on your application services being started.
For integrating RAUC with your platform, you need to have a system
description file /etc/rauc/system.conf in your platforms projectroot/
dir. This defines all relevant slots and provides information and
configuration RAUC requires to properly handle the platform it is
running on.
You also have to place a valid keyring file into you platforms
projectroot/ as /etc/rauc/ca.cert.pem to allow RAUC verifying update
Bundles before installing them.
There are dummy files installed by default for ca.cert.pem and
system.conf which only contain hints on how to set up correct
project-specific ones.
The additional good-marking-service installed by the recipe runs after
user space is brought up and notifies the underlying bootloader
implementation about a successful boot of the system.
This is typically used in conjunction with a boot attempts counter
in the bootloader that is decremented before starting the systemd and
reset by `rauc status mark-good` to indicate a successfully system
startup.
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
