/Zephyr-Core-3.5.0/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-Core-3.5.0/subsys/fs/nvs/ |
D | Kconfig | 1 # Non-volatile Storage NVS 7 bool "Non-volatile Storage" 10 Enable support of Non-volatile Storage. 15 bool "Non-volatile Storage lookup cache" 17 Enable Non-volatile Storage cache, used to reduce the NVS data lookup 22 int "Non-volatile Storage lookup cache size" 27 Number of entries in Non-volatile Storage lookup cache.
|
/Zephyr-Core-3.5.0/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-Core-3.5.0/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. 64 bool "NVS non-volatile storage support" 68 Enables NVS storage support 91 Use a custom settings storage back-end. 96 No storage back-end.
|
/Zephyr-Core-3.5.0/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-Core-3.5.0/tests/subsys/storage/stream/stream_flash/ |
D | testcase.yaml | 2 storage.stream_flash: 7 storage.stream_flash.dword_wbs: 13 storage.stream_flash.no_erase: 19 storage.stream_flash.mpu_allow_flash_write:
|
/Zephyr-Core-3.5.0/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>`. 40 This gets called when the value is loaded from persisted storage with 66 This gets called when loading values from persistent storage using 70 This gets called when saving a single setting to persistent storage using 81 Zephyr Storage Backends 84 Zephyr has three storage backends: a Flash Circular Buffer 86 (:kconfig:option:`CONFIG_SETTINGS_FILE`), or non-volatile storage 100 Non-volatile storage read target is registered using [all …]
|
/Zephyr-Core-3.5.0/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-Core-3.5.0/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-Core-3.5.0/include/zephyr/drivers/sensor/ |
D | grow_r502a.h | 27 /** Add values to the sensor which are having record storage facility */ 29 /** To find requested data in record storage */ 31 /** To delete mentioned data from record storage */ 33 /** To get available position to store data on record storage */ 35 /** To empty the storage record*/
|
/Zephyr-Core-3.5.0/samples/tfm_integration/psa_protected_storage/ |
D | README.rst | 3 PSA Protected Storage 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 18 - "Protected Storage sample started" 19 - "PSA Protected Storage API Version [0-9]*.[0-9]*"
|
/Zephyr-Core-3.5.0/samples/subsys/usb/mass/ |
D | sample.yaml | 2 name: Mass Storage 21 - "The device is put in USB mass storage mode." 42 - "The device is put in USB mass storage mode." 61 - "The device is put in USB mass storage mode." 86 - "The device is put in USB mass storage mode." 112 - "The device is put in USB mass storage mode." 133 - "The device is put in USB mass storage mode." 158 - "The device is put in USB mass storage mode."
|
/Zephyr-Core-3.5.0/subsys/storage/ |
D | Kconfig | 6 menu "Storage" menu 8 source "subsys/storage/flash_map/Kconfig" 9 source "subsys/storage/stream/Kconfig"
|
/Zephyr-Core-3.5.0/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-Core-3.5.0/tests/subsys/storage/flash_map/ |
D | testcase.yaml | 2 storage.flash_map: 12 storage.flash_map.mpu: 23 storage.flash_map.mbedtls:
|
/Zephyr-Core-3.5.0/samples/tfm_integration/psa_crypto/src/ |
D | util_app_cfg.h | 16 * @brief The struct used to persist config data to secure storage. 43 * @brief Creates a new config record in secure storage. 50 * @brief Attempts to load the config record from secure storage. If the 51 * record is not found in secure storage, a new record will be created
|
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/dfu/ |
D | dfu_slot.sh | 8 # - First test creates slots and saves them in storage. 9 # - Second test is rebooted device that restores saved slots from storage and checks their state. 13 # from storage.
|
/Zephyr-Core-3.5.0/subsys/settings/src/ |
D | settings_priv.h | 62 /* in storage line contex */ 73 * Read RAW settings line entry data from the storage. 79 * @param[in] cb_arg settings line storage context expected by the 83 * -ERCODE on storage errors 96 * Read the settings line entry name from the storage. 101 * @param[in] cb_arg settings line storage context expected by the 106 * -ERCODE on storage errors
|
/Zephyr-Core-3.5.0/modules/trusted-firmware-m/ |
D | Kconfig.tfm | 145 bool "Override maximum number of Internal Trusted Storage assets" 148 Internal Trusted Storage (ITS) with TFM_ITS_NUM_ASSETS. 151 int "Maximum number of Internal Trusted Storage assets" 155 Maximum number of assets to be stored in Internal Trusted Storage (ITS). 158 bool "Override maximum Internal Trusted Storage asset size" 161 stored in Internal Trusted Storage (ITS) with TFM_ITS_MAX_ASSET_SIZE. 164 int "Maximum Internal Trusted Storage asset size" 169 Storage (ITS). 364 bool "Storage tests" 366 Enable the PSA Protected Storage test suite. [all …]
|
/Zephyr-Core-3.5.0/tests/subsys/settings/fcb_init/src/ |
D | settings_test_fcb_init.c | 15 #include <zephyr/storage/flash_map.h> 109 TC_PRINT("First run: erasing the storage\r\n"); in test_prepare_storage() 111 zassert_true(err == 0, "Can't open storage flash area"); in test_prepare_storage() 114 zassert_true(err == 0, "Can't erase storage flash area"); in test_prepare_storage() 117 zassert_true(err == 0, "Can't open storage flash area"); in test_prepare_storage() 128 TC_PRINT("Storage preparation can't be performed\r\n"); in test_prepare_storage() 129 TC_PRINT("Erase storage manually before test flashing\r\n"); in test_prepare_storage()
|
/Zephyr-Core-3.5.0/doc/kernel/services/other/ |
D | thread_local_storage.rst | 3 Thread Local Storage (TLS) 6 Thread Local Storage (TLS) allows variables to be allocated on a per-thread 16 To enable thread local storage in Zephyr, :kconfig:option:`CONFIG_THREAD_LOCAL_STORAGE` 21 thread local storage and/or the toolchain does not support TLS.
|
/Zephyr-Core-3.5.0/samples/subsys/fs/littlefs/boards/ |
D | bmd_345_eval.conf | 6 # Need this when storage is on flash 9 # Need this when storage is on MX25R64
|
D | nrf52840dk_nrf52840_qspi.conf | 8 # Need this when storage is on flash 11 # Need this when storage is on MX25R64
|
/Zephyr-Core-3.5.0/tests/subsys/logging/log_backend_fs/boards/ |
D | nrf52840dk_nrf52840.conf | 7 # Need this when storage is on flash 10 # Need this when storage is on MX25R64
|