94d4bbbe9f
Implement a new mechanism to allow users to create update packages based on files and folders to modify
the active system.
This is done through the new class 'swupdate-files', which creates a tar.gz update file in the image
distribution output directory containing all the files and directories to create/update. The 'tar.gz'
file is used later by the 'swu-images' recipe to generate the final SWUpdate package. The SWU package
installation process extracts the tar.gz file in the root folder ("/") of the active system.
Users can specify the list of files and directories to include in the update package using the
'SWUPDATE_FILES_LIST' variable. These files will be directly copied from the generated system rootfs and
placed in the tar.gz archive. Additionally, users can provide their custom 'tar.gz' file to use in the update
by specifying its location in the 'SWUPDATE_FILES_TARGZ_FILE' variable. In any case, all the paths to include
in the update package must be relative to "/", as it is the base directory where tar.gz file contents are
extracted.
The update process for dual boot systems sets a new u-boot flag so that active bank is not swapped once
installation is complete and system reboots.
The SWU update mechanism based on files provides a custom update script which takes care of preparing the
system for the installation process. Just like in the SWU updates based on images, users can customize this
script or override it with the 'SWUPDATE_SCRIPT' variable, specifying the location of the new script to use.
If both the 'SWUPDATE_FILES_LIST' and 'SWUPDATE_FILES_TARGZ_FILE' variables are empty, a standard images
SWUpdate package will be generated instead.
Signed-off-by: David Escalona <david.escalona@digi.com>
|
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers | ||
| recipes-aws | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-crank | ||
| recipes-devtools | ||
| recipes-digi | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-multimedia | ||
| recipes-sato | ||
| recipes-support | ||
| DIGI_EULA | ||
| DIGI_OPEN_EULA | ||
| README | ||
README
OpenEmbedded/Yocto Digi Embedded Linux layer ============================================ This layer provides the Digi Embedded Linux distribution images. This layer depends on: git://git.yoctoproject.org/poky.git git://git.openembedded.org/meta-openembedded.git git://git.yoctoproject.org/meta-freescale.git git://github.com/Freescale/meta-fsl-demos.git Digi's license agreements ------------------------- All software is covered by Digi's general EULA and Digi's Open Source EULA. To have the right to use the software in your images you need to read and accept both EULAs at the DIGI_EULA and DIGI_OPEN_EULA files. NXP Semiconductors' software license agreement ---------------------------------------------- Some platforms depends on libraries and packages that are covered by NXP Semiconductors' EULA. To have the right to use those binaries in your images you need to read and accept the EULA file in meta-freescale Yocto layer. Support ------- This layer is provided 'as is' with no guarantee. However, some support may be available from tech.support@digi.com