On ODROID-H4 platform where IBECC option is enabled, the form setup overwrites
the IBECC variable despite the option is not modified in the setup. It happens
that if the IBECC option is after IBG_STATUS in DASHARO_FEATURES_DATA, the value
of the UEFI avriabel changes, which may indicate some alignment problems of the
structures in memory and how the code accesses it.
When IBECC option is before IBG_STATUS, everything works as expected. Move
the IBECC option before IBG_STATUS as a workaroudn until the root cause is found
and fixed.
Addresses issue: https://github.com/Dasharo/dasharo-issues/issues/1544
Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
The variable is being checked in DasharoCapsulesCanPersistAcrossReset().
An error from gRT->GetVariable() about missing variable is effectively
ignored (ASSERT_EFI_ERROR() does nothing) and default assumption of ME
is enabled which ended up preventing use of capsules even after
HAP-disabling ME.
Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
This causes crash on writing capsule to /dev/efi_capsule_loader in
Linux. The Print() function is asserting in this case and apparently
ends up accessing a pointer memory that was not updated on
SetVirtualAddressMap().
Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Fixes the assert happenning in OVMF when attempting to enter
setup:
GetVariableInfo(): Unknown variable: UsbPortPower.
ASSERT DasharoVariablesLib.c(198):
(0 && "No default value set for a variable.")
Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
Sergii Dmytruk
Michał Kopeć
Michał Żygowski
Wiktor Mowinski
Filip Lewiński
kamay