1:orphan:
2
3*************
4Version 1.2.0
5*************
6
7New features
8============
9
10  - A new build system based on Modern CMake.
11  - First implementation of level 3 isolation on Musca-B1 and AN521.
12  - Remove MCUBoot fork from TF-M.
13  - Move test and app code to tf-m-tests repo.
14  - Add Profile Medium.
15  - Migrate support to Mbed TLS v2.24.
16  - New platforms added.
17    See :ref:`releases/1.2.0:New platforms supported` for
18    details.
19  - New SPM HAL APIs including isolation API and logging API.
20  - Update MCUboot version to 1.7.0-rc1.
21  - Initial ITS/PS HAL for dynamic filesystem configuration.
22  - Remove auto-generated files from the source tree.
23
24New security advisories
25=======================
26
27Stack sealing
28-------------
29
30Refer to :doc:`Advisory TFMV-1</security/security_advisories/stack_seal_vulnerability>`
31for more details.
32A common mitigation is included in this release.
33
34New platforms supported
35=======================
36
37- Cortex-M33 based system:
38
39  - `Nordic nRF9160 DK (nordic_nrf/nrf9160dk_nrf9160).
40    <https://www.nordicsemi.com/Products/Development-hardware/nrf9160-dk>`_
41  - `Nordic nRF5340 PDK (nordic_nrf/nrf5340pdk_nrf5340_cpuapp).
42    <https://www.nordicsemi.com/Products/Development-hardware/nrf5340-pdk>`_
43  - `Nordic nRF5340 DK (nordic_nrf/nrf5340dk_nrf5340_cpuapp).
44    <https://www.nordicsemi.com/Products/Development-hardware/nrf5340-dk>`_
45
46- Cortex-M23 based system:
47
48  - `Nuvoton M2351.
49    <https://www.nuvoton.com/products/iot-solution/iot-platform/numaker-pfm-m2351/>`_
50
51- Cortex-M55 based system:
52
53  - `Corstone-300 Ethos-U55 FVP (Cortex-M55 plus Ethos-U55 SSE-300 MPS3).
54    <https://developer.arm.com/Processors/Corstone-300#Tools-and-Software>`_
55
56Tested platforms
57================
58
59The following platforms are successfully tested in this release.
60
61 - AN519
62 - AN521
63 - Musca-B1
64 - MPS2 SSE300
65 - PSoC 64
66 - M2351
67 - nrf5340dk
68 - nrf5340pdk
69 - nrf9160dk
70 - LPCXpresso55S69
71 - NUCLEO-L552ZE-Q
72 - STM32L562E-DK
73
74Known issues
75============
76
77Some open issues exist and will not be fixed in this release.
78
79.. list-table::
80
81  *  - **Descriptions**
82     - **Issue links**
83
84  *  - | PSA Arch Crypto tests have several known failures.
85     - See this link for detailed analysis of the failures:
86       https://developer.trustedfirmware.org/w/tf_m/release/psa_arch_crypto_test_failure_analysis_in_tf-m_v1.2_release/
87
88Issues fixed since 1.1
89======================
90
91Issues fixed by TF-M since v1.1 are listed below.
92
93.. list-table::
94
95  *  - **Descriptions**
96     - **Issue links**
97
98  *  - | The eflash driver on Musca-B1 can return random failures hence
99       | triggering random failures during PSA Arch ITS and PSA Arch PS tests.
100       | This happens when ITS/SST is configured to use flash.
101     - https://developer.trustedfirmware.org/T697
102
103Issues closed since 1.1
104=======================
105
106The following issues are closed since v1.1. These issues are related to platform
107hardware limitations or 3rd-party tools and therefore won't be fixed by TF-M.
108
109.. list-table::
110
111  *  - **Descriptions**
112     - **Issue links**
113
114  *  - | All the supported GNUARM toolchain versions generate corrupt veneer
115       | code for Armv8-M baseline architecture, when the -Os optimization flag
116       | is used. This affects the Armv8-M baseline platforms built with GNUARM
117       | toolchain and Minsizerel build type.
118       | It relies on an official release of GNUARM toolchain to fix this issue.
119     - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95646
120
121  *  - | AN521 FVP soft reset via AIRCR does not reset MPC / PPC / MPU and will
122       | cause boot failure. This is a known issue for AN521 FVP. This will
123       | cause the system to fail to boot after a warm reset during PSA Arch FF
124       | testing.
125     - https://developer.trustedfirmware.org/T692
126
127  *  - | There are 2 additional failures for PSA-Arch Crypto tests with CC-312
128       | other than the known failures. This is due to limitation of CC-312
129       | implementation as it does not support MD_NONE hashing mode causing the
130       | additional failures.
131     - https://developer.trustedfirmware.org/T691
132
133  *  - | Boot up fails if there is unexpected data in flash on Musca-A. The boot
134       | is successful and the tests pass if all the associated (PS/ITS/NV
135       | Counter) flash areas are erased.
136     - https://developer.trustedfirmware.org/T694
137
138  *  - | If the flash is not erased, boot fails on Musca-B1 when SST is using
139       | flash for Minsizerel config.
140     - https://developer.trustedfirmware.org/T695
141
142--------------
143
144*Copyright (c) 2020-2021, Arm Limited. All rights reserved.*
145