The S3 path now follows the pattern:
/mender/mender-convert/uboot/<dev-family>/<dev-config>-<uboot-ver>.tar
For RPi and BBB these are automatically published form the CI Pipeline
of repo mender-convert-integration-scripts while for RockPro64 they have
been manually moved (as we expect this to be a one time integration).
Reworked a bit also the *_BINARIES variable so that we can keep the
u-boot version in the base config files and let the childs only define
the a config name.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
This is necessary for the U-boot -> EFI -> GRUB integration to be
complete as many boards embedd the U-Boot binary at the start
of the SD/eMMC a.k.a boot-gap.
When MENDER_COPY_BOOT_GAP is enabled, it will be copied from the
input disk image to the output ".sdimg"
MEN-2784
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Ubuntu Server images actually use U-boot by default on RPi3 and the
layout and naming of the files is slightly different on the boot partition.
That is why we need additional logic here to determinant what we are converting
Changelog: Add support for Ubuntu Server images on Raspberry Pi 3
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
On some RPi3 images, e.g Ubuntu Server there is no resize init script,
and these commands would fail trying to convert such an image.
This can also be useful on Raspbian images, if they have been booted
once before they are converted using "mender-convert"
Changelog: None
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
And drop the workaround.
This includes only one change:
2a8a20f01d4 Disable addition of simple-framebuffer by U-boot
Fixes: MEN-2685
Changelog: Fix "yellow" HDMI output on Raspbian Buster
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
The goals of the re-write was to achieve the following:
1. It should be easy to extend the tool to support other boards or distributions
2. We should not compile code in the tool (rely on binaries built elsewhere)
compiling code increases complexity, due to requirement of toolchains etc.
3. The tool shall not be designed around specific hardware/platform types
- This is the case today with the usage of --device-type flag
4 The tool should be to convert images without knowing anything about the hardware/platform
relates to above 3.
5. Configuration interface should be simplified
- command line flags -> configuration files
6. Platform specific code shall be provided trough “hooks”, and are not part of the “core” mender-convert code
7. It shall be easy to extend functionality
- support for rootfs overlay to inject user applications/configurations
- ability to override how the Mender Artifact is generated (to be able to sign and include state-scripts)
8. Code structure should be modular
- Eases Maintenance and possibility of making isolated changes
Changelog: Title
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
Drew Moseley
Lluis Campos
Fabio Tranchitella
Ole Petter
Mirza Krak