Upgrade Layer Refs

See merge request !41

Dynamic selection of i.MX8MM U-Boot environment config in Linux userspace

See merge request !40

Support for i.MX8MP hardware (OSM-S, BL)

See merge request !13

Sparkle Recipe Fixes

See merge request !38

Remove KED i.MX production-tool (ptool) as it causes more pain than it helps

See merge request !39

They are already covered in the python3-can recipe or if not should
be added there.

This solves the following error message with Kirkstone:

Bitbake Fetcher Error: FetchError("Recipe uses a floating tag/branch 'rel_1.9.0' for repo 'git.kontron-electronics.de/sw/misc/apps/sparkle.git' without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE).", None)

docs: Split release notes and update content

See merge request !34

This will provide a better overview when the number of releases
increases.

For customers it is more helpful to provide guiding in the docs for the production
steps instead of using this horrible shell script that doesn't do what you want in
most cases.

meta-ked-imx: Use fitImageA/B instead of active/inactive

See merge request !35

Michael Walle authored 1 year ago and Frieder Schrempf committed 1 year ago

This is supposed to fix a problem where you can end up with two
non-working images.

This can be triggered by the following actions:

  * Starting with rootfs A and fitImage_active
  * Doing an update via swupdate using a corrupted kernel image
  * fitImage_active gets renamed to fitImage_inactive.
  * The corrupted kernel now in fitImage_active fails to boot
  * A fallback to rootfs A occurs: rootfs A is started together
    with the working fitImage_inactive
  * On the next update via swupdate the corrupted fitImage_active is
    renamed to fitImage_inactive ending up with two corrupted kernel
    images
  * The now corrupted fitImage_inactive is copied to fitImage_active
    and the boot is bricked

To remedy this flaw, simply swap the fitImage in sync with the rootfs.
Instead of the active/inactive image we now use A/B for the kernel image
and the currently used image is selected by the sys_active file.