Hi, folks.
This is perhaps a little off the beaten path, but I’m hoping to migrate from a yocto build to a mender-convert process for deploying to a fleet of Raspberry Pi 4s. I realize there’s an advantage to having a more optimized deploy image from yocto, but the iteration cycle of making changes in yocto is agonizing compared to using standard linux tools to create a golden image. Plus, we’re running Chromium on these Pis, and no amount of tweaking of the build settings seems to create a Chromium that performs as well and makes full use of the GPU as the one that ships for Debian.
It’s really undesirable to install new SD cards in all the devices that are out there, so the hope is very much to be able to send an OTA image update that will just drop into the inactive partition and boot up into the “new way”. I’ve got things mostly together, I think, but when I test an update locally I run into some boot errors that are exposing areas of my ignorance about how the boot process works with Mender.
When I just install the OTA image with mender-update, the subsequent startup fails looking for a nonexistent “/boot/Image”. I feel like with a little more knowledge, this would be simple to solve! Is it just a matter of needing a step such as exists in meta-raspberry pi to update firmware? I spent way too long banging my head against various yocto obstacles, and it would be fantastic to have a process that works smoothly - it feels very close.
Thanks!