Hi everyone,

If you are creating out-of-tree partitions, please assign c-flag ‘CONFIG_TFM_BUILDING_SPE’ to the partitions sources.

The reason is that FFM client header is used by both SPE and NSPE clients, and SPE would support multiple ABI methods and these methods can co-exist in the system, this flag can help the partition to choose correct ABI for FFM API.

Check here for an example:

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11897/11/secure_fw/CMakeLists.txt#108

Or do you think choosing one ABI as the default ABI (default ABI owns the spec originally defined symbols) should work?

Any comments please feel free to raise.

BR.

/Ken

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M
Sent: Wednesday, October 20, 2021 3:12 PM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] [ATTENTION] SPM logic is under significant updating before End of Oct

Hi,

To support FFM 1.1 features (SFN mainly), the SPM logic is under significant updating till End of Oct, please:

- If you are doing release-targeted development, please based on the released tags.

- If you are developing with the latest master branch, please report bugs met. Our plan is to collect all bugs and fix them after this update, before the next release.

- Keen to receive your fixes and contributions. It would be very nice if you can do these.

All patches would go as a usual process, hence it should work for most of the configurations, except those not covered by the automation test. The platform related interfaces are not changing, hence no worry for platform owners.

Thanks!

/Ken