Lines Matching +full:runs +full:- +full:on

4 services in Trusted Firmware M(TF-M) through Platform Security Architecture
5 (PSA) API based on the ARM Cortex-M23, Cortex-M33, Cortex-M55 and Cortex-M85
10 …ource Page](https://developer.arm.com/architectures/security-architectures/platform-security-archi…
12 TF-M is an open source project. It provides a reference implementation of PSA
13 for Arm M-profile architecture. Please get the details from this [link](https://git.trustedfirmware…
18 …The implementation of APIs which are defined in ```\ns_interface\os_wrapper\mutex.h``` by tf-m-tes…
19   (tag: TF-Mv1.5.0 & TF-Mv1.6.0). The implementation is based on FreeRTOS mutex type semaphore.
23 To build a project based on this port:
25 * Step 2: build the nonsecure image. Please follow the **Build the Non-Secure Side** for details.
29 ### Get the TF-M source code
31 …firmware.org/TF-M/trusted-firmware-m.git/) to get the source code. This port is supported by TF-M …
33 ### Build TF-M
36 _**Note:** ```TFM_NS_MANAGE_NSID``` must be configured as "OFF" when building TF-M_.
38 ## Build the Non-Secure Side
40 …fore using this port. Note that TrustZone is enabled in this port. The TF-M runs in the Secure Sid…
42 …e API ```tfm_ns_interface_init()``` which is defined in ```\app\tfm_ns_interface.c``` by tf-m-tests
43 (tag: TF-Mv1.5.0 & TF-Mv1.6.0) at the very beginning of your application. Otherwise, it will always…
48 This macro should be configured as 0. In this port, TF-M runs in the Secure Side while FreeRTOS
49 Kernel runs in the Non-Secure Side.
52 The setting of this macro is decided by the setting in Secure Side which is platform-specific.
53 If the Secure Side enables Non-Secure access to FPU, then this macro can be configured as 0 or 1. O…
54 Please note that Cortex-M23 does not support FPU.
55 … refer to [TF-M documentation](https://tf-m-user-guide.trustedfirmware.org/integration_guide/tfm_f…
58 The setting of this macro is decided by the setting in Secure Side which is platform-specific.
59 If the Secure Side enables Non-Secure access to MVE, then this macro can be configured as 0 or 1. O…
60 Please note that only Cortex-M55 and Cortex-M85 support MVE.
61 … refer to [TF-M documentation](https://tf-m-user-guide.trustedfirmware.org/integration_guide/tfm_f…
64 …s 0 because TF-M doesn't use the secure context management function of FreeRTOS. New secure contex…
67 ### Integrate TF-M Non-Secure interface with FreeRTOS project
69 To enable calling TF-M services by the Non-Secure Side, the files below should be included in the F…
70 * files in ```trusted-firmware-m\build\install\interface\src```
71 … be called by Non-Secure Side directly and PSA Firmware Framework APIs in the IPC model. These fil…
72 * files in ```trusted-firmware-m\build\install\interface\include```
73   These files are the necessary header files to call TF-M services.
74 * ```trusted-firmware-m\build\install\interface\lib\s_veneers.o```
75   This object file contains all the Non-Secure callable functions exported by
76   TF-M and it should be linked when generating the Non-Secure image.
80 *Copyright (c) 2020-2022, Arm Limited. All rights reserved.*