Hi,

How does TF-M consider Product Lifecycle Management (PLM)?

Assuming the following scenario where TF-M and Non-Secure Application are independently developed/updated in a deployed system:

* TF-M is delivered i.e. by a silicon vendor in a pre-configured variant and Non-Secure Application starts to use this configuration. * During PLM there is a decision to update/upgrade/downgrade TF-M. The new image is pushed to deployed devices independent of Non_Secure application.

Questions that I have:

* Is there a way for the Non-Secure application to identify the functionality available in TF-M? * How is it ensured that new TF-M versions are compatible with previous versions?

Reinhard