| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Select BUSYBOX_CONFIG_FEATURE_TAR_AUTODETECT and
BUSYBOX_FEATURE_SEAMLESS_XZ if BUSYBOX_TAR is enabled. These options are
required according to the documentation avilable at [1].
While at it convert the space to tab after the if for long options.
[1]: https://rauc.readthedocs.io/en/v1.0/integration.html#required-target-tools
Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
|
|
|
|
|
| |
On systems showing /dev/root for the root node in /proc/mounts instead of a
real device, RAUC tries to mount an already mounted device when using
glib without feature libmount enabled.
Using feature libmount in glib fixes this.
Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
|
|
| |
Since RAUC 1.0 that calls tar with --numeric-owner argument, one needs
to have long options support enabled when using busybox tar.
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
| |
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
| |
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
| |
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
|
| |
RAUC uses gdbus-codegen host tool for creating its gdbus source files.
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
|
|
| |
This allows for installation of the rauc system configuration via an
extra package, which is useful in scenarios involving image packages.
Signed-off-by: Florian Bäuerle <florian.baeuerle@allegion.com>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
|
|
|
|
|
| |
In my usecase I need PTXCONF_PROJECT_VERSION in the rauc bundle instead
of PTXDIST_BSP_AUTOVERSION that is hard coded in rules/image-rauc.make.
Introduce a new switch RAUC_BUNDLE_VERSION to menuconfig that defaults
to "${PTXDIST_BSP_AUTOVERSION}".
Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
rauc uses unsquashfs to extract the data from the bundle. If unsquashfs
is not installed, for example 'rauc info' fails with the following error
message:
(rauc:302): rauc-WARNING **: Failed to start unsquashfs: Failed to execute child process "unsquashfs" (No such file or directory)
Therefore, rauc should pull unsquashfs as a runtime dependency.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
|
|
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>
|
