Searched full:solution (Results 1 – 25 of 41) sorted by relevance
12
| /trusted-firmware-m-latest/platform/ext/common/ |
| D | faults.c | 17 * taken, so the current solution is not to return. in C_HardFault_Handler()
37 * to be taken, so the current solution is to panic. in C_MemManage_Handler()
57 * taken, so the current solution is to panic. in C_BusFault_Handler()
77 * taken, so the current solution is to panic. in C_SecureFault_Handler()
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Core/Include/ |
| D | cmsis_compiler.h | 161 #warning No compiler specific solution for __COMPILER_BARRIER. __COMPILER_BARRIER is ignored.
231 #warning No compiler specific solution for __RESTRICT. __RESTRICT is ignored.
235 #warning No compiler specific solution for __COMPILER_BARRIER. __COMPILER_BARRIER is ignored.
268 #warning No compiler specific solution for __USED. __USED is ignored.
300 #warning No compiler specific solution for __ALIGNED. __ALIGNED is ignored.
304 #warning No compiler specific solution for __RESTRICT. __RESTRICT is ignored.
308 #warning No compiler specific solution for __COMPILER_BARRIER. __COMPILER_BARRIER is ignored.
|
| /trusted-firmware-m-latest/docs/design_docs/booting/ |
| D | secure_boot_hw_key_integration.rst | 16 independently from any software components. The current key handling solution
23 document to propose a solution to decouple MCUBoot from public key(s) and
26 Existing key handling solution
81 to the device with the current solution. A new TLV type (TLV_KEY) can be
143 The solution must be compile time configurable in order to be able to switch
153 Table to compare the current and proposed solution::
|
| D | secure_boot_rollback_protection.rst | 73 However, as an alternative solution the image version number also could serve
|
| /trusted-firmware-m-latest/docs/design_docs/software/ |
| D | tfm_code_generation_with_jinja2.rst | 49 Improvements over the current solution
52 - Compatible with Python 2.7 and Python 3, while current solution only supports
58 well established software in contrast with the current proprietary solution.
|
| D | code_sharing.rst | 59 following design proposal provides a solution to these challenges.
299 code sharing might be a solution, as the new runtime firmware could contain the
|
| /trusted-firmware-m-latest/docs/design_docs/services/ |
| D | tfm_its_service.rst | 203 A third, even more general, solution would be to use arbitrary-length
204 null-terminated strings as the file IDs. This is the standard solution in
233 However, it is a more intuitive solution and would simplify both flash alignment
237 the proposed solution.
342 similar to Protected Storage solution. When used, the default NV seed template
|
| /trusted-firmware-m-latest/platform/include/ |
| D | tfm_plat_rotpk.h | 28 * \note Just temporary solution, hard-coded key-hash values in firmware is not
|
| /trusted-firmware-m-latest/lib/ext/qcbor/ |
| D | 0001-Disable-gcc-Wmaybe-uninitialized-because-of-false-po.patch | 63 + * One solution would be to change the code so -Wmaybe-uninitialized
72 + * The solution here is to just use a pragma to disable it for the
|
| /trusted-firmware-m-latest/interface/include/mbedtls/ |
| D | config_adjust_legacy_crypto.h | 259 * - CIPHER_C is not defined, which is also the legacy solution;
290 * to enable the built-in solution.
404 * can either be provided through the legacy ECP solution or through the
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Project/ |
| D | Validation.csolution.yml | 1 solution:
|
| /trusted-firmware-m-latest/lib/ext/mbedcrypto/ |
| D | 0007-Enable-sources-when-MCUBOOT_USE_PSA_CRYPTO-and-not-M.patch | 9 such case. A full solution might require a change in config strategy of
|
| /trusted-firmware-m-latest/platform/ext/target/rpi/rp2350/ |
| D | tfm_hal_multi_core.c | 62 * The simplest solution is for Core0 to ring Core1's doorbell where we wait out
|
| /trusted-firmware-m-latest/docs/platform/arm/rse/ |
| D | rse_provisioning.rst | 97 FVP. The preferred solution is to preload to the provisioning bundles into VM0
99 on other systems. An alternative solution is to perform provisioning manually
|
| /trusted-firmware-m-latest/docs/platform/ |
| D | platform_introduction.rst | 56 <https://www.nuvoton.com/products/iot-solution/iot-platform/numaker-pfm-m2351/>`_
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/ |
| D | README.md | 11 ┣ �� Project Solution and project files to build tests for various configurations.
|
| /trusted-firmware-m-latest/docs/design_docs/ |
| D | tfm_builtin_keys.rst | 34 In TF-M's legacy solution, the IAK is loaded by the attestation service as a
46 solution for dealing with this type of keys in several ways. For example, it
|
| /trusted-firmware-m-latest/docs/releases/ |
| D | 1.2.0.rst | 49 <https://www.nuvoton.com/products/iot-solution/iot-platform/numaker-pfm-m2351/>`_
|
| /trusted-firmware-m-latest/secure_fw/partitions/ns_agent_tz/ |
| D | psa_api_veneers_v80m.c | 26 * software solution needs to be applied because hardware reentrant
|
| /trusted-firmware-m-latest/platform/ext/common/template/ |
| D | tfm_hal_its_encryption.c | 59 /* Copy PS solution */
|
| /trusted-firmware-m-latest/docs/platform/arm/corstone1000/ |
| D | readme.rst | 49 Platform solution
|
| /trusted-firmware-m-latest/platform/ext/target/nuvoton/common/bsp/StdDriver/src/ |
| D | usci_uart.c | 372 /* Find best solution */ in UUART_Open()
548 /* Find best solution */ in UUART_SetLine_Config()
|
| /trusted-firmware-m-latest/docs/design_docs/dual-cpu/ |
| D | mailbox_ns_agent_update.rst | 24 interrupt handling was not ready. Hence a customized solution
441 The solution is:
|
| /trusted-firmware-m-latest/platform/ext/target/nordic_nrf/common/core/common/ |
| D | nrfx_glue.h | 142 * @ref nrfx_coredep_delay_us uses a precise DWT-based solution.
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Core/Include/a-profile/ |
| D | cmsis_iccarm_a.h | 50 #warning No compiler specific solution for __ALIGNED.__ALIGNED is ignored.
|
12
