| /trusted-firmware-m-3.7.0/docs/contributing/ |
| D | code_review_guide.rst | 70 namespace needs to be expressed in one word to be followed by other words
101 external MACRO wrapped assembler code is allowed. Here is one example of the
124 - R5.1 Put the ``interface header`` of one module in the ``include`` folder
126 folders, which means only one ``include`` is allowed for one module.
159 even this header is included inside one of the existing included headers.
228 Ideally, one topic should cover one specific type of changes. For crossing
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/services/ |
| D | tfm_manifest_tool_user_guide.rst | 48 Required. At least one item must be provided.
50 A list of TF-M Secure Partition manifest lists which contain one or more
56 Required. At least one item must be provided.
63 Required. At least one item must be provided.
120 The value must be defined in one of the `Configuration Header File`_.
134 The manifest tool assigns one for the Secure Partition.
177 Each one must contain a ``file_list`` attribute which collects the files to
198 so they are not in any generated file lists since one template generates
|
| D | tfm_its_integration_guide.rst | 161 This implementation writes entire block updates in one-shot, so the CMSIS
199 each logical block corresponds to one physical flash erase sector (the smallest
201 below allows a number of contiguous erase sectors to form one logical block.
234 asset size will fit in one logical block.
311 data to be copied between the client and the filesystem in one iteration.
|
| /trusted-firmware-m-3.7.0/docs/design_docs/ |
| D | ff_isolation.rst | 64 The essence of isolation is to protect the assets of one protection domain from
172 one running at a time and all others are deactivated, the SPM needs to set up
173 necessary regions for each asset type in one partition only.
183 duplicating the library code can be one solution but it is not "shared"
201 And one more Armv8.1M access permssion:
224 access attributes into one same region:
226 - The data relocating or clearing when booting can be done in one step instead
278 inside one upper region can be adjusted freely.
344 n equals the maximum peripheral numbers needed by one partition. This is
369 default access rules to the collected. Furthermore, one default rule can be
|
| D | tfm_log_system_design_document.rst | 54 be equal to one of the four log levels.
76 * brief Output the given message plus one value as hexadecimal. The message
150 be equal to one of the four log levels and it is an overall setting for all
|
| /trusted-firmware-m-3.7.0/docs/design_docs/services/ |
| D | tfm_its_512_flash.rst | 34 that much data in one-shot.
60 proposed block-buffer is used, the block is programmed in one-shot and the
|
| D | stateless_rot_service.rst | 148 service is a one-shot connection. These services provide standalone operations
202 Similar stateless services in a partition could be grouped, and assign one
207 It is recommended that each Secure Partition declares one stateless service
|
| D | secure_partition_manager.rst | 81 handles the service access in messages one by one.
121 services in one step, an `NSPE` client needs to cross the secure boundaries
215 This procedure is abstracted into one `HAL`, and a few example procedures
315 access request is raised by one client.
386 - PSA API gets called by one of the ABI mentioned in the last chapter as
473 - IPC partitions handles messages one by one, the client gets blocked before
482 `Function call ABI`. After SPM operations, one more component runtime type
519 example, the `First Level Interrupt Handler (FLIH)` of one partition.
608 is set as one level higher than the default thread mode priority. If
|
| /trusted-firmware-m-3.7.0/docs/design_docs/dual-cpu/ |
| D | mailbox_ns_agent_update.rst | 13 one other isolation mechanism that implements individual PEs in physically
82 - Working like a standard Secure Partition under the IPC model, has one
196 is a connection-based one.
239 services because ``agent_psa_connect()`` already assigned one in the
261 To cooperate with the agent-specific API, one extra acknowledgement signal is
269 ``psa_get()`` with this signal to get one acknowledged message. This signal is
436 - If there is one Trustzone-based NSPE, this NSPE is the recommended place no
439 one of the mailbox agents.
|
| D | communication_prototype_between_nspe_and_spe_in_dual_core_systems.rst | 285 process mailbox messages one by one.
381 Currently one and only one mailbox implementation is supported in dual core
382 communication. This flag indicates that callback functions from one mailbox
474 Currently one and only one underlying mailbox communication implementation is
488 Currently one and only one underlying mailbox communication implementation is
|
| D | mailbox_design_on_dual_core_system.rst | 114 NSPE mailbox queue contains one or more slots. The number of slots should be
156 SPE mailbox queue contains one or more slots. The number of slots should be
214 process mailbox messages one by one.
245 It is recommended to assign one independent set of Inter-Processor Communication
383 A new PSA Client call cannot be started until the previous one is completed.
1063 ``tfm_ns_mailbox_os_lock_init()`` is defined as a dummy one.
1088 ``tfm_ns_mailbox_os_lock_acquire()`` is defined as a dummy one.
1113 ``tfm_ns_mailbox_os_lock_release()`` is defined as a dummy one.
1189 ``tfm_ns_mailbox_os_mq_create()`` is defined as a dummy one.
1220 ``tfm_ns_mailbox_os_mq_send()`` is defined as a dummy one.
[all …]
|
| /trusted-firmware-m-3.7.0/platform/ext/target/nordic_nrf/common/core/ |
| D | CMakeLists.txt | 18 message(FATAL_ERROR "Please select one of the nRF boards. "
26 # Maybe we only need to check one of these options but these
|
| /trusted-firmware-m-3.7.0/config/ |
| D | tfm_platform.cmake | 13 # the "cpuarch.cmake" and find the matching one.
|
| D | kconfig.cmake | 8 # Load multiple config files and merge into one, generates CMake config file and config header file.
54 # Try to convert CMake format to Kconfig one
94 # The function distinguishes command-line variables and other ones and it can only handle one of
|
| /trusted-firmware-m-3.7.0/lib/ext/cryptocell-312-runtime/codesafe/src/crypto_api/ffcdh/ |
| D | cc_ffcdh.c | 1077 uint32_t one; in CC_FfcDhValidatePublKey() local
1122 one = 1; in CC_FfcDhValidatePublKey()
1123 cmp = CC_CommonCmpLsWordsUnsignedCounters(pPublKey32, primeSizeWords, &one, 1); in CC_FfcDhValidatePublKey()
1148 cmp = CC_CommonCmpLsWordsUnsignedCounters(pPublKey32, primeSizeWords, &one, 1); in CC_FfcDhValidatePublKey()
1326 uint32_t *pPrime, *pOrder, one = 0; in CC_FfcDhValidateAndImportKeyPair() local
1415 one = 0; in CC_FfcDhValidateAndImportKeyPair()
1416 cmp = CC_CommonCmpLsWordsUnsignedCounters(pPrivKey32, orderSizeWords, &one, 1); in CC_FfcDhValidateAndImportKeyPair()
1424 one = 1; in CC_FfcDhValidateAndImportKeyPair()
1425 cmp = CC_CommonCmpLsWordsUnsignedCounters(pPublKey32, primeSizeWords, &one, 1); in CC_FfcDhValidateAndImportKeyPair()
|
| /trusted-firmware-m-3.7.0/docs/doxygen/ |
| D | Doxyfile.in | 50 # Using the PROJECT_BRIEF tag one can provide an optional one line description
56 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
163 # Stripping is only done if one of the specified strings matches the left-hand
177 # the header file containing the class definition is used. Otherwise one should
288 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
372 # If one adds a struct or class to a group and this option is enabled, then also
374 # is disabled and one has to add nested compounds explicitly via \ingroup.
622 # only one candidate or it is obvious which candidate to choose by doing a
715 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
816 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
[all …]
|
| /trusted-firmware-m-3.7.0/lib/ext/t_cose/ |
| D | README.md | 136 t_cose has one configuration that covers both which hinges off a
162 That said, there is one case where t_cose source code needs to be
194 The design is such that only one copy of the COSE_Sign1 need be in memory. It makes
197 The payload to sign must be in one contiguous buffer and be passed in. It can be allocated
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/ |
| D | tfm_secure_irq_integration_guide.rst | 122 The interrupt handling model is SLIH by default as it is the only supported one
150 The ``source`` is the same as the one in Firmware Framework Version 1.0.
171 have one of the following values:
223 The ``permission`` attribute must have one of the following values:
|
| D | non-secure_client_extension_integration_guide.rst | 64 specified for the connection of the NS client. NSCE allocates only one context
92 As TF-M only supports one context for now, so the return value is always `1`
174 context number allocated to it. TF-M only supports one context for now.
222 If the RTOS has no existing one, then a "Secure Context Manager" should be
|
| /trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/Core/Test/ |
| D | README.md | 103 To build and run the CoreValidation tests for one or more configurations use the following command …
131 In case of failing test cases, one can run a single test case with verbose output like this:
|
| /trusted-firmware-m-3.7.0/docs/design_docs/software/ |
| D | tfm_code_generation_with_jinja2.rst | 44 library is very similar to the one required by the current scripts.
|
| /trusted-firmware-m-3.7.0/lib/ext/cryptocell-312-runtime/codesafe/src/crypto_api/dh/ |
| D | cc_dh.c | 415 uint8_t one = 1; in CC_DhGetSecretKey() local
485 &one, 1/*size*/, in CC_DhGetSecretKey()
|
| /trusted-firmware-m-3.7.0/docs/design_docs/booting/ |
| D | secure_boot_hw_key_integration.rst | 12 specification requires the support of at least one immutable root of trust
66 - Multiple independent vendor scenario must be supported, when more than one
|
| /trusted-firmware-m-3.7.0/platform/ext/target/arm/mps4/corstone315/ |
| D | config.cmake | 39 … ON CACHE STRING "Whether to use default BL1 or platform-specific one")
|
| /trusted-firmware-m-3.7.0/docs/platform/cypress/psoc64/ |
| D | cypress_psoc64_spec.rst | 242 Note: the tool overwrites unsigned file with a signed one, it also creates an
269 * CySecureTools sign-image overwrites unsigned file with a signed one,
298 Copy tfm hex files one by one to the DAPLINK device:
|
