blob: 4d8452f3567b2c7b71c8732272ba4ab0bc32b614 [file] [log] [blame]
Julian Halle76ade82020-11-25 03:07:21 +01001Change Log & Release Notes
2==========================
3
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +01004This document contains a summary of the new features, changes, fixes and known issues in each release of Trusted
5Services.
Julian Halle76ade82020-11-25 03:07:21 +01006
Gyorgy Szing08129852024-04-06 08:16:29 +02007Version <next>
8--------------
9
10- Trustedfirmware.org has deprecated Phabricator, the wiki and issue tracking provider. This functionality has been
11 moved to GitHub. See the `Trusted Services organization`_. The project wiki has been moved
12 `to here <https://github.com/Trusted-Services/trusted-services/wiki>`_
13
14
15Feature Highlights
16^^^^^^^^^^^^^^^^^^
17
18- Add documentation covering the :ref:`OP-TEE SPMC tests`.
Gyorgy Szingc6450a02024-10-28 10:44:29 +010019- :ref:`UEFI SMM Services`:
20
21 - Extend the implementation to support Authenticated Variables.
22 - Relax the UEFI variable name length limit imposed by the size of the RPC buffer.
23
Gyorgy Szing08129852024-04-06 08:16:29 +020024- Introduce a work in progress RPMB implementation and integrate it to the Block Storage service. The current
25 configuration uses an SWd RAM buffer for data storage, and is not connected to the RPMB provider running in the NWd.
26 This is the first baseline to implement a scenario where the RPMB owner is an S-EL0 SP.
27- Introduce the :ref:`Logging Service`.
28- Add crypto key store partitioning support to the Crypto Service. This feature allows isolating clients running in
29 different SPs.
Gyorgy Szinge6b38462024-10-24 17:36:45 +020030- Add the "RSE Com" protocol. RSE Com is a new protocol used between secure partitions and security subsystems like the
31 Secure Enclave on Corstone-1000 or Runtime Security Engine on `RD-1 AE`_.
Gyorgy Szingc6450a02024-10-28 10:44:29 +010032- libsp learnt to support FF-A v1.1 and all SPs are updated to use this version.
33- tstee Linux driver was merged upstream and the LinuxFfaTEEDriver external component is removed.
34- All SP and arm-linux deployments are updated to support Armv8.5-A Branch Protection feature.
35 See: :ref:`branch_protection`
36- A new FWU agent implementation is introduced, which implements a `PSA Certified Firmware Update API 1.0`_ client. This
37 component can be used to implement an FWU proxy on A+M systems like Corstone1000 and RD-1 AE. For more details see:
38 :ref:`Firmware update on A+M systems`
39- A new shared library called ``libpsats`` is introduced to help integration of PSA clients to 3rd party linux
40 user-space projects. For details see: :ref:`libs-libpsats`
41- The following new tests and enhancements have been added to :ref:`OP-TEE SPMC tests`:
Gyorgy Szing4a0829d2024-04-19 09:34:53 +020042
Gyorgy Szingc6450a02024-10-28 10:44:29 +010043 - FFA_MEM_PERM_GET/SET tests.
44 - Memory sharing test updated to cover invalid requests.
45 - VM availability message tests.
46 - Endpoint ID checking is fixed.
Gyorgy Szing4a0829d2024-04-19 09:34:53 +020047
48Deprecations
49^^^^^^^^^^^^
50
51- This OpenAMP based psa_ipc implementation is deprecated and will be removed in the future.
52
Gyorgy Szing08129852024-04-06 08:16:29 +020053
54Updated external components
55^^^^^^^^^^^^^^^^^^^^^^^^^^^
56
Gyorgy Szingc6450a02024-10-28 10:44:29 +010057- MbedTLS version in the Crypto service is updated to v3.6.0.
Gyorgy Szing4a0829d2024-04-19 09:34:53 +020058- NanoPB has been upgraded to v0.4.8.
Gyorgy Szingc6450a02024-10-28 10:44:29 +010059- Newlib is no longer required and the newlib external component is removed.
Gyorgy Szing08129852024-04-06 08:16:29 +020060
61Breaking changes
62^^^^^^^^^^^^^^^^
63
Gyorgy Szing4a0829d2024-04-19 09:34:53 +020064
Gyorgy Szing08129852024-04-06 08:16:29 +020065Resolved issues
66^^^^^^^^^^^^^^^
67
68- Fix psa-ps-api-test test case 414.
69- Crypto key store partitioning has been implemented, and clients accessing the crypto service from different FF-A
70 endpoints can not access each other's assets anymore.
71
72Known limitations
73^^^^^^^^^^^^^^^^^
74
Gyorgy Szingc6450a02024-10-28 10:44:29 +010075None.
Gyorgy Szing08129852024-04-06 08:16:29 +020076
Gyorgy Szing30731ce2023-09-27 12:24:18 +020077Version 1.0.0
78-------------
79
80The first stabilised release of the project from previously prototype releases ready for product use.
81
82Feature Highlights
83^^^^^^^^^^^^^^^^^^
84
85- Introduce the :doc:`Block Storage Service </services/block-storage-service-description>`. The Block Storage service
86 can be used to share a block-oriented storage device such as a QSPI flash between a set of independent secure world
87 clients.
88
89- Introduce the :doc:`Firmware Update Service </services/fwu/index>`. The FWU service implements the Update Agent
90 defined in the `Arm FWU-A specification`_ and allows replacing FW components with newer versions.
91
92- Refactor FF-A UUID policy. Reinterpret the FF-A UUID to identify the protocol supported by TS SP instead of the
93 service. This removes the maintenance burden of keeping an up to date UUID list in the service locator. All SPs start
94 using the same protocol UUID, and implement a new discovery service (see the next point).
95
96- Overhaul the RPC protocol. The main driver is to remove the single shared memory region limitation, which does not
97 allow separating shared regions of clients running over Linux in the user-space. The second driver is to add
98 versioning support to the RPC layer.
99
100 - Allow multiple shared memory regions between endpoints.
101 - Implement the discovery service in the RPC layer.
102 - Allow assigning a UUID to interfaces. This mechanism replaces the protocol identifier used earlier. Each protocol
103 of a service is represented as a dedicated interface.
104 - Add versioning support to the RPC layer.
105
106- Refactor the discovery service. The is removing the runtime overhead of memory sharing during the discovery and
107 decreases code size and duplication using the same code for service discovery.
108
109 - Implement the discovery service in the RPC layer for efficiency reasons.
110 - Implement service identity discovery for all services.
111 - Remove the encoding type entity and use service UUIDs to represent the serialization type.
112 - Service property discovery is to be implemented in the future.
113
Gyorgy Szingc6450a02024-10-28 10:44:29 +0100114- Add support for the Corstone-1000 platform. For more information about this platform please see:
115 `Corstone-1000 product homepage`_
Gyorgy Szing30731ce2023-09-27 12:24:18 +0200116
Gyorgy Szingc6450a02024-10-28 10:44:29 +0100117- SPs now indicate support of :term:`Normal World` interrupt preemption capability in their SP manifest and allow the
118 SPMC to enable preemption if possible. This removes NWd interrupts being disabled for long periods due to long service
119 calls.
Gyorgy Szing30731ce2023-09-27 12:24:18 +0200120
121- Add support for the Armv8-A CRC32 feature for :term:`Secure World` and :term:`Normal World` components.
122
123- Extend FF-A support with:
124
125 - FF-A v1.1 boot protocol between the SPM and SPs.
126 - FF-A v1.2 FFA_CONSOLE_LOG call. This allows SPs to emit log messages in an SPMC agonistic way.
127
128- Improve the build system to allow setting the build steps of external components to be verbose.
129
130- Add support for runtime (dynamic) psa-acs test case configuration.
131
132Updated external components
133^^^^^^^^^^^^^^^^^^^^^^^^^^^
134
135- MbedTLS version integration into the Crypto service is updated to v3.4.0.
136- The PSA Arch test is updated to version `74dc6646ff594e131a726a5305aba77bac30eceb`.
137
138Breaking changes
139^^^^^^^^^^^^^^^^
140
141- The new RPC ABI is not backwards compatible and needs recent version of all depending components.
142
143Resolved issues
144^^^^^^^^^^^^^^^
145
146- The new RPC version allows having multiple shared memory regions between endpoints. This allows each NWd client
147 running in Linux user-space to use a dedicated buffer.
148
149Known limitations
150^^^^^^^^^^^^^^^^^
151
152 - Crypto key store partitioning by client is not yet supported. This means multiple clients running at the same FF-A
153 endpoint use a shared key space.
154 - The full firmware update process implementation and testing is work-in-progress. The FWU process relies on the
155 cooperation of multiple FW components owned by multiple FW projects. Some 3rd party components do not implement the
156 needed features yet and thus, the FWU service was validated in "isolation" and exercised by TS test on the FVP
157 platform and on the host PC only.
158 - Service property discovery is not implemented yet.
159 - Discovering the maximum payload size of a service is not supported yet and buffer sizes are hardcoded.
160
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100161Version 1.0.0-Beta
162------------------
Julian Halle76ade82020-11-25 03:07:21 +0100163
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100164The first tagged release of the project.
Julian Halle76ade82020-11-25 03:07:21 +0100165
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100166Feature Highlights
167^^^^^^^^^^^^^^^^^^
Julian Halle76ade82020-11-25 03:07:21 +0100168
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100169The project supports the following services:
Julian Halle76ade82020-11-25 03:07:21 +0100170
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100171 - Secure Storage
172 - Crypto
173 - Initial Attestation
174 - Smm Variable
175
Gyorgy Szingc6450a02024-10-28 10:44:29 +0100176Services may be accessed using client components that implement "`Psacertified v1.0 APIs`_". The project includes
177deployments that integrate `PSA API certification tests`_ with API clients to facilitate end-to-end PSA certification
178testing.
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100179
180Known limitations
181'''''''''''''''''
182
183 - Crypto key store partitioning by client is not yet supported.
184 - Discovery support is only currently integrated into the Crypto service provider. In case of services not supporting
185 this feature yet, communication parameters (e.g. maximum buffer size) and supported feature set needs to be hardcode
186 to the service provider and service client.
187
188Supported Trusted Environments
189''''''''''''''''''''''''''''''
190
191In the default configuration each service is deployed to a dedicated FF-A Secure Partition and executes isolated.
192Service implementations are platform, trusted environment and service deployment agonistic. With appropriate enablement
193work services can be enabled to work in any combination of these.
194
195The reference integration uses the SPMC implemented in OP-TEE OS to manage TS SPs. This release supports `OP-TEE v3.19`_.
196
197Supported Integration Systems
198'''''''''''''''''''''''''''''
199
Gyorgy Szingc6450a02024-10-28 10:44:29 +0100200The reference solution uses the OP-TEE integration methodology. This relies on the google repo tool for high-level
201dependency management and a set of makefiles to capture the build configuration information. For details please refer to
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100202`OP-TEE git repo documentation`_.
203
204The project is officially enabled in `Yocto meta-arm`_.
205
206Supported Target Platforms
207''''''''''''''''''''''''''
208
209The only reference platform supported by this release is the `AEM FVP`_ build using the OP-TEE integration method.
210
211Known limitations:
212
213 - Non-volatile backend secure storage is not currently provided.
214
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100215Test Report
216^^^^^^^^^^^
217
Imre Kis92eeced2024-01-31 13:38:57 +0100218Please find the Test Report covering this release in the `project wiki`_.
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100219
220
Julian Halle76ade82020-11-25 03:07:21 +0100221--------------
222
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100223.. _`FF-A Specification v1.0`: https://developer.arm.com/documentation/den0077/a
224.. _`Psacertified v1.0 APIs`: https://www.psacertified.org/development-resources/building-in-security/specifications-implementations/
225.. _`OP-TEE v3.19`: https://github.com/OP-TEE/optee_os/tree/3.19.0
226.. _`Yocto meta-arm` : https://gitlab.oss.arm.com/engineering/yocto/meta-arm/-/tree/master/meta-arm/recipes-security/trusted-services
Imre Kis92eeced2024-01-31 13:38:57 +0100227.. _`project wiki`: https://github.com/Trusted-Services/trusted-services/wiki/Trusted-Services-test-reports
Gabor Toth4fc6d9e2024-07-12 10:09:18 +0200228.. _`AEM FVP`: https://developer.arm.com/-/media/Files/downloads/ecosystem-models/FVP_Base_RevC-2xAEMvA_11.22_14_Linux64.tgz
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100229.. _`PSA API certification tests`: https://github.com/ARM-software/psa-arch-tests
230.. _`OP-TEE git repo documentation`: https://optee.readthedocs.io/en/latest/building/gits/build.html
Gyorgy Szing30731ce2023-09-27 12:24:18 +0200231.. _`Corstone-1000 product homepage`: https://developer.arm.com/Processors/Corstone-1000
232.. _`Arm FWU-A specification`: https://developer.arm.com/documentation/den0118
Gyorgy Szing08129852024-04-06 08:16:29 +0200233.. _`Trusted Services organization`: https://github.com/Trusted-Services
Gyorgy Szinge6b38462024-10-24 17:36:45 +0200234.. _`RD-1 AE`: https://developer.arm.com/Tools%20and%20Software/Arm%20Reference%20Design-1%20AE
Gyorgy Szingc6450a02024-10-28 10:44:29 +0100235.. _`PSA Certified Firmware Update API 1.0`: https://arm-software.github.io/psa-api/fwu/1.0/
Gyorgy Szing0b8b4fa2022-11-17 13:00:45 +0100236
Imre Kis92eeced2024-01-31 13:38:57 +0100237*Copyright (c) 2020-2024, Arm Limited and Contributors. All rights reserved.*
Julian Halle76ade82020-11-25 03:07:21 +0100238
239SPDX-License-Identifier: BSD-3-Clause