Searched refs:then (Results 1 – 25 of 93) sorted by relevance
1234
| /trusted-firmware-m-3.6.0/docs/configuration/ |
| D | build_configuration.rst | 16 3. If TEST_PSA_TEST is set, then PSA API test related config is applied from
22 6. If CRYPTO_HW_ACCELERATOR is set, then a config specific to the
28 ``TEST_NS_ATTESTATION`` (see :ref:`test_configuration`) is set, then
38 settings (this is not usually a good idea) then TFM_EXTRA_CONFIG_PATH should be
|
| /trusted-firmware-m-3.6.0/docs/integration_guide/ |
| D | platform_provisioning.rst | 10 is the default for non-provisioned boards), then TF-M will attempt to provision
14 ``assembly_and_test_prov_data`` struct, and will then provision it to OTP. The
15 lifecycle state will then transition to ``TFM_SLC_PSA_ROT_PROVISIONING`` [1]_.
18 then TF-M will attempt to provision the:
78 then it can provide a backing for the OTP HAL by implementing the methods
|
| D | spm_backends.rst | 67 requires isolation level 1, then it is recommended to select the SFN backend
71 isolation level 2 or 3, then the IPC backend is required.
84 If ``CONFIG_TFM_SPM_BACKEND`` is not set, then ``IPC`` is the default value.
|
| /trusted-firmware-m-3.6.0/docs/design_docs/booting/ |
| D | secure_boot_rollback_protection.rst | 30 well. If the new image is successfully authenticated then the boot loader is in
64 device then it is not allowed to go back to earlier versions. It is beneficial
69 counter has the same value in the older image then it is accepted.
70 - If the boot loader verifies multiple images then these can be handled
129 secure image then the following threat is unmitigated: The content of the
133 - If the boot loader does not trust the loaded image at all then security
141 and related manifest data is stored in trusted memory then the included
149 corresponding manifest) then the value of security counter must be copied to
155 active software then it is not mandatory to store the security counter to
180 If non-volatile counters are used to save security counters then their value
[all …]
|
| D | tfm_secure_boot.rst | 26 TF-M secure boot code is not guaranteed then TF-M secure boot code must be
28 of trust (first stage bootloader + ROTPK) is not ensured then there is a
33 stage bootloader then it must be stored according to the above requirements.
76 concatenated. In case of single image boot they are concatenated first and then
77 signed. In case of multiple image boot they are separately signed first and then
152 upgrade, then the content of the primary slot will be simply overwritten with
167 secondary slot, which is marked for upgrade, then contents of the primary slot
181 the swap is made "permanent" and MCUBoot will then still choose to run it
192 then the active image flag is moved between slots during firmware upgrade. If
193 firmware is executed-in-place (XIP), then two firmware images must be generated.
[all …]
|
| /trusted-firmware-m-3.6.0/docs/platform/arm/rss/ |
| D | rss_provisioning.rst | 20 (which it is by default) then the chip will be set to TCI mode. If this option
24 Once the TP mode has been set, the chip is then is Chip Manufacturer
31 the CryptoCell TRNG. The chip must then enter secure provisioning mode by
35 disclosure of the decrypted provisioning bundle values. The RSS will then
63 data), and then encrypts and signs them with the RTL key to produce
74 ``TFM_DUMMY_PROVISIONING`` enabled then it will automatically set the chip to
99 once, and then to save the state of the OTP in SE LCS and then preload that on
|
| D | rss_key_management.rst | 27 hardware as hardware keyslots) can be read and written, and then subsequently
35 and then can use it to perform cryptographic operations. For the CryptoCell-3XX
48 and the HUK and GUK are then invalidated so they cannot be used by the runtime
|
| D | readme.rst | 128 obtained, RSS images can be inserted by first patching the host FIP and then
149 extracted from the GPT image using the following commands (and can then be
178 If ``TFM_DUMMY_PROVISIONING`` is disabled and provisioning is required, then
180 ``tp_mode`` variable in the current stack frame is easiest). BL1_1 will then
|
| /trusted-firmware-m-3.6.0/docs/platform/arm/mps3/corstone300/ |
| D | README.rst | 69 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` and ``-DTFM_DUMMY_PROVISIONING=ON`` then the keys in
74 then unique values can be used for provisioning. The keys and seeds can be changed by
84 If ``-DMCUBOOT_GENERATE_SIGNING_KEYPAIR=ON`` is set then a new mcuboot signing public and private
156 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` is set then the provisioning bundle has to
158 renaming it to ``prv.bin``, then extending the images.txt with::
222 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` is set then the provisioning bundle has to
224 renaming it to ``prv.bin``, then extending the images.txt with::
268 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` is set then the provisioning bundle has to
|
| /trusted-firmware-m-3.6.0/docs/platform/arm/mps3/corstone310/ |
| D | README.rst | 62 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` and ``-DTFM_DUMMY_PROVISIONING=ON`` then the keys in
67 then unique values can be used for provisioning. The keys and seeds can be changed by
77 If ``-DMCUBOOT_GENERATE_SIGNING_KEYPAIR=ON`` is set then a new mcuboot signing public and private
157 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` is set then the provisioning bundle has to
159 renaming it to ``prv.bin``, then extending the images.txt with::
203 If ``-DPLATFORM_DEFAULT_PROVISIONING=OFF`` is set then the provisioning bundle has to
|
| /trusted-firmware-m-3.6.0/docs/doxygen/ |
| D | mainpage.dox | 20 If information of a specific item is needed, then please use the search box
|
| D | Doxyfile.in | 70 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
140 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
190 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
199 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
219 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
225 # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
257 # only. Doxygen will then generate output that is more tailored for C. For
265 # Python sources only. Doxygen will then generate output that is more tailored
273 # sources. Doxygen will then generate output that is tailored for Fortran.
279 # sources. Doxygen will then generate output that is tailored for VHDL.
[all …]
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/utils/src/cc3x_asset_prov_rt/examples/ |
| D | asset_prov_se_512.cfg | 12 # For enhanced security, this parameter can be omitted, and then the utility …
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/utils/src/dmpu_asset_pkg_util/icv_key_response/examples/ |
| D | dmpu_icv_key_response.cfg | 13 # For enhanced security, this parameter can be omitted, and then the utility …
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/utils/src/dmpu_asset_pkg_util/oem_key_request/examples/ |
| D | dmpu_oem_key_request.cfg | 12 # For enhanced security, this parameter can be omitted, and then the utility …
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/host/src/tests/integration_cc3x/ |
| D | proj_integration_tests.cfg | 37 # If the following flag = 1, then use specific ECC functions
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/utils/src/dmpu_asset_pkg_util/oem_asset_package/examples/ |
| D | asset_oem_ce.cfg | 14 # For enhanced security, this parameter can be omitted, and then the utility …
|
| D | asset_oem_cp.cfg | 14 # For enhanced security, this parameter can be omitted, and then the utility …
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/utils/src/cmpu_asset_pkg_util/examples/ |
| D | asset_icv_ce.cfg | 16 # For enhanced security, this parameter can be omitted, and then the utility …
|
| D | asset_icv_cp.cfg | 16 # For enhanced security, this parameter can be omitted, and then the utility …
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/host/ |
| D | proj.cfg | 51 # If the following flag = 1, then use specific ECC functions
|
| /trusted-firmware-m-3.6.0/docs/design_docs/services/ |
| D | tfm_its_512_flash.rst | 28 requires two flash blocks to be updated: first the data block and then the
32 However, if the ITS_FLASH_PROGRAM_UNIT is 512 Bytes then the data will have to
|
| /trusted-firmware-m-3.6.0/lib/ext/cryptocell-312-runtime/utils/src/cc3x_boot_cert/examples/developer_cert/ |
| D | sb_developer_dbg_cert.cfg | 12 # For enhanced security, this parameter can be omitted, and then the utility …
|
| D | sb_developer_dbg_cert_no_pwd.cfg | 12 # For enhanced security, this parameter can be omitted, and then the utility …
|
| /trusted-firmware-m-3.6.0/config/ |
| D | pre_config.cmake | 23 # The default build type is MinSizeRel. If debug symbols are needed then
|
1234
