Home
last modified time | relevance | path

Searched refs:ref (Results 1 – 25 of 38) sorted by relevance

12

/trusted-firmware-m-3.7.0/secure_fw/partitions/protected_storage/crypto/
Dps_crypto_interface.c134 (void)memcpy(ps_crypto_iv_buf, crypto->ref.iv, PS_IV_LEN_BYTES); in ps_crypto_set_iv()
186 (void)memcpy(crypto->ref.iv, ps_crypto_iv_buf, PS_IV_LEN_BYTES); in ps_crypto_get_iv()
203 crypto->ref.iv, PS_IV_LEN_BYTES, in ps_crypto_encrypt_and_tag()
213 (void)memcpy(crypto->ref.tag, (out + *out_len), PS_TAG_LEN_BYTES); in ps_crypto_encrypt_and_tag()
230 (void)memcpy((in + in_len), crypto->ref.tag, PS_TAG_LEN_BYTES); in ps_crypto_auth_and_decrypt()
234 crypto->ref.iv, PS_IV_LEN_BYTES, in ps_crypto_auth_and_decrypt()
253 crypto->ref.iv, PS_IV_LEN_BYTES, in ps_crypto_generate_auth_tag()
256 crypto->ref.tag, PS_TAG_LEN_BYTES, &out_len); in ps_crypto_generate_auth_tag()
272 crypto->ref.iv, PS_IV_LEN_BYTES, in ps_crypto_authenticate()
274 crypto->ref.tag, PS_TAG_LEN_BYTES, in ps_crypto_authenticate()
Dps_crypto_interface.h34 } ref; member
/trusted-firmware-m-3.7.0/secure_fw/partitions/protected_storage/
Dps_object_system.c169 g_obj_tbl_info.tag = g_ps_object.header.crypto.ref.tag; in ps_system_prepare()
191 g_ps_object.header.crypto.ref.uid = uid; in ps_object_read()
192 g_ps_object.header.crypto.ref.client_id = client_id; in ps_object_read()
249 g_ps_object.header.crypto.ref.uid = uid; in ps_object_create()
250 g_ps_object.header.crypto.ref.client_id = client_id; in ps_object_create()
303 g_ps_object.header.crypto.ref.uid = uid; in ps_object_create()
304 g_ps_object.header.crypto.ref.client_id = client_id; in ps_object_create()
365 g_ps_object.header.crypto.ref.uid = uid; in ps_object_write()
366 g_ps_object.header.crypto.ref.client_id = client_id; in ps_object_write()
418 g_ps_object.header.crypto.ref.uid = uid; in ps_object_write()
[all …]
Dps_encrypted_object.c37 psa_storage_uid_t uid = obj->header.crypto.ref.uid; in fill_key_label()
38 int32_t client_id = obj->header.crypto.ref.client_id; in fill_key_label()
170 (void *)obj->header.crypto.ref.iv, in ps_encrypted_object_read()
181 decrypt_size = data_length - sizeof(obj->header.crypto.ref.iv); in ps_encrypted_object_read()
210 wrt_size += sizeof(obj->header.crypto.ref.iv); in ps_encrypted_object_write()
215 return psa_its_set(fid, wrt_size, (const void *)obj->header.crypto.ref.iv, in ps_encrypted_object_write()
/trusted-firmware-m-3.7.0/docs/configuration/
Dindex.rst27 In the :ref:`Base_configuration` table these options have *Build* type.
32 Options are in C header file. The :ref:`Header_configuration` has more
34 In the :ref:`Base_configuration` table these options have *Component* type.
41 :ref:`Header_configuration` and moved component options into a dedicated
53 Use :ref:`tf-m_profiles`.
65 Use :ref:`Kconfig_system`.
84 :ref:`tfm_cmake_configuration` or :ref:`Header_configuration` please
Dbuild_configuration.rst28 ``TEST_NS_ATTESTATION`` (see :ref:`test_configuration`) is set, then
Dheader_file_system.rst20 :ref:`Base_configuration` for details of the base configurations.
/trusted-firmware-m-3.7.0/docs/building/
Dtfm_build_instruction.rst47 This build generates the SPE binary and artifacts, necessary for :ref:`Building NSPE`.
61 you can alter that behaviour using :ref:`Dependency management`.
75 :ref:`tf-m_configuration` section for the details. The **base** (default) configuration
142 artifact directory please refer to :ref:`Artifacts structure`.
147 explained in :ref:`tfm_cmake_configuration`. Several important options
159 | TFM_PROFILE | See :ref:`tf-m_profiles`. | |
166 for the project config header file is in :ref:`Header_configuration`.
197 for alternatives as described in :ref:`Toolchains`
200 as described in :ref:`Output files`
209 :ref:`Build type` using ArmClang :ref:`Toolchains` you can use the following:
[all …]
/trusted-firmware-m-3.7.0/docs/integration_guide/source_structure/
Dsource_structure.rst40 The `platform` folder contains SW ports of all :ref:`supported platforms
41 <supported_platforms>` and the files necessary for :ref:`adding a new platform
42 <adding_platform>`. Please refer to :ref:`platform folder document
55 BSD-3 license. More details are in the dedicated document :ref:`platform_ext_folder`.
/trusted-firmware-m-3.7.0/docs/releases/
Dindex.rst55 :ref:`releases/release_process:Release Cadence and Process` for
D1.3.0.rst23 See :ref:`releases/1.3.0:New platforms supported` for
153 | A note is added in :ref:`getting_started/tfm_getting_started:Install a toolchain`.
D1.4.0.rst19 See :ref:`releases/1.4.0:New platforms supported` for details.
Drelease_process.rst5 The planned dates are listed in the :ref:`releases/index:Future release plans`
204 using the reference platform :ref:`platform/arm/musca_b1/readme:Musca-B1 Platform Specifics`.
D1.5.0.rst29 See :ref:`releases/1.5.0:New platforms supported` for details.
D1.2.0.rst17 See :ref:`releases/1.2.0:New platforms supported` for
/trusted-firmware-m-3.7.0/platform/ext/target/stm/common/stm32u5xx/hal/Src/
Dstm32u5xx_hal_dma_ex.c4083 uint32_t ref = 0U; in DMA_List_CheckNodesBaseAddresses() local
4088 ref = (uint32_t)pNode1; in DMA_List_CheckNodesBaseAddresses()
4093 ref = (uint32_t)pNode2; in DMA_List_CheckNodesBaseAddresses()
4098 ref = (uint32_t)pNode3; in DMA_List_CheckNodesBaseAddresses()
4103 ref = (uint32_t)pNode4; in DMA_List_CheckNodesBaseAddresses()
4111 if (temp != ((uint32_t)ref & DMA_CLBAR_LBA)) in DMA_List_CheckNodesBaseAddresses()
4132 uint32_t ref = 0U; in DMA_List_CheckNodesTypes() local
4137 ref = pNode1->NodeInfo & NODE_TYPE_MASK; in DMA_List_CheckNodesTypes()
4142 ref = pNode2->NodeInfo & NODE_TYPE_MASK; in DMA_List_CheckNodesTypes()
4147 ref = pNode3->NodeInfo & NODE_TYPE_MASK; in DMA_List_CheckNodesTypes()
[all …]
/trusted-firmware-m-3.7.0/docs/introduction/
Dreadme.rst28 :ref:`Base_configuration` build with just TF-M core and platform drivers and 4 predefined
29 configurations known as :ref:`tf-m_profiles`. TF-M Profiles or TF-M base can
31 :ref:`tf-m_configuration` section.
/trusted-firmware-m-3.7.0/interface/include/psa/
Dcrypto_values.h1361 #define PSA_ALG_AEAD_WITH_DEFAULT_LENGTH_TAG_CASE(aead_alg, ref) \ argument
1363 PSA_ALG_AEAD_WITH_SHORTENED_TAG(ref, 0) ? \
1364 ref :
Dinitial_attestation.h.in162 * \ref PSA_INITIAL_ATTEST_TOKEN_SIZE bytes
171 * \return Returns error code as specified in \ref psa_status_t
191 * \return Returns error code as specified in \ref psa_status_t
/trusted-firmware-m-3.7.0/platform/ext/target/stm/common/stm32h5xx/hal/Src/
Dstm32h5xx_hal_dma_ex.c4079 uint32_t ref = 0U; in DMA_List_CheckNodesBaseAddresses() local
4084 ref = (uint32_t)pNode1; in DMA_List_CheckNodesBaseAddresses()
4089 ref = (uint32_t)pNode2; in DMA_List_CheckNodesBaseAddresses()
4094 ref = (uint32_t)pNode3; in DMA_List_CheckNodesBaseAddresses()
4102 if (temp != ((uint32_t)ref & DMA_CLBAR_LBA)) in DMA_List_CheckNodesBaseAddresses()
4121 uint32_t ref = 0U; in DMA_List_CheckNodesTypes() local
4126 ref = pNode1->NodeInfo & NODE_TYPE_MASK; in DMA_List_CheckNodesTypes()
4131 ref = pNode2->NodeInfo & NODE_TYPE_MASK; in DMA_List_CheckNodesTypes()
4136 ref = pNode3->NodeInfo & NODE_TYPE_MASK; in DMA_List_CheckNodesTypes()
4147 if (ref != (pNode2->NodeInfo & NODE_TYPE_MASK)) in DMA_List_CheckNodesTypes()
[all …]
/trusted-firmware-m-3.7.0/docs/integration_guide/services/
Dtfm_crypto_integration_guide.rst49 :ref:`TF-M Internal Trusted Storage (ITS) service <its-introduction-label>`,
162 described in :ref:`the components list <components-label>`.
169 :ref:`design document <tfm-builtin-keys-label>`.
/trusted-firmware-m-3.7.0/docs/contributing/
Ddoc_guidelines.rst69 Follow the :ref:`platform_documentation` document for more details.
254 (if they are included in the index), the `ref:` keyword can be used
258 :ref:`docs/getting_started/tfm_getting_started:Tool & Dependency overview`
/trusted-firmware-m-3.7.0/docs/design_docs/services/
Dsymmetric_initial_attest.rst45 The top-level design is shown in :ref:`overall-diagram-figure` below.
92 :ref:`ia-service-figure` below. Note that the ``Register symmetric IAK`` stage
176 :ref:`attest-token-start-figure` below.
227 :ref:`attest-token-finish-figure` below.
Dps_key_management.rst111 crypto->ref.iv, PS_IV_LEN_BYTES,
/trusted-firmware-m-3.7.0/docs/design_docs/
Dtfm_physical_attack_mitigation.rst24 The :ref:`tf-m-against-physical-attacks` discussed below
346 Based on the assumption in :ref:`attacker-capability`, a malicious actor is
352 :ref:`physical-attacks-spm` for details.
356 Based on the assumption in :ref:`attacker-capability`, a malicious actor can be
364 stored in PS. Refer to :ref:`physical-attacks-spm` for details.
434 listed in :ref:`phy-att-countermeasures`.
474 As analyzed in :ref:`phy-att-threat-model`, this section focuses on integrating

12