| /Zephyr-latest/boards/raytac/mdbt53_db_40/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
16 # For the non-secure version of the board, the firmware
17 # must be linked into the code-partition (non-secure) defined in DT, regardless.
23 # If the secure firmware is to be combined with a non-secure image
24 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
25 # be restricted to the secure image SRAM partition (sram-secure-partition).
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
[all …]
|
| /Zephyr-latest/boards/raytac/mdbt53v_db_40/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
16 # For the non-secure version of the board, the firmware
17 # must be linked into the code-partition (non-secure) defined in DT, regardless.
23 # If the secure firmware is to be combined with a non-secure image
24 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
25 # be restricted to the secure image SRAM partition (sram-secure-partition).
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
[all …]
|
| /Zephyr-latest/boards/nordic/nrf5340dk/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
16 # For the non-secure version of the board, the firmware
17 # must be linked into the code-partition (non-secure) defined in DT, regardless.
23 # If the secure firmware is to be combined with a non-secure image
24 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
25 # be restricted to the secure image SRAM partition (sram-secure-partition).
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
[all …]
|
| /Zephyr-latest/boards/nordic/nrf5340_audio_dk/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
16 # For the non-secure version of the board, the firmware
17 # must be linked into the code-partition (non-secure) defined in DT, regardless.
23 # If the secure firmware is to be combined with a non-secure image
24 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
25 # be restricted to the secure image SRAM partition (sram-secure-partition).
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
[all …]
|
| /Zephyr-latest/boards/nordic/thingy53/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
16 # For the non-secure version of the board, the firmware
17 # must be linked into the code-partition (non-secure) defined in DT, regardless.
23 # If the secure firmware is to be combined with a non-secure image
24 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
25 # be restricted to the secure image SRAM partition (sram-secure-partition).
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
[all …]
|
| /Zephyr-latest/samples/tfm_integration/tfm_secure_partition/ |
| D | README.rst | 4 Create a secure partition that exposes secure services.
10 "secure services" to other partitions and/or to the non-secure firmware. TF-M already contains
14 This sample creates a dummy secure partition and secure service for TF-M and instructs the TF-M
15 build system to build it into the secure firmware. The dummy secure service is then called in the
16 main file (in the non-secure firmware).
18 This dummy partition has a single secure service, which can index one of 5 dummy secrets inside the
25 For more information on how to add custom secure partitions refer to TF-M's guide:
30 both the secure and non-secure CMakeLists.txt file and make relevant changes, as well as the yaml
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/ |
| D | Kconfig.defconfig | 14 # For the secure version of the board the firmware is linked at the beginning
16 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
17 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
20 # For the non-secure version of the board, the firmware
21 # must be linked into the code-partition (non-secure) defined in DT, regardless.
27 # If the secure firmware is to be combined with a non-secure image
28 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
29 # be restricted to the secure image SRAM partition (sram-secure-partition).
33 # For the non-secure version of the board, the firmware image SRAM is
34 # always restricted to the allocated non-secure SRAM partition.
[all …]
|
| /Zephyr-latest/samples/boards/arc_secure_services/ |
| D | README.rst | 11 This sample implements a simple secure service based on ARC SecureShield to
12 demonstrate how a secure zephyr application runs together with a normal
17 * Secure application will be in the secure memory space defined in
18 ``arc_mpu_regions.c``. Half of RAM and ROM is allocated to secure world,
21 * Memory not allocated to the secure application is allocated to
25 the peripherals are shared between normal mode and secure mode. If some
26 peripherals are required by secure world, it can be done by adding static
32 * Secure interrupts priority > secure threads priority > normal interrupts
43 * secure application: em_starterkit_em7d_secure
46 * secure application: nsim_sem
[all …]
|
| /Zephyr-latest/samples/tfm_integration/tfm_regression_test/ |
| D | README.rst | 9 Run both the Secure and Non-secure TF-M Regression tests using the Zephyr build system.
22 Tests for both the secure and non-secure domain are enabled by default, controlled via the CONFIG_T…
69 Test suite 'Crypto secure interface tests (TFM_CRYPTO_TEST_5XXX)' has PASSED
70 … Test suite 'Initial Attestation Service secure interface tests(TFM_ATTEST_TEST_1XXX)' has PASSED
72 Test suite 'IPC secure interface test (TFM_IPC_TEST_1XXX)' has PASSED
76 #### Execute test suites for the Non-secure area ####
80 Running Test Suite Core non-secure positive tests (TFM_CORE_TEST_1XXX)...
88 Description: 'Test secure service buffer accesses'
91 Description: 'Test secure service to service call'
94 Description: 'Test secure service to service call with buffer handling'
[all …]
|
| /Zephyr-latest/boards/actinius/icarus/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
15 # For the non-secure version of the board, the firmware
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/actinius/icarus_som/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
15 # For the non-secure version of the board, the firmware
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/actinius/icarus_bee/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
15 # For the non-secure version of the board, the firmware
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/nordic/nrf9131ek/ |
| D | Kconfig.defconfig | 8 # For the secure version of the board the firmware is linked at the beginning
10 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
13 # For the non-secure version of the board, the firmware
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/norik/octopus_io_board/ |
| D | Kconfig.defconfig | 6 # For the secure version of the board the firmware is linked at the beginning
8 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
9 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
11 # For the non-secure version of the board, the firmware
12 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/norik/octopus_som/ |
| D | Kconfig.defconfig | 6 # For the secure version of the board the firmware is linked at the beginning
8 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
9 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
11 # For the non-secure version of the board, the firmware
12 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/subsys/secure_storage/src/its/ |
| D | CMakeLists.txt | 15 retrieved through the HW info API. This is not necessarily secure as the device ID may be
17 This means that the data and keys stored via the PSA APIs may not be secure at rest.")
20 The PSA ITS encryption key provider in use is not secure.
22 This means that the data and keys stored via the PSA APIs will not be secure at rest.
23 Use a secure key provider if possible.")
35 The secure storage ITS module is enabled but has no implementation.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 16 Through a set of secure services and by design, TF-M provides:
18 * Isolation of secure and non-secure resources
35 * The secure processing environment (secure boot and TF-M) starts first
36 * Resource allocation for Zephyr relies on choices made in the secure image.
43 order (secure boot > secure image > ns image).
45 While the secure bootloader is optional, it is enabled by default, and secure
46 boot is an important part of providing a secure solution:
84 * PSA Immutable Root of Trust: secure boot
85 * PSA Updateable Root of Trust: most trusted secure services
86 * Application Root of Trust (**ARoT**): isolated secure services
[all …]
|
| /Zephyr-latest/boards/sparkfun/thing_plus/ |
| D | Kconfig.defconfig | 9 # For the secure version of the board the firmware is linked at the beginning
11 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
12 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
14 # For the non-secure version of the board, the firmware
15 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/innblue/innblue22/ |
| D | Kconfig.defconfig | 8 # For the secure version of the board the firmware is linked at the beginning
10 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
13 # For the non-secure version of the board, the firmware
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/innblue/innblue21/ |
| D | Kconfig.defconfig | 8 # For the secure version of the board the firmware is linked at the beginning
10 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
13 # For the non-secure version of the board, the firmware
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/actinius/icarus_som_dk/ |
| D | Kconfig.defconfig | 10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
15 # For the non-secure version of the board, the firmware
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/circuitdojo/feather/ |
| D | Kconfig.defconfig | 9 # For the secure version of the board the firmware is linked at the beginning
11 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
12 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
14 # For the non-secure version of the board, the firmware
15 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/nxp/lpcxpresso55s28/ |
| D | Kconfig.defconfig | 20 # For the secure version of the board the firmware is linked at the beginning
22 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
23 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
25 # For the non-secure version of the board, the firmware
26 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/nordic/nrf9151dk/ |
| D | Kconfig.defconfig | 8 # For the secure version of the board the firmware is linked at the beginning
10 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
13 # For the non-secure version of the board, the firmware
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
| /Zephyr-latest/boards/nordic/nrf9160dk/ |
| D | Kconfig.defconfig | 8 # For the secure version of the board the firmware is linked at the beginning
10 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
13 # For the non-secure version of the board, the firmware
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
|
