Re: [cip-dev][isar-cip-core][PATCH] fix: Disable bootloader interaction in case of ebg only updates

[Quirin Gylstorff <quirin.gylstorff@siemens.com>]

On 2/19/26 1:50 PM, Jan Kiszka wrote:
> On 19.02.26 13:36, Quirin Gylstorff wrote:
>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>
>> During an update of the efibootguard binary the boot entries should
>> not be changed. Therefore disable the boot-loader state and transition
>> update.
>>
>> This was found during testing for issue #149.
>>
>> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>> ---
>>   recipes-core/images/swu/sw-description-ebg.tmpl | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/recipes-core/images/swu/sw-description-ebg.tmpl b/recipes-core/images/swu/sw-description-ebg.tmpl
>> index c19157c..a63e38a 100644
>> --- a/recipes-core/images/swu/sw-description-ebg.tmpl
>> +++ b/recipes-core/images/swu/sw-description-ebg.tmpl
>> @@ -12,6 +12,8 @@ software =
>>   {
>>       version = "${SWU_VERSION}";
>>       name = "${SWU_NAME}";
>> +    bootloader_transaction_marker = false;
>> +    bootloader_state_marker = false;
> 
> So we need to set both to false to avoid the SWUpdate talks to EBG, and
> one does not influence the other (although there is only one state in EBG)?

According to 
https://sbabic.github.io/swupdate/suricatta.html#update-activation yes.

Quirin
> 
> Jan
> 
>>       ${SWU_HW_COMPAT_NODE}
>>       files: (${SWU_BOOTLOADER_FILE_NODE});
>>   }
>