Hi, we've been using meta-qoriq (scarthgap) in the solution that we've been working on.
Current upstream version of TF-A project is v2.12 whereas in the meta-qoriq (scarthgap) NXP's fork is v2.10.
The thing is that, v2.12 already supports FWU Metadata v2 whereas v2.10 still uses v1. The firmware component that uses FWU Metadata to select appropriate firmware is TF-A BL2 which on the LS1028A is not updatable - I mean we could physically replace the entire image but it will not be possible once the device is shipped and deployed in the field. Once the device is released we will be able to update only FIP and other components but not BL2.
As far as I understand and seems to be logically correct - once we deploy the device with BL2 supporting FWU Metadata v1 there will be no way to switch to FWU Metadata v2 in the future releases because the old BL2 will not be able to handle the newest, v2 format, which means that we will be stuck with TF-A v2.10 and thus FWU Metadata v1 for years in order to support already deployed devices.
What can we do about it? Are there any plans to bump NXP's TF-A fork in meta-qoriq (scarthgap) to v2.12 or it's not going to happen?
Should we perhaps switch to upstream v2.12 version?
