Searched +full:created +full:- +full:for (Results 1 – 25 of 100) sorted by relevance
1234
| /trusted-firmware-m-latest/docs/releases/ |
| D | 1.0.rst | 9 - First major release.
11 - A Secure FW with support for PSA Level 1 and 2 isolation on Armv8-M
12 using TrustZone extension and Dual-core Cortex-M config.
14 - The PSA Firmware Framework (PSA FF)/Dev API interfaces exposed by the
17 - A secure FW model with NS application example.
19 - Secure services running within this SPE
21 - Secure Storage Service (PSA Protected Storage API - 1.0.0)
22 - Attestation (PSA Attestation API 1.0.0)
23 - Crypto Service (PSA API 1.0-beta-3)
24 - TF-M Audit Log
[all …]
|
| D | release_process.rst | 9 `TF-M mailing list <https://lists.trustedfirmware.org/mailman3/lists/tf-m.lists.trustedfirmware.org…
13 issues found, additional candidates may be created to fix and retest the issues.
27 hide time-axis
34 -3 is development
35 @0 <-> @8 : release cadence: ~9 months
39 main -> rel1 : start
42 +1 is {-}
43 rel1 -> main : back port
45 +1 is {-}
46 rel1 -> main : cherry-pick
[all …]
|
| /trusted-firmware-m-latest/interface/include/os_wrapper/ |
| D | mutex.h | 2 * Copyright (c) 2017-2019, Arm Limited. All rights reserved.
6 * SPDX-License-Identifier: BSD-3-Clause
20 * \brief Creates a mutex for mutual exclusion of resources
22 * \return The handle of the created mutex on success or NULL on error
27 * \brief Acquires a mutex that is created by \ref os_wrapper_mutex_create()
31 * \param[in] timeout The maximum amount of time(in tick periods) for the
32 * thread to wait for the mutex to be available.
53 * \brief Deletes a mutex that is created by \ref os_wrapper_mutex_create()
|
| /trusted-firmware-m-latest/docs/design_docs/services/ |
| D | tfm_uniform_secure_service_signature.rst | 16 Individual signatures - current method
19 A ``<service_name>_veneers.c`` file is created in the ``secure_fw/ns_callable``
20 directory, that specifies the signature for each veneer function, and calls the
23 have to be created and maintained manually.
24 Note that at present TF-M framework limits the range of valid return values a
25 secure service can provide, reserving a range for framework error codes.
27 Uniform signatures - proposal
30 The proposal is to use a uniform signature for all the secure functions of the
33 - TF-M Core can do a sanity check on the access rights of the veneer
34 parameters, and there is no need for the secure services to make these checks
[all …]
|
| D | secure_partition_manager.rst | 5 design in Trusted Firmware-M (`TF-M`).
8 - The FF-M in this document refers to the accumulated result of two
10 `FF-M v1.1 Update <https://developer.arm.com/documentation/aes0039/latest>`_
12 `FF-M v1.0 <https://developer.arm.com/documentation/den0063/latest/>`_.
13 - The words marked as `interpreted` are defined terms. Find the terms in
19 The service access process of FF-M:
23 :name: fig-tfmdev
26 FF-M service access process
34 - Contains services with the same purpose.
35 - Provides implementation required isolation boundaries.
[all …]
|
| /trusted-firmware-m-latest/docs/cmake/ |
| D | FindSphinx.cmake | 1 #-------------------------------------------------------------------------------
4 # SPDX-License-Identifier: BSD-3-Clause
6 #-------------------------------------------------------------------------------
9 #-----------
11 #See http://www.sphinx-doc.org/en/master/
14 #(sphinx-build) and it's dependences (Python).
16 #package (i.e. python-sphinx for Ubuntu). Independent of the distribution
17 #method this module expects sphix-build to be either available on the PATH,
21 # SPHINX_PATH = variable specifying where sphinx-build can be found.
28 # SPHINX_VERSION = The version reported by "sphinx-build --version"
[all …]
|
| /trusted-firmware-m-latest/interface/include/psa/ |
| D | crypto_types.h | 10 * This file contains portable definitions of integral types for properties
18 * SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
25 * Include the build-time configuration information header. Here, we do not
28 * TF-PSA-Crypto repository which has a different build system and
89 * Values defined by this standard will never be in the range 0x80-0xff.
99 /** The type of PSA Diffie-Hellman group family identifiers.
104 * The group identifier is required to create a Diffie-Hellman key using the
108 * Values defined by this standard will never be in the range 0x80-0xff.
123 * For algorithms that can be applied to multiple key types, this type
124 * does not encode the key type. For example, for symmetric ciphers
[all …]
|
| D | protected_storage.h | 2 * Copyright (c) 2019-2020, Arm Limited. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
38 * \param[in] uid The identifier for the data
48 * created with
52 * is invalid, for example is `NULL` or
96 * `p_data_length`) is invalid, for example
125 * Retrieves the metadata stored for a given `uid`
136 * is invalid, for example is `NULL` or
168 * uid value was created with
178 * \brief Reserves storage for the specified uid
[all …]
|
| D | internal_trusted_storage.h | 4 * SPDX-License-Identifier: BSD-3-Clause
36 * \param[in] uid The identifier for the data
46 * created with
60 * is invalid, for example is `NULL` or
98 * `p_data_length`) is invalid, for example
114 * Retrieves the metadata stored for a given `uid` as a `psa_storage_info_t`
130 * is invalid, for example is `NULL` or
153 * uid value was created with
|
| D | initial_attestation.h.in | 2 * Copyright (c) 2018-2022, Arm Limited. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
39 * attestation service. Used to configure buffers for services that verify the
50 * https://tools.ietf.org/html/draft-mandyam-eat-01
53 * - Challenge: Input object from caller. Can be a single nonce from server
62 * - Instance ID: It represents the unique identifier of the instance. In the
70 * - Verification service indicator: Optional, recommended claim. It is used by
71 * a Relying Party to locate a validation service for the token.
79 * - Profile definition: Optional, recommended claim. It contains the name of
85 * - Implementation ID: It represents the original implementation signer of the
[all …]
|
| /trusted-firmware-m-latest/secure_fw/partitions/initial_attestation/ |
| D | attest_token.h | 4 * Copyright (c) 2018-2019, Laurence Lundblade.
5 * Copyright (c) 2020-2023, Arm Limited. All rights reserved.
7 * SPDX-License-Identifier: BSD-3-Clause
9 * See BSD-3-Clause license in README.md
35 * -# Create and initialize an attest_token_encode_ctx indicating the
38 * -# Use various add methods to fill in the payload with claims. The
39 * encoding context can also be borrowed for more rich payloads.
41 * -# Call attest_token_encode_finish() to create the signature and finish
62 /** CBOR Syntax not well-formed -- a CBOR syntax error. */
64 /** Bad CBOR structure, for example not a map when was is
[all …]
|
| /trusted-firmware-m-latest/docs/platform/arm/rse/ |
| D | readme.rst | 5 ------------
9 …chitecture (CCA) <https://www.arm.com/architecture/security-features/arm-confidential-compute-arch…
10 It is designed to be integrated into A-profile compute subsystems that implement
14 jumping to BL1_2, which is provisioned and hash-locked in RSE OTP. The updatable
16 is authenticated. BL2 loads and authenticates the TF-M runtime into RSE SRAM
17 from host flash. BL2 is also responsible for loading initial boot code into
20 The RSE platform port supports the TF-M Crypto, TF-M Initial Attestation,
21 Measured Boot and TF-M Platform services along with the corresponding
22 regression tests. It supports the IPC model in multi-core topology with
25 Building TF-M
[all …]
|
| /trusted-firmware-m-latest/docs/configuration/ |
| D | kconfig_system.rst | 6 The Kconfig system is an alternative tool to the CMake config system for users to change config
7 options of TF-M.
25 - CMake config file
29 - Header file
32 Component options are gathered together in a separate menu ``TF-M component configs`` in
35 - The .config and .config.old files
38 It will be created after the first execution of the script. It is only used to allow
40 The Kconfig tool will load it if it exists and ``.config.old`` will be created to
43 The tool supports loading multiple pre-set configuration files merging into a single one.
47 It then launches a configuration GUI for users to change any config options if the ``MENUCONFIG`` is
[all …]
|
| /trusted-firmware-m-latest/secure_fw/partitions/protected_storage/ |
| D | tfm_protected_storage.h | 2 * Copyright (c) 2019-2020, Arm Limited. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
38 * \param[in] uid Unique identifier for the data
48 * created with
71 * \brief Gets the asset data for the provided uid.
74 * \param[in] uid Unique identifier for the data
109 * \brief Gets the metadata for the provided uid.
112 * \param[in] uid Unique identifier for the data
144 * \param[in] uid Unique identifier for the data to be removed
157 * provided uid value was created with
[all …]
|
| /trusted-firmware-m-latest/cmake/ |
| D | remote_library.cmake | 1 #-------------------------------------------------------------------------------
6 # SPDX-License-Identifier: BSD-3-Clause
8 #-------------------------------------------------------------------------------
18 # WORKING_DIRECTORY - working directory where patches should be applied.
19 # PATCH_FILES - list of patches. Patches will be applied in alphabetical order.
22 # Step 1 - keep changes in stash with random message/name to detect
23 # that stash has been created by git
25 set(STASH_NAME "tfm-remote_library-apply_patches-${STASH_NAME}")
26 execute_process(COMMAND "${GIT_EXECUTABLE}" stash push -u -m "${STASH_NAME}"
31 # Step 2 - get list of stashes to validate that stash has been created
[all …]
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/shared/include/crypto_api/ |
| D | cc_ecpki_ecdsa.h | 2 * Copyright (c) 2001-2019, Arm Limited and Contributors. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
33 * CC_EcdsaSign - integrated function
39 Algorithm according to the ANSI X9.62-2005: Public Key Cryptography for the Financial Services Indu…
42 The message data may be either a non-hashed data or a digest of a hash function.
43 For a non-hashed data, the message data will be hashed using the hash function indicated by ::CCEcp…
44 For a digest, ::CCEcpkiHashOpMode_t should indicate the hash function that the message data was cre…
48 @return A non-zero value on failure as defined cc_ecpki_error.h, cc_hash_error.h or cc_rnd_error.h.
52 …rContext_t *pSignUserContext, /*!< [in/out] Pointer to the user buffer for signing the databas…
54 …HashOpMode_t hashMode, /*!< [in] One of the supported SHA-x HASH modes, as defi…
[all …]
|
| /trusted-firmware-m-latest/secure_fw/partitions/internal_trusted_storage/flash_fs/ |
| D | its_flash_fs_mblock.h | 2 * Copyright (c) 2018-2021, Arm Limited. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
80 uint8_t roundup[sizeof(struct __attribute__((__aligned__(ITS_FLASH_MAX_ALIGNMENT))) { _T1 }) -
113 …uint8_t roundup[sizeof(struct __attribute__((__aligned__(ITS_FLASH_MAX_ALIGNMENT))) { _T1_COMP }) -
133 * block compaction for gap reuse) \
139 uint8_t roundup[sizeof(struct __attribute__((__aligned__(ITS_FLASH_MAX_ALIGNMENT))) { _T2 }) -
157 size_t cur_size; /* Size in storage system for this fragment */ \
159 uint32_t flags; /* Flags set when the file was created */ \
167 size_t cur_size; /* Size in storage system for this fragment */ \
169 uint32_t flags; /* Flags set when the file was created */ \
[all …]
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/shared/include/pal/linux/ |
| D | cc_pal_dma_plat.h | 2 * Copyright (c) 2001-2019, Arm Limited and Contributors. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
20 …* @brief Initializes contiguous memory pool required for CC_PalDmaContigBufferAllocate() and CC_…
21 …* example implementation is to mmap 0x30000000 and call to bpool(), for use of bget() in CC_P…
24 * @return A non-zero value in case of failure.
30 * @brief free system resources created in CC_PalDmaInit()
32 * @param[in] buffSize - buffer size in Bytes
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/host/src/tests/TestAL/pal/include/ |
| D | test_pal_semphr.h | 5 * (C) COPYRIGHT [2001-2017] ARM Limited or its affiliates. *
34 * ppMutexId - pointer to the created Test_PalMutex.
36 * @return - 0 on success, 1 for failure.
45 * ppMutexId - pointer to Test_PalMutex.
49 * @return - 0.
55 * @brief This function waits for a mutex with timeout. The timeout is
59 * ppMutexId - pointer to Test_PalMutex.
60 * timeout - Timeout in msec, or INFINITE.
62 * @return - 0 on success, 1 for failure.
72 * ppMutexId - pointer to Test_PalMutex.
[all …]
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/host/src/tests/integration_cc3x/runtime_integration_test/ |
| D | README.txt | 4 The HAL and PAL layers are assumed to be implemented by the user for the user's system.
6 These integration tests use simple scenarios for verifying successful
10 - Chapter "Appendix C - Integration test" in the Software Integrators Manual
13 - Chapter "2.2.1 Unpacking the shipment" in the Release Notes document - for
17 The integration tests package was tested for the following environment:
20 . arm-compiler-5 5.06 compiler.
23 1. The user created a dedicated PAL and HAL layers, which match the user's platform.
28 --------------
30 Copyright (c) 2001-2019, Arm Limited. All rights reserved.
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/utils/src/dmpu_asset_pkg_util/oem_key_request/examples/ |
| D | dmpu_oem_key_request.cfg | 1 #-------------------------------------------------------------------------------
2 # Copyright (c) 2001-2019, Arm Limited. All rights reserved.
4 # SPDX-License-Identifier: BSD-3-Clause
6 #-------------------------------------------------------------------------------
8 # This is configuration file example for generating key request certificate by OEM
9 # [DMPU-OEM-KEY-REQ-CFG] Mandatory header.
10 # oem-main-keypair = File holding the RSA keypair for signing this certificate, in pem forma…
11 # oem-main-keypwd = Passphrase for the keypair file, in txt format.
12 # For enhanced security, this parameter can be omitted, and then the utility …
13 # oem-enc-pubkey = File holding the RSA public key for ICV to encrypt the requested key, in pem …
[all …]
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Project/ |
| D | Validation.csolution.yml | 2 created-for: cmsis-toobox@2.1.0
7 - for-compiler: GCC
8 C-CPP:
9 - -masm-syntax-unified
12 - pack: ARM::CMSIS
15 target-types:
17 - type: CM0
20 - type: CM0plus
23 - type: CM3
26 - type: CM4
[all …]
|
| /trusted-firmware-m-latest/platform/ext/target/stm/common/secure_element/stsafea/se_psa/ |
| D | se_psa.c | 15 * If no LICENSE file comes with this software, it is provided AS-IS.
22 /* Includes ------------------------------------------------------------------*/
35 /* Private typedef -----------------------------------------------------------*/
59 /* Private define ------------------------------------------------------------*/
60 /* Private macro -------------------------------------------------------------*/
62 /* Private struct ------------------------------------------------------------*/
63 /* Private variables ---------------------------------------------------------*/
64 /* Private function prototypes -----------------------------------------------*/
71 * psa trace function for SE PSA traces.
110 * @param key[in] : Identifier of the key to use for the operation.
[all …]
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/shared/include/pal/ |
| D | cc_pal_mutex.h | 2 * Copyright (c) 2001-2019, Arm Limited and Contributors. All rights reserved.
4 * SPDX-License-Identifier: BSD-3-Clause
14 @brief This file contains functions for resource management (mutex operations).
17 operating-system calls.
37 /*----------------------------
39 -----------------------------------*/
46 @return A non-zero value on failure.
49 /*! [out] A pointer to the handle of the created mutex. */
59 @return A non-zero value on failure.
68 @brief This function waits for a mutex with \p aTimeOut.
[all …]
|
| /trusted-firmware-m-latest/platform/ext/target/cypress/psoc64/libs/core-lib/ |
| D | EULA | 9 "Source Code" means software in human-readable form.
13 …to be installed on a personal computer and used to create programming code for Firmware, Drivers, …
21 …information file (.inf file) created by the Software to allow a Microsoft Windows operating system…
23 …nductor Corporation ("Cypress") and its suppliers grant to you a non-exclusive, non-transferable l…
25 …t Tools in object code form solely for the purpose of creating Firmware, Drivers, Host Application…
27 …, to copy, modify, and compile the Firmware Source Code to create Firmware for execution on a Cypr…
35 …ent must be made pursuant to your standard end user license agreement used for your proprietary (c…
37 …for any Third Party Software included with the Software, either the source code will be included …
39 …-readable form; or (iv) use the Software or any sample code other than for the Purpose. You hereb…
41 5. No Support. Cypress may, but is not required to, provide technical support for the Software.
[all …]
|
1234
