Searched refs:current (Results 1 – 25 of 52) sorted by relevance
123
| /trusted-firmware-m-3.4.0/docs/technical_references/design_docs/ |
| D | tfm_code_generation_with_jinja2.rst | 44 library is very similar to the one required by the current scripts.
49 Improvements over the current solution
52 - Compatible with Python 2.7 and Python 3, while current solution only supports
58 well established software in contrast with the current proprietary solution.
|
| D | tfm_cooperative_scheduling_rules.rst | 14 regardless of current security state of the PE, and that may lead to scheduling
54 - SPE makes a function call into NSPE (not covered in current design)
55 - NSPE returns a call from SPE (not covered in current design)
90 If the SPE context targeted by the interrupt is not same as current SPE context,
91 the SPM may choose to switch the current running SPE context based on priority.
152 3. **The current NSPE call stack has not already been returned with SPM_IDLE.**
178 3. **The current NSPE call stack has not already been returned with SPM_IDLE.**
|
| D | secure_boot_hw_key_integration.rst | 16 independently from any software components. The current key handling solution
81 to the device with the current solution. A new TLV type (TLV_KEY) can be
153 Table to compare the current and proposed solution::
|
| D | secure_boot_rollback_protection.rst | 63 was fixed in the current version. Later when this image is installed on the
109 software images should have a separate security counter. In current TF-M
140 scope for the current implementation. It is assumed that if an active image
|
| D | tfm_its_512_flash.rst | 27 In the current ITS filesystem design, each filesystem create or write operation
|
| D | tfm_uniform_secure_service_signature.rst | 16 Individual signatures - current method
|
| D | tfm_log_system_design_document.rst | 13 In current TF-M log system, the SPM and Secure partitions share the same log
|
| /trusted-firmware-m-3.4.0/secure_fw/partitions/crypto/ |
| D | dir_crypto.dox | 8 //This file holds description for the current directory. This documentation
|
| /trusted-firmware-m-3.4.0/interface/ |
| D | dir_interface.dox | 8 //This file holds description for the current directory. This documentation
|
| /trusted-firmware-m-3.4.0/docs/technical_references/design_docs/dual-cpu/ |
| D | tfm_multi_core_access_check.rst | 185 /* Compare according to current Isolation Level */
214 * Compare according to current Isolation Level and non-secure/secure
232 classified as unprivileged in current TF-M implementation. Multi-core access
367 ``tfm_spm_hal_get_mem_security_attr()`` retrieves the current active security
389 The implementation should be decoupled from TF-M current isolation level or
398 region violates current security isolation.
436 The implementation should be decoupled from TF-M current isolation level or
440 ``tfm_spm_hal_get_secure_access_attr()``, according to current active memory
445 If the target memory region is not specified in current active secure memory
456 ``false`` and set other fields according to current system-level memory region
[all …]
|
| /trusted-firmware-m-3.4.0/secure_fw/partitions/platform/ |
| D | dir_platform.dox | 8 //This file holds description for the current directory. This documentation
|
| /trusted-firmware-m-3.4.0/secure_fw/partitions/initial_attestation/ |
| D | dir_initial_attestation.dox | 8 //This file holds description for the current directory. This documentation
|
| /trusted-firmware-m-3.4.0/secure_fw/partitions/protected_storage/ |
| D | dir_protected_storage.dox | 8 //This file holds description for the current directory. This documentation
|
| /trusted-firmware-m-3.4.0/secure_fw/partitions/ |
| D | dir_services.dox | 8 //This file holds description for the current directory. This documentation
|
| /trusted-firmware-m-3.4.0/lib/ext/cryptocell-312-runtime/host/src/tests/TestAL/ |
| D | ReadMe.txt | 24 For cleaning the current config file:
|
| /trusted-firmware-m-3.4.0/docs/integration_guide/services/ |
| D | tfm_ps_integration_guide.rst | 11 access domain and, in the current version, relies on hardware to
53 - **Fragmentation** - The current design does not support fragmentation, as an
60 - **Non-hierarchical storage model** - The current design uses a
67 - **PSA internal trusted storage API** - In the current design, the service does
73 is not supported by the current design.
83 - **Provisioning vs user/device data** - In the current design, all assets are
177 The current PS service provides rollback protection based on NV
295 TF-M core tracks the current client IDs running in the secure or non-secure
|
| D | tfm_its_integration_guide.rst | 16 The current ITS service design relies on hardware abstraction provided by TF-M.
47 - **Fragmentation** - The current design does not support fragmentation, as an
55 - **Non-hierarchical storage model** - The current design uses a
64 is not supported by the current design.
71 - **Provisioning vs user/device data** - In the current design, all assets are
|
| D | tfm_secure_partition_addition.rst | 90 The current manifest format in TF-M is "yaml" which is different from the
213 number in the range [1, 32] in current implementation and may extend. Also the
260 needs access to. TF-M only supports the ``named_region`` current. Please refer
276 This structure is not expected by TF-M, it's only that the current
311 The current CMake configuration should also be updated, by updating
|
| D | tfm_crypto_integration_guide.rst | 56 for multipart operations (8 for the current implementation). For multipart
|
| /trusted-firmware-m-3.4.0/ |
| D | CMakeLists.txt | 14 # It is aligned with current Armclang toolchain implementation.
|
| /trusted-firmware-m-3.4.0/docs/platform/nxp/lpcxpresso55s69/ |
| D | README.rst | 341 | ``until <n>`` | Run until source line ``n`` in the current file |
343 | ``info locals`` | Display the local variables and their current values |
345 | ``bt`` | Display a stack backtrace up to the current function |
|
| /trusted-firmware-m-3.4.0/docs/integration_guide/ |
| D | non-secure_client_extension_integration_guide.rst | 87 context number based on the current available resource in TF-M. If
188 - `tfm_nsce_save_ctx()` should be called if the current task has a valid
190 for another task before saving the current context may result in NS context
|
| D | tfm_fpu_support.rst | 22 current stage.
|
| D | index.rst | 112 With the current implementation, a NSPE task can spoof the identity of another
|
| /trusted-firmware-m-3.4.0/docs/configuration/ |
| D | kconfig_system.rst | 92 - Due to the current limitation of the tool, you are not allowed to change the values of build
|
123
