| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 3 Secure storage
6 | The secure storage subsystem provides an implementation of the functions defined in the
7 …`Platform Security Architecture (PSA) Secure Storage API <https://arm-software.github.io/psa-api/s…
14 The secure storage subsystem makes the PSA Secure Storage API available on all board targets with
23 may secure the data stored via the PSA Secure Storage API at rest.
30 The secure storage subsystem's implementation of the PSA Secure Storage API:
41 * does not yet provide an implementation of the Protected Storage (PS) API as of this writing.
43 Instead, the PS API directly calls into the Internal Trusted Storage (ITS) API
50 …ernal Trusted Storage requirements <https://arm-software.github.io/psa-api/storage/1.0/overview/re…
52 | The specification considers the storage underlying the ITS to be
[all …]
|
| /Zephyr-latest/subsys/usb/device/class/ |
| D | Kconfig.msc | 5 bool "USB Mass Storage Device Class support"
8 USB Mass Storage device class support
13 string "Mass storage disk or drive name"
16 Mass storage device disk or drive name
44 Mass storage device class bulk endpoints size
47 int "Set stack size for mass storage thread"
51 Stack size for mass storage disk operations thread
54 module-str = usb mass storage
|
| /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"
|
| /Zephyr-latest/subsys/fs/zms/ |
| D | Kconfig | 5 #Zephyr Memory Storage ZMS
8 bool "Zephyr Memory Storage"
11 Enable support of Zephyr Memory Storage.
23 int "ZMS Storage lookup cache size"
43 Increasing this buffer means as well that ZMS could work with storage devices
54 bool "Avoid writing the same data again in the storage"
58 Enable this config to avoid rewriting data in the storage if it already exists.
60 data in the whole storage before any write.
|
| /Zephyr-latest/tests/subsys/storage/stream/stream_flash/ |
| D | testcase.yaml | 8 storage.stream_flash:
14 storage.stream_flash.simulator.no_explicit_erase:
19 storage.stream_flash.no_explicit_erase:
24 storage.stream_flash.dword_wbs:
27 storage.stream_flash.no_erase:
|
| /Zephyr-latest/subsys/settings/ |
| D | Kconfig | 19 bool "runtime storage back-end"
21 Enables runtime storage back-end.
34 prompt "Storage back-end"
40 Storage back-end to be used by the settings subsystem.
46 Use FCB as a settings storage back-end.
53 Use a file (on mounted file system) as a settings storage back-end.
56 bool "NVS non-volatile storage support"
60 Enables NVS storage support
83 Use a custom settings storage back-end.
88 No storage back-end.
|
| /Zephyr-latest/subsys/secure_storage/include/psa/ |
| D | internal_trusted_storage.h | 7 /** @file psa/internal_trusted_storage.h The PSA Internal Trusted Storage (ITS) API.
9 …Internal Trusted Storage API](https://arm-software.github.io/psa-api/storage/1.0/overview/architec…
30 * Stores data in the internal storage.
44 * @retval PSA_ERROR_INSUFFICIENT_STORAGE There is insufficient space on the storage medium.
45 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
70 * @retval PSA_ERROR_DOES_NOT_EXIST The provided `uid` was not found in the storage.
71 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
91 * @retval PSA_ERROR_DOES_NOT_EXIST The provided `uid` was not found in the storage.
92 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
105 * Deletes all the data associated with the entry from internal storage.
[all …]
|
| D | protected_storage.h | 7 /** @file psa/protected_storage.h The PSA Protected Storage (PS) API.
9 … see [The Protected Storage API](https://arm-software.github.io/psa-api/storage/1.0/overview/archi…
43 * @retval PSA_ERROR_INSUFFICIENT_STORAGE There is insufficient space on the storage medium.
44 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
74 * @retval PSA_ERROR_DOES_NOT_EXIST The provided `uid` was not found in the storage.
75 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
102 * @retval PSA_ERROR_DOES_NOT_EXIST The provided `uid` was not found in the storage.
103 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
132 * @retval PSA_ERROR_DOES_NOT_EXIST The provided `uid` was not found in the storage.
133 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
[all …]
|
| D | storage_common.h | 7 * @defgroup psa_secure_storage PSA Secure Storage API
9 * @details For more information on the PSA Secure Storage API, see the
10 * [PSA Certified Secure Storage API](https://arm-software.github.io/psa-api/storage/1.0/)
16 * @brief Common definitions of the PSA Secure Storage API.
39 /** The allocated capacity of the storage associated with an entry. */
|
| /Zephyr-latest/samples/tfm_integration/psa_protected_storage/ |
| D | README.rst | 2 :name: TF-M PSA Protected Storage
4 Use the Protected Storage (PS) API to store encrypted data.
9 This sample demonstrates how the Protected Storage (PS) API can be used for storing data.
11 Protected storage provides a key/value storage interface where data is (by default) encrypted, with
16 Using the PS API, this sample stores data to non-volatile storage. The sample shows how data can
24 More information about Protected Storage can be found in the Platform Security Architecture (PSA)
25 Secure Storage API: https://developer.arm.com/architectures/architecture-security-features/platform…
57 TF-M Protected Storage sample started. PSA Protected Storage API Version 1.0
|
| D | sample.yaml | 2 description: Protected Storage API sample
3 name: PSA Protected Storage
19 - "Protected Storage sample started"
20 - "PSA Protected Storage API Version [0-9]*.[0-9]*"
|
| /Zephyr-latest/tests/subsys/settings/functional/file/ |
| D | settings_test_file.c | 13 void *storage; in ZTEST() local
17 rc = settings_storage_get(&storage); in ZTEST()
18 zassert_equal(0, rc, "Can't fetch storage reference (err=%d)", rc); in ZTEST()
20 zassert_not_null(storage, "Null reference."); in ZTEST()
22 rc = fs_stat((const char *)storage, &entry); in ZTEST()
|
| /Zephyr-latest/tests/subsys/debug/coredump_backends/ |
| D | Kconfig | 8 bool "Expected backend has coredump storage."
10 Set if the test expects coredump backend with storage.
13 int "Expected backend's coredump storage size."
16 Test expects coredump backend storage with the size given.
|
| /Zephyr-latest/modules/canopennode/ |
| D | canopennode.h | 32 * @brief CANopen object dictionary storage types.
45 * @brief Attach CANopen object dictionary storage handlers.
47 * Attach CANopen storage handler functions to object dictionary
53 * CANOPEN_STORAGE_ROM to non-volatile storage when a CANopen SDO
59 * non-volatile storage when a CANopen SDO client writes 0x64616F6C
68 * never saved to non-volatile storage.
76 * @brief Save CANopen object dictionary entries to non-volatile storage.
79 * storage.
81 * @param storage CANopen object dictionary entry type
85 int canopen_storage_save(enum canopen_storage storage);
[all …]
|
| /Zephyr-latest/tests/subsys/settings/functional/fcb/ |
| D | settings_test_fcb.c | 13 void *storage; in ZTEST() local
17 rc = settings_storage_get(&storage); in ZTEST()
18 zassert_equal(0, rc, "Can't fetch storage reference (err=%d)", rc); in ZTEST()
20 zassert_not_null(storage, "Null reference."); in ZTEST()
23 rc = fcb_getnext((struct fcb *)storage, &loc); in ZTEST()
|
| /Zephyr-latest/tests/subsys/settings/functional/nvs/ |
| D | settings_test_nvs.c | 13 void *storage; in ZTEST() local
17 rc = settings_storage_get(&storage); in ZTEST()
18 zassert_equal(0, rc, "Can't fetch storage reference (err=%d)", rc); in ZTEST()
20 zassert_not_null(storage, "Null reference."); in ZTEST()
22 nvs_rc = nvs_write((struct nvs_fs *)storage, 26, &data, sizeof(data)); in ZTEST()
|
| /Zephyr-latest/samples/psa/its/ |
| D | README.rst | 2 :name: PSA Internal Trusted Storage API
11 …ernal Trusted Storage (ITS) API <https://arm-software.github.io/psa-api/storage/1.0/overview/archi…
12 which is part of the `PSA Secure Storage API <https://arm-software.github.io/psa-api/storage/>`_,
22 * The :ref:`secure storage subsystem <secure_storage>`, for the other board targets.
45 .. tab:: secure storage subsystem
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig | 5 bool "Secure storage subsystem"
9 The secure storage subsystem provides an implementation of the PSA Secure Storage API
11 It allows making use of the PSA Secure Storage API and persistent keys in the PSA Crypto
15 In addition to providing functional support for the PSA Secure Storage API, depending on
28 prompt "Internal Trusted Storage (ITS) API implementation"
70 The module that handles the storage/retrieval of the ITS data to/from NVM.
78 prompt "Protected Storage (PS) API implementation"
|
| D | Kconfig.its_store | 13 bool "ITS store module implementation using ZMS for storage"
19 This implementation of the ITS store module makes direct use of ZMS for storage.
21 to a fixed storage partition that will be dedicated to the ITS. It has lower
23 execution and storage space, and also ROM footprint if the settings subsystem is disabled.
24 As this implementations directly maps the PSA storage UIDs to ZMS entry IDs, it limits
28 bool "ITS store module implementation using the settings subsystem for storage"
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | sample.yaml | 2 name: Mass Storage
21 - "The device is put in USB mass storage mode."
47 - "The device is put in USB mass storage mode."
66 - "The device is put in USB mass storage mode."
91 - "The device is put in USB mass storage mode."
117 - "The device is put in USB mass storage mode."
139 - "The device is put in USB mass storage mode."
162 - "The device is put in USB mass storage mode."
187 - "The device is put in USB mass storage mode."
|
| /Zephyr-latest/subsys/storage/ |
| D | Kconfig | 6 menu "Storage" menu
8 source "subsys/storage/flash_map/Kconfig"
9 source "subsys/storage/stream/Kconfig"
|
| /Zephyr-latest/tests/subsys/storage/flash_map/ |
| D | testcase.yaml | 2 storage.flash_map:
13 storage.flash_map.mpu:
25 storage.flash_map_sha.mbedtls:
36 storage.flash_map_sha.psa:
|
| /Zephyr-latest/dts/bindings/misc/ |
| D | zephyr,flash-disk.yaml | 4 description: Block storage device on flash partition
15 Backing storage flash map partition.
34 adequately chosen. On storage backends with uniform erase-blocks it
35 should be at least the erase-block-size, on storage backends with
|
| /Zephyr-latest/doc/services/settings/ |
| D | index.rst | 7 configuration and runtime state. A variety of storage implementations are
10 appropriate storage medium, and even change it later as needs change. This
27 storage is :ref:`NVS <nvs_api>`.
42 This gets called when the value is loaded from persisted storage with
78 This gets called when loading values from persistent storage using
82 This gets called when saving a single setting to persistent storage using
93 Zephyr Storage Backends
96 Zephyr has three storage backends: a Flash Circular Buffer
98 (:kconfig:option:`CONFIG_SETTINGS_FILE`), or non-volatile storage
112 Non-volatile storage read target is registered using
[all …]
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 3 Zephyr Memory Storage (ZMS)
5 Zephyr Memory Storage is a new key-value storage system that is designed to work with all types
6 of non-volatile storage technologies. It supports classical on-chip NOR flash as well as new
99 Mounting the Storage system
102 Mounting the storage starts by getting the flash parameters, checking that the file system
104 make the storage ready.
114 /** Storage system is split into sectors, each sector size must be multiple of
185 Some applications need to make sure that storage writes have a maximum defined latency.
214 * such as storage version.
286 This storage system is optimized for devices that do not require an erase.
[all …]
|
