Searched refs:enabled (Results 1 – 25 of 72) sorted by relevance
123
| /trusted-firmware-m-3.7.0/docs/configuration/ |
| D | test_configuration.rst | 57 Individual test suites can be enabled when their dependencies like partitions or
63 If regression testing is enabled by ``TEST_NS`` or ``TEST_S``, individual
64 test suites will be enabled or disabled as appropriate for the TF-M
65 configuration (i.e. all enabled secure partitions will be tested).
67 Some cryptographic tests can be enabled and disabled. This is done to prevent
|
| /trusted-firmware-m-3.7.0/platform/ext/target/nordic_nrf/common/core/ |
| D | config.cmake | 22 will trigger SecureFaults even without this option enabled. \
26 # Required if MCUBoot has been built without CONFIG_MCUBOOT_CLEANUP_ARM_CORE enabled
29 # Required if MCUboot has been built without CONFIG_MCUBOOT_NRF_CLEANUP_PERIPHERAL enabled.
|
| /trusted-firmware-m-3.7.0/platform/ext/target/arm/rse/common/ns/ |
| D | config.cmake.in | 18 …ERS @RSE_ENABLE_BRINGUP_HELPERS@ CACHE BOOL "Whether RSE bringup helpers are enabled")
21 …BLE_TRAM @RSE_ENABLE_TRAM@ CACHE BOOL "Whether TRAM encryption is enabled")
|
| /trusted-firmware-m-3.7.0/docs/releases/ |
| D | 1.8.1.rst | 9 on the PSA driver API interface in CryptoCell enabled
|
| D | 1.4.0.rst | 86 | level 2 when PXN is enabled.
111 * - | IPC Regression test fail when non-secure regression test is enabled and
|
| /trusted-firmware-m-3.7.0/secure_fw/partitions/internal_trusted_storage/ |
| D | Kconfig.comp | 26 If this option enabled, ITS_RAM_FS_SIZE must also be provided by platforms
85 ITS files is enabled
92 The size of the nonce used when ITS file encryption is enabled
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/source_structure/ |
| D | platform_folder.rst | 62 - `DAUTH_NONE`: Debugging the system is not enabled.
64 enabled.
66 code is enabled.
|
| /trusted-firmware-m-3.7.0/docs/security/security_advisories/ |
| D | debug_log_vulnerability.rst | 28 TF-M log subsystem if enabled by ``TFM_SP_LOG_RAW_ENABLED`` config option,
54 option enabled an ARoT partition can expose to the stdout device any memory
|
| D | cc3xx_partial_tag_compare_on_chacha20_poly1305.rst | 6 | | PSA driver API interface in CryptoCell enabled platforms |
16 | Configurations | CC312 enabled platforms, where the legacy driver API is |
84 For CryptoCell enabled platforms, the software component implementing the PSA
91 By default, CryptoCell enabled platforms don't build the PSA Unified Driver
|
| D | index.rst | 35 | | driver API interface in CryptoCell enabled platforms |
|
| /trusted-firmware-m-3.7.0/docs/configuration/profiles/ |
| D | tfm_profile_medium.rst | 244 .. [1] PS service is enabled by default. Platforms without off-chip storage
262 Will enable testing for all enabled partitions. See above for details of enabled
264 enabled.
319 The following PSA Crypto operationts are enabled by default.
363 ITS service is enabled in top-level Profile Medium CMake config file by default.
376 Data confidentiality, integrity and anti-rollback protection are enabled by
393 If MCUBoot provided by TF-M is enabled, multiple image boot is selected by
447 possible to build with either only TEST_S enabled or only TEST_NS enabled.
|
| D | tfm_profile_medium_arot-less.rst | 84 As PSA Certified ARoT-less requests, FWU RoT Service is enabled by default to support secure
164 enabled.
214 possible to build with either only TEST_S enabled or only TEST_NS enabled.
|
| D | tfm_profile_small.rst | 59 - Anti-rollback protection is enabled
188 Neither encryption nor rollback protection is enabled in current ITS
259 If MCUBoot provided by TF-M is enabled, single image boot [10]_ is selected by
367 In SFN model, ``-DPSA_FRAMEWORK_HAS_MM_IOVEC`` is enabled by default.
422 ITS service is enabled in top-level Profile Small CMake config file.
511 If MCUBoot provided by TF-M is enabled, single image boot is selected in TF-M
575 possible to build with either only TEST_S enabled or only TEST_NS enabled.
|
| /trusted-firmware-m-3.7.0/docs/platform/arm/rse/ |
| D | rse_provisioning.rst | 19 the RTL key reads as zero). If ``TFM_DUMMY_PROVISIONING`` is enabled in cmake
21 is not enabled, execution will pause to allow the setting to be set by a
42 enabled the reset will happen automatically, else the external provisioning
75 ``TFM_DUMMY_PROVISIONING`` enabled then it will automatically set the chip to
124 | 0x4 | CM secure provisioning started, secure provisioning mode enabled |
134 | 0x9 | DM secure provisioning started, secure provisioning mode enabled |
|
| D | readme.rst | 108 If XIP mode is enabled, the following ``fiptool`` command should be run to
127 If GPT support is enabled, and a host ``fip.bin`` and ``fip_gpt.bin`` has been
174 ``TFM_DUMMY_PROVISIONING`` enabled, BL1_1 expects provisioning bundles to be
182 when ``TFM_DUMMY_PROVISIONING`` is enabled, except that it will not
|
| /trusted-firmware-m-3.7.0/secure_fw/partitions/protected_storage/ |
| D | Kconfig | 30 enabled to protect against IV rollback.
|
| /trusted-firmware-m-3.7.0/config/ |
| D | tfm_secure_log.cmake | 13 # regression test is enabled.
|
| /trusted-firmware-m-3.7.0/docs/platform/nordic_nrf/nrf9160dk_nrf9160/ |
| D | README.rst | 64 #. When connecting a J-Link-enabled board such as an nRF9160 DK, a
104 the read back protection mechanism if enabled.
126 SECURE_UART1 is enabled by default when building TF-M on nRF9160 DK, so the secure firmware console…
|
| /trusted-firmware-m-3.7.0/docs/platform/nordic_nrf/nrf9161dk_nrf9161/ |
| D | README.rst | 64 #. When connecting a J-Link-enabled board such as an nRF9161 DK, a
104 the read back protection mechanism if enabled.
126 SECURE_UART1 is enabled by default when building TF-M on nRF9161 DK, so the secure firmware console…
|
| /trusted-firmware-m-3.7.0/platform/ext/accelerator/cc312/ |
| D | CMakeLists.txt | 138 # FixMe: Secure tests enabled and Debug builds with FP support set to hardware
152 # FixMe: Secure tests enabled and Debug builds on Musca-B1 need to fallback to
167 … message(FATAL_ERROR "CC3xx and the Legacy Crypto driver API can't be enabled at the same time.")
|
| /trusted-firmware-m-3.7.0/docs/platform/nordic_nrf/nrf5340dk_nrf5340_cpuapp/ |
| D | README.rst | 72 #. When connecting a J-Link-enabled board such as an nRF5340 DK, a drive
112 the read back protection mechanism if enabled.
135 SECURE_UART1 is enabled by default when building TF-M on nRF5340 DK, so the secure firmware console…
|
| /trusted-firmware-m-3.7.0/platform/ext/target/arm/drivers/lcm/ |
| D | lcm_drv.h | 160 enum lcm_error_t lcm_get_sp_enabled(struct lcm_dev_t *dev, enum lcm_bool_t *enabled);
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/ |
| D | platform_provisioning.rst | 36 If ``TFM_DUMMY_PROVISIONING`` is enabled in the cmake config (as it is by
59 Provisioning on CryptoCell-312 enabled platforms
|
| /trusted-firmware-m-3.7.0/docs/design_docs/software/ |
| D | code_sharing.rst | 72 Simplified steps of building with code sharing enabled:
131 RAM memory layout in MCUboot with code sharing enabled:
147 RAM memory layout in SPE with code sharing enabled:
189 enabled. The patch has no effect on the functional behaviour of the
273 If MCUboot image encryption support is enabled then saving could be up to
322 by default. It can be enabled from the command line with a compile time switch:
330 and some RSA related functions. If image encryption support is enabled in
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/services/ |
| D | tfm_manifest_tool_user_guide.rst | 66 level and Secure Partition enabled status.
121 If it is omitted, the Secure Partition is always enabled.
276 TF-M regression or PSA compliance tests are enabled.
281 The ``-q`` argument is appended if ``PARSE_MANIFEST_QUIET_FLAG`` is enabled.
|
123
