uImage is not a valid target for aarch64/arm64 in the kernel (like it is for arm). This is because "uImage" is actually shorthand for u-boot wrapped zImage. And arm64 does not have support for zImage, thus also does not have a uImage target.
(Credit to Nathan Rossi)
So my question is, is possible at all to use Mender? If yes, how?
Would it be possible to generate the OS normally with Yocto and as postbuild steps to manually generate a uImage with mkimage?
Regards,
David Bensoussan
Synapticon GmbH
Hello,I am working with a rpi3 64 bits. The reason is I have software that just doesn't work in 32.I tested mender in 32 bits using Yocto and could use the update without problems.The issue I'm encountering is that, from what I read, there's no uImage support for arm64 and as it is i the documentation,uImage is not a valid target for aarch64/arm64 in the kernel (like it is for arm). This is because "uImage" is actually shorthand for u-boot wrapped zImage. And arm64 does not have support for zImage, thus also does not have a uImage target.(Credit to Nathan Rossi)So my question is, is possible at all to use Mender? If yes, how?
I tested generating an image for the rpi3-64. Somehow the sdimg is not built and IMAGE_FSTYPES doesn't include sdimg. I am using the same environment and configuration than the rpi3, with upstream meta-raspberrypi layer
Thanks for the answer. I have many include files and nothing in the local.conf. That would have been long to copy. I'm using sumo by the way.I actually found out it was in the meta-mender layer. In mender-full.bbclass
This was needed:
MENDER_FEATURES_ENABLE_append_aarch64 = " mender-image-sd mender-uboot"
I am still testing and will do a PR in the next days once I am sure everything is working