Originally the intention was to fix the U-Boot integration for
Beaglebone, but this seems to have been broken for a long time, almost
a year, and no one has complained about it. The problem appears to be
connected to this commit [1], but it's not entirely clear to me what
the fix should be, and there are a lot of patches for our U-Boot fork.
However, since the U-Boot integration is supposed to be the backup
solution, rather than dig into U-Boot I decided to just fix the UEFI
path instead. This method doesn't require any patching, but there is
a problem with the specific image which is available for download at
the time of writing. So just grab the boot loader and kernel pieces
from a later, yet unbuilt, image, and it all works again.
Changelog: Title
Changelog: beaglebone: Remove U-Boot integration, which has not worked
for a long time. U-Boot will still be used for booting, but GRUB will
be used for integration with Mender, by chainloading via UEFI.
[1] e88d5dbf01
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
(cherry picked from commit ce2b1f46cf)
This change required some changes to the current test scripts. Most notably, the
whole conversion is now run two times. One for the compressed input image, and
one for the already decompressed image.
Also, the test framework was cleaned up significantly, and the number of
arguments passed to the 'convert_and_test' function has been decreased to remove
the redundancies that were present (like passing the image name, and the image
name with the extension, in two separate parameters).
These changes are a result of the changes introduced with:
* MEN-3052: https://tracker.mender.io/browse/MEN-3052
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
This image is old enough to have a U-Boot version from before the boot
problems in MEN-2404 were introduced (>= v2018.09). At the time of
writing, no image has been released which has a U-Boot from after the
problem was fixed (> v2019.07), but we expect it will eventually be
released, and then we can bump to that version.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This is a bit unfortunate, but our converted image does not work for
all of them, like the original.
Changelog: Title
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
The current execution of the acceptance tests is too long, in some cases
reaching the GitLab timeout of this project of 2 hours.
Rework the Pipeline to use a template and rework the script to allow
running tests for only one device type.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
This makes it a bit more explicit that it is part of the testing
files. It follows the same pattern as in meta-mender with pulling
automatically, and using `--no-pull` to disable it.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This avoid problems when running the tests locally. Technically it
will run the Raspberry Pi test twice on Gitlab, once with the prebuilt
image, and once with a test image, but the two configurations are not
identical, so I reckon that's alright.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
This also means using the new mender-gitlab-tmp-storage bucket to
transfer artifacts between stages, because the built in artifact
mechanism has a size cap that we are exceeding.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
Kristian Amlie
Lluis Campos
Ole Petter
Alf-Rune Siqveland