Hello mender community,
First of all, I find it necessary to say that I’ve been very impressed with mender and its integration with the Yocto project, it is extremely rugged and has saved us countless hours of development work.
My problem is an extension of the comment I placed on github regarding the new Kirkstone branch of the meta-mender-community integration layers for the raspberry pi.
I have a fleet of RPis (3B and 4B) that use mender standalone in order to preform software and OS updates. We have a custom Yocto layer that makes heavy use of the meta-mender and meta-mender-community layers and we’re very excited to make the change from Dunfell to Kirkstone as it’ll open up new recipes that will help us a lot and also needless to say, update the OS to a more recent version and all the stability that comes with that.
Our problem currently is due to the change in the default size of the
/boot partition. My understanding is that there is a need for this partition to be larger than the
dunfell default and thus a
kirkstone update applied to a
dunfell update does not work. I have tested this to be true, simply changing the branch from
kirkstone (and applying the migration considerations from Yocto), I can create an update file and run a
mender install over it in the
dunfell image. However, after commiting and rebooting, the device will not boot properly - I get no splash screen nor do I get any particularly relevant output from the screen.
By looking at this topic provided in @TheYoctoJester 's response, I can inherit
rpi-update-firmware to apply the change to the
/boot partition, however the change in default boot partition size makes the update fail since the existing
/boot partition is too small compared to the required
Now the suggestion before considering reformatting (which will inevitability be required but ideally would prefer to leave it for a later update) is to review the overlays, which I agree are not all necessary. And I guess therein lies my current question. Has anyone played around with the overlays of the
/boot partition, and would it be possible to point me in the right direction to play around with them myself? Has someone here had these issues before and has had to consider the process of reformatting who could also point me in the right direction for that?
I appreciate any answers and am open to provide any needed information, configuration files and outputs necessary. I didn’t right now since this is:
- A fairly high level question,
- I am not a very talented firmware developer or implementer and am fairly dependent on third party (hence mender) tools for these kinds of situations.