Good afternoon,
Linaro and Arm have been standardizing the FW update mechanism for A-class devices.
The intention behind the standardization is to enable generic implementations of the UEFI UpdateCapsule where: 1) the FW store resides in Secure World controlled flash; 2) there is FW bank duplication (A/B model).
Arm published a specification, at Alpha quality, that defines the FW update model and a set of tools catering for 1) and 2) : https://developer.arm.com/-/media/Files/pdf/FWU-PSA-A_DEN0118_1.0ALP3.pdf
Arm welcomes feedback on the specification. Please direct feedback to either myself or Grant Likely
The FW update work will be discussed at the EBBR biweekly call this Monday (26th April).
Regards,
Jose
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 23.04.21 13:51, Jose Marinho wrote:
Good afternoon,
Linaro and Arm have been standardizing the FW update mechanism for A-class devices.
The intention behind the standardization is to enable generic implementations of the UEFI UpdateCapsule where:
the FW store resides in Secure World controlled flash;
there is FW bank duplication (A/B model).
Arm published a specification, at Alpha quality, that defines the FW update model and a set of tools catering for 1) and 2) : https://developer.arm.com/-/media/Files/pdf/FWU-PSA-A_DEN0118_1.0ALP3.pdf https://developer.arm.com/-/media/Files/pdf/FWU-PSA-A_DEN0118_1.0ALP3.pdf
Arm welcomes feedback on the specification. Please direct feedback to either myself or Grant Likely
The FW update work will be discussed at the EBBR biweekly call this Monday (26^th April).
Regards,
Jose
Thank you for sharing this document.
Looking at the license this is a generic API definition that is not bound to TF-A but might also be implemented on non-TF-A and non-ARM platforms. - Do I get this right?
From the view of non-secure firmware like U-Boot or EDK II having a cross-platform specification is preferable.
Best regards
Heinrich
On 23/04/2021 13:41, Heinrich Schuchardt wrote:
On 23.04.21 13:51, Jose Marinho wrote:
Good afternoon,
Linaro and Arm have been standardizing the FW update mechanism for A-class devices.
The intention behind the standardization is to enable generic implementations of the UEFI UpdateCapsule where:
the FW store resides in Secure World controlled flash;
there is FW bank duplication (A/B model).
Arm published a specification, at Alpha quality, that defines the FW update model and a set of tools catering for 1) and 2) : https://developer.arm.com/-/media/Files/pdf/FWU-PSA-A_DEN0118_1.0ALP3.pdf https://developer.arm.com/-/media/Files/pdf/FWU-PSA-A_DEN0118_1.0ALP3.pdf
Arm welcomes feedback on the specification. Please direct feedback to either myself or Grant Likely
The FW update work will be discussed at the EBBR biweekly call this Monday (26^th April).
Regards,
Jose
Thank you for sharing this document.
Looking at the license this is a generic API definition that is not bound to TF-A but might also be implemented on non-TF-A and non-ARM platforms. - Do I get this right?
From the view of non-secure firmware like U-Boot or EDK II having a cross-platform specification is preferable.
Correct. The Arm non-confidential document is not restricted to Arm-based designs.
g. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
boot-architecture@lists.linaro.org
-
Grant Likely -
Heinrich Schuchardt -
Jose Marinho