| /Zephyr-latest/subsys/fs/nvs/ |
| D | Kconfig | 1 # Non-volatile Storage NVS
7 bool "Non-volatile Storage"
12 Enable support of Non-volatile Storage.
17 bool "Non-volatile Storage lookup cache"
19 Enable Non-volatile Storage cache, used to reduce the NVS data lookup
24 int "Non-volatile Storage lookup cache size"
29 Number of entries in Non-volatile Storage lookup cache.
33 bool "Non-volatile Storage CRC protection on the data"
41 bool "Non-volatile Storage bad memory region recovery"
45 caused by corruption or by providing a non-empty region. This option
|
| /Zephyr-latest/arch/arm/core/cortex_m/tz/ |
| D | Kconfig | 21 comment "Non-secure firmware"
37 Non-Secure state. Secure Entry functions must be
38 located in Non-Secure Callable memory regions.
41 hex "ARM Non-Secure Callable Region base address"
45 Start address of Non-Secure Callable section.
50 place the Non-Secure Callable section, automatically,
54 a Non-Secure Callable section, depending on the available
58 bool "Non-Secure Firmware uses Secure Entry functions"
61 Option indicates that ARM Non-Secure Firmware uses Secure
74 the Non-Secure Firmware to call into the Secure Firmware.
|
| /Zephyr-latest/arch/arm/include/cortex_m/ |
| D | cmse.h | 40 * Return the non-negative MPU region that the address maps to,
220 * @brief Get the MPU (Non-Secure) region number of an address
222 * Return the non-negative MPU (Non-Secure) region that the address maps to,
240 * Return the non-negative SAU (Non-Secure) region that the address maps to,
258 * Return the non-negative IDAU (Non-Secure) region that the address maps to,
277 * This function shall always return zero if executed from Non-Secure state.
286 * @brief Non-Secure Read accessibility of an address
288 * Evaluates whether a specified memory location can be read from Non-Secure
289 * state according to the permissions of the Non-Secure state MPU and the
293 * - if executed from Non-Secure state
[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.
11 The build system will replace the Zephyr application with the Non-Secure TF-M test application,
22 Tests for both the secure and non-secure domain are enabled by default, controlled via the CONFIG_T…
44 Non-Secure system starting...
76 #### Execute test suites for the Non-secure area ####
80 Running Test Suite Core non-secure positive tests (TFM_CORE_TEST_1XXX)...
106 *** Non-secure test suites summary ***
109 Test suite 'Crypto non-secure interface test (TFM_CRYPTO_TEST_6XXX)' has PASSED
110 Test suite 'Platform Service Non-Secure interface tests(TFM_PLATFORM_TEST_2XXX)' has PASSED
111 …Test suite 'Initial Attestation Service non-secure interface tests(TFM_ATTEST_TEST_2XXX)' has PAS…
[all …]
|
| D | sample.yaml | 18 - "Non-Secure system starting..."
19 - "\\#\\#\\#\\# Execute test suites for the Non-secure area \\#\\#\\#\\#"
20 - "\\*\\*\\* End of Non-secure test suites \\*\\*\\*"
|
| /Zephyr-latest/boards/raytac/mdbt53_db_40/ |
| D | Kconfig.defconfig | 12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
|
| /Zephyr-latest/boards/raytac/mdbt53v_db_40/ |
| D | Kconfig.defconfig | 12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
|
| /Zephyr-latest/boards/nordic/nrf5340dk/ |
| D | Kconfig.defconfig | 12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
|
| /Zephyr-latest/boards/nordic/nrf5340_audio_dk/ |
| D | Kconfig.defconfig | 12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
|
| /Zephyr-latest/dts/common/nordic/ |
| D | nrf5340_cpuapp_partition.dtsi | 17 * 0x0005_0000 Non-secure image primary (192 KB)
20 * 0x000c_0000 Non-secure image secondary (192 KB)
24 * 0x000f_8000 Non-secure storage, used when built with NRF_NS_STORAGE=ON,
74 * - Upper 256 kB allocated to Non-Secure image (sram0_ns)
75 * Of the memory allocated to the Non-Secure image
76 * - 192 kB SRAM allocated to the Non-Secure application (sram0_ns_app).
96 /* Non-Secure image memory */
101 /* Non-Secure image memory */
|
| D | nrf91xx_partition.dtsi | 17 * 0x0005_0000 Non-secure image primary (192 KB)
20 * 0x000c_0000 Non-secure image secondary (192 KB)
24 * 0x000f_8000 Non-secure storage, used when built with NRF_NS_STORAGE=ON,
76 * - Upper 168 kB SRAM allocated to Non-Secure image (sram0_ns).
77 * Of the memory allocated to the Non-Secure image
92 /* Non-Secure image memory */
102 /* Non-Secure application memory */
|
| /Zephyr-latest/boards/nordic/thingy53/ |
| D | Kconfig.defconfig | 12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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
29 # For the non-secure version of the board, the firmware image SRAM is
30 # always restricted to the allocated non-secure SRAM partition.
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/ |
| D | Kconfig.defconfig | 16 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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
33 # For the non-secure version of the board, the firmware image SRAM is
34 # always restricted to the allocated non-secure SRAM partition.
|
| D | bl5340_dvk_nrf5340_cpuapp_partition_conf.dtsi | 12 * implies building Secure and Non-Secure Zephyr images.
18 * Non-Secure image will be placed in slot0_ns, and use
22 * the beginning of the Non-Secure image (not its size).
44 * - Middle 192 kB allocated to Non-Secure image (sram0_ns)
|
| /Zephyr-latest/soc/nxp/imx/imx8m/m7/ |
| D | mpu_regions.c | 24 * Memory with Device type, not executable, not shareable, non-cacheable.
32 * Memory with Normal type, not shareable, non-cacheable
48 * Memory with Normal type, not shareable, non-cacheable
56 * Memory with Normal type, not shareable, non-cacheable
63 * Non-cacheable area is provided in DDR memory, the DDR region [0x80000000 ~ 0x81000000]
68 * space 0x80000000 ~ 0xBFFFFFFF to be non-cacheable. Then MPU region 6 set the text and
74 * Memory with Normal type, not shareable, non-cacheable
|
| /Zephyr-latest/tests/subsys/fs/fat_fs_api/src/ |
| D | test_fat_rename.c | 68 /* Rename non-existing dir to non-existing dir */ in test_rename_dir()
71 TC_PRINT("Renamed non-existent directory\n"); in test_rename_dir()
76 /* Rename existing dir to non-existing dir */ in test_rename_dir()
121 /* Rename non-existing file to non-existing file */ in test_rename_file()
124 TC_PRINT("Renamed non-existent file\n"); in test_rename_file()
129 /* Rename existing file to non-existing file */ in test_rename_file()
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 46 itself is to be executed in the Non-Secure Processing Environment.
48 ensures that the Zephyr image is built as a Non-Secure image. Both
200 secure + non-secure builds (TFM_MCUBOOT_IMAGE_NUMBER == 1).
203 string "Version of the Non-Secure Image"
207 Version of the non-secure image.
218 bool "Use the TF-M Non-Secure application"
222 non-secure application can be built.
223 Usually the TF-M non-secure application is not used since the
224 zephyr application is the non-secure application.
225 With this option enabled this is reversed and the TF-M non-secure
[all …]
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/inc/ |
| D | coex.h | 36 * Returns non-zero upon unsuccessful configuration.
52 * Returns non-zero upon unsuccessful configuration.
60 * @brief Function used to configure non-PTA registers of coexistence hardware.
69 * Returns non-zero upon unsuccessful configuration.
80 * Returns non-zero upon unsuccessful configuration.
|
| /Zephyr-latest/tests/bluetooth/host/keys/bt_keys_store/src/ |
| D | main.c | 58 zassert_true(returned_key != NULL, "bt_keys_get_addr() returned a non-valid reference"); in ZTEST()
65 zassert_true(returned_code == 0, "bt_keys_store() returned a non-zero code"); in ZTEST()
92 zassert_true(returned_key != NULL, "bt_keys_get_addr() returned a non-valid reference"); in ZTEST()
99 zassert_true(returned_code == -1, "bt_keys_store() returned a non-zero code"); in ZTEST()
125 zassert_true(returned_key != NULL, "bt_keys_get_addr() returned a non-valid reference"); in ZTEST()
132 zassert_true(returned_code == 0, "bt_keys_store() returned a non-zero code"); in ZTEST()
159 zassert_true(returned_key != NULL, "bt_keys_get_addr() returned a non-valid reference"); in ZTEST()
166 zassert_true(returned_code == -1, "bt_keys_store() returned a non-zero code"); in ZTEST()
|
| /Zephyr-latest/lib/libc/picolibc/ |
| D | locks.c | 44 /* Create a new dynamic non-recursive lock */
61 /* Close dynamic non-recursive lock */
74 /* Acquiure non-recursive lock */
87 /* Try acquiring non-recursive lock */
100 /* Release non-recursive lock */
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/ |
| D | Kconfig | 63 non-0 "rc" codes.
66 bool "Allow to confirm secondary slot of non-active image"
69 Allows to confirm secondary (non-active) slot of non-active image.
70 Normally it should not be allowed to confirm any slots of non-active
76 bool "Allow to confirm slots of non-active image"
79 Allows to confirm any slot of non-active image.
80 Normally it should not be allowed to confirm any slots of non-active
119 The status list send back from the device will only be filled with data that is non-zero,
120 non-empty or true. This option slightly reduces number of bytes transferred back from
165 Note: setting this to a non-disabled option will prevent uploading of padded and
|
| /Zephyr-latest/lib/libc/minimal/ |
| D | Kconfig | 7 bool "Non-reentrant functions"
11 Enable non-reentrant functions that make use of the globals; e.g.
35 In order to make use of the non-reentrant rand() and srand(), it is
53 In order to make use of the non-reentrant gmtime(), it is necessary
|
| /Zephyr-latest/boards/norik/octopus_io_board/ |
| D | Kconfig.defconfig | 8 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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 | 8 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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/sparkfun/thing_plus/ |
| D | Kconfig.defconfig | 11 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
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.
|
