Searched refs:persistent (Results 1 – 25 of 48) sorted by relevance
12
2 :name: PSA Crypto persistent key4 Manage and use persistent keys via the PSA Crypto API.9 This sample demonstrates usage of persistent keys in the :ref:`PSA Crypto API <psa_crypto>`.16 (for storage of the persistent keys) must be present for this sample to work.
52 When a client connects to a MQTT broker using a persistent session,56 subscribed. When the client reconnects to the persistent session,59 persistent session.
24 the stream write progress to persistent storage so that the operation can resume28 write progress to persistent storage using the :ref:`Settings <settings_api>`
12 from persistent storage and exported to persistent storage using different
19 in the :ref:`persistent storage <bluetooth_mesh_persistent_storage>`.
40 the entire RPL in the persistent storage before it is powered off. Depending on44 storing of RPL entries in the persistent storage.
46 processed by the node. The delay between updating the SRPL and storing the change to the persistent
191 persistent=mocked_hm.options.persistent_hardware_map381 persistent, argument452 mocked_hm.scan(persistent)
179 self.scan(persistent=self.options.persistent_hardware_map)318 def scan(self, persistent=False): argument321 if persistent and platform.system() == 'Linux':
13 for storing and retrieving persistent data.
138 * RTC time is not persistent across application initialization.139 * RTC alarms are not persistent across application initialization.
6 The settings subsystem gives modules a way to store persistent per-device78 This gets called when loading values from persistent storage using82 This gets called when saving a single setting to persistent storage using142 Storing data to persistent storage
85 with persistent lifetime. The users of the PSA API are responsible (WIFI credentials
36 - Generate/import a persistent key: secp256r1 (usage: ecdsa-with-SHA256)39 - Sign the hash with the persistent key45 - Generate/import a persistent key: secp256r1 (usage: ecdsa-with-SHA256)50 Importing/generating the persistent key is based on config option337 [00:00:06.349,000] <inf> app: Destroyed persistent key #1
7 # The user cache can be used for caching of data that should be persistent
11 It allows making use of the PSA Secure Storage API and persistent keys in the PSA Crypto
77 The meshctl utility maintains a persistent JSON database containing
98 The meshctl utility maintains a persistent JSON database containing
20 persistent=no
164 Zephyr's DHCPv4 server does not implement persistent storage of address
307 .. _bluetooth-persistent-storage:313 persistent storage to flash. This requires the presence of a flash
231 Openthread value ahead of the current frame counter for persistent storage.
175 The settings subsystem gives modules a way to store persistent per-device
326 …n attempt on an iface times out, the iface will not attempt to reconnect, even if it is persistent.328 …ied timeout, the iface will try to connect forever until it succeeds, even if it is not persistent.
746 enabled this choice will provide a non-persistent implementation770 might wear out persistent memory.1517 with persistent lifetime. The users of the PSA API is responsible1835 are actually written into persistent storage (flash) after1845 updated in persistent storage (i.e. flash). E.g. a value of 1001863 are written to the persistent storage. Setting this value1866 as the persistent storage setting this value to a low number