UEFI Capsule update proposal 1. Why do we need this? Today Mender has no ability to update System Firmware. Whole firmware single image updates will be a step forwards from today’s firmware update capability, but the end goal should be to support partial firmware updates where only one part of the i…

Tagging: @GowthamSK Thanks for reviewing and tagging the necessary members. [image] kacf: One comment about naming You describe the --no-default-software-version flag, but in your command you have --no-default-clears-provides. I would recommend that you remove both, and instead use --software-…

Just a clarification first, I made a mistake above: When I said uefi-firmware.edk2.name, I meant uefi-firmware.edk2.version. Sorry about that. [image] jainvikas8: Considering your suggestion: I think the idea to use this kind of format uefi-firmware.<firmware name>.<GUID of the firmware>:<versi…

Thanks for the reply. < firmware name > is just an alias and can be the same (very low probability), as people can decide what they want to call it. On the other hand <GUID> is unique, in that way 1:1 relationship can be established. [image] kacf: uefi-firmware.<firmware name>.<GUID of the fi…

[image] jainvikas8: This should be good, but .version anyways is implied? so we could ignore that, therefore avoiding the complexity of having multiple fields. .version has a special meaning in the UI. That’s why I keep suggesting it. :slightly_smiling_face: [image] jainvikas8: uefi-firm…

[image] kacf: Note the verbatim version in there. This is important for clear-provides to work correctly. But I think it will not render correctly in the UI, because it does not yet support multi-level software versions (this is coming though). Could you please link the issue? Will update the…

It’s this one: [MEN-5875] UI: Implement support for more than three levels of software provides - Northern.tech AS .

It will work in your proposed variant though, because it has three levels, which is already supported.

Hi @kacf . Thanks for your input. I tried both the naming conventions discussed above and found the following, (Please note we are using Mender Server Version: 3.1.0) Separate name and version uefi-firmware.GUID.version: v1 uefi-firmware.GUID.name: edk2 Sample Mender server view: [image] S…

Oh my apologies, I thought this would render correctly, but it appears that there is special handling in the UI for rootfs-image, but not for other software components. However, I spoke to our UI developer and he confirmed that this will be fixed in https://tracker.mender.io/browse/MEN-5875 , which …

@GowthamSK take a look at this pull request which has screenshots. We used your use case as inspiration! It’s being worked on right now, so maybe you can comment directly in there if you see something which doesn’t align with what you expect.

Design proposal: UEFI Capsule support

General Discussions

kacf November 7, 2022, 7:29am 18

Looks good to me! I have updated Apply preexisting provides to compiled mender uefiimg image - #11 by kacf.

Topic		Replies	Views
How to get information about additional artifact in to the mender blob General Discussions tegra , uefi	0	44	September 1, 2025
Simple configuration (dunfell) General Discussions	29	2701	March 9, 2021
Update Fails General Discussions	8	1752	March 4, 2021
Robust delta update rootfs Update Modules	14	9995	December 11, 2025
Issues with UBIFS, rebooting and dashboard General Discussions nxp , buildroot , ubifs	25	1824	October 8, 2020

Design proposal: UEFI Capsule support

Related topics