Home
last modified time | relevance | path

Searched full:stored (Results 1 – 25 of 440) sorted by relevance

12345678910>>...18

/Zephyr-Core-3.4.0/subsys/net/lib/lwm2m/
DKconfig.ucifi49 device that can be stored in this object.
57 device that can be stored in this object.
65 to a device that can be stored in this object.
74 stored in this object.
82 that can be stored in this object.
91 that can be stored in this object.
100 be stored in this object.
/Zephyr-Core-3.4.0/tests/subsys/debug/coredump_backends/src/
Dmain.c70 /* There should be a stored coredump now if backend has storage */ in test_query_stored_dump()
78 TC_PRINT("Should have stored dump!\n"); in test_query_stored_dump()
81 TC_PRINT("Error reading stored dump! (%d)\n", ret); in test_query_stored_dump()
93 /* There should be a stored coredump now if backend has storage */ in test_verify_stored_dump()
101 TC_PRINT("Verification of stored dump failed!\n"); in test_verify_stored_dump()
104 TC_PRINT("Error reading stored dump! (%d)\n", ret); in test_verify_stored_dump()
/Zephyr-Core-3.4.0/subsys/debug/coredump/
Dcoredump_backend_flash_partition.c28 * On the partition, a header is stored at the beginning with padding
225 * @brief Process the stored coredump in flash partition.
227 * This reads the stored coredump data and processes it via
230 * @param cb callback to process the stored coredump data
232 * @return 1 if successful; 0 if stored coredump is not found
277 * @brief Get the stored coredump in flash partition.
279 * This reads the stored coredump data and copies the raw data
288 * @return dump size if successful; 0 if stored coredump is not found
345 * @brief Erase the stored coredump header from flash partition.
347 * This erases the stored coredump header from the flash partition,
[all …]
/Zephyr-Core-3.4.0/tests/bluetooth/mesh/rpl/src/
Dmain.c173 /* Entries with old_iv == true should be removed, others should be stored. */ in expect_pending_store()
259 * stored after the reset operation is finished.
285 /** Test that RPL accepts and stores a valid entry that was just stored. The entry should be stored
294 * address and correct IVI after the entry was stored. in ZTEST()
312 * be stored during the reset operation.
342 /* Test that RPL accepts and stores a valid entry that has not yet been stored. The entry should be
343 * stored during the reset operation.
349 /* Take RPL entry from test vector that has old_iv == false and is not stored yet after in ZTEST()
365 /* The entry should have been stored in previous bt_mesh_rpl_pending_store() call. Another in ZTEST()
374 * The entry will be added at the end of RPL, therefore it should be stored during the reset
[all …]
/Zephyr-Core-3.4.0/include/zephyr/debug/
Dcoredump.h22 * Check if there is a stored coredump from backend.
24 * Returns 1 if there is a stored coredump.
52 * Verify that the stored coredump is valid.
55 * 0 if not valid or no stored coredump.
62 * Erase the stored coredump.
71 * Copy the raw stored coredump.
74 * 0 if stored coredump is not found
81 * Invalidate the stored coredump. This is faster than
291 * Perform certain on coredump subsystem, for example, output the stored
/Zephyr-Core-3.4.0/samples/tfm_integration/psa_protected_storage/
DREADME.rst17 be stored to and read from UIDs, and how overwrite protection can be enabled using flags.
59 Info on data stored in UID1:
63 Read and compare data stored in UID1
64 Data stored in UID1: The quick brown fox jumps over the lazy dog
65 Overwriting data stored in UID1 with: Lorem ipsum dolor sit amet
/Zephyr-Core-3.4.0/samples/tfm_integration/psa_protected_storage/src/
Dmain.c42 printk("Info on data stored in UID1:\n"); in main()
47 printk("Read and compare data stored in UID1\n"); in main()
53 printk("Failed to get data stored in UID1! (%d)\n", status); in main()
56 printk("Data stored in UID1: %s\n", stored_data); in main()
58 printk("Overwriting data stored in UID1: %s\n", TEST_STRING_2); in main()
/Zephyr-Core-3.4.0/include/zephyr/sys/
Dbyteorder.h366 * @brief Get a 16-bit integer stored in big-endian format.
368 * Get a 16-bit integer, stored in big-endian format in a potentially
381 * @brief Get a 24-bit integer stored in big-endian format.
383 * Get a 24-bit integer, stored in big-endian format in a potentially
396 * @brief Get a 32-bit integer stored in big-endian format.
398 * Get a 32-bit integer, stored in big-endian format in a potentially
411 * @brief Get a 48-bit integer stored in big-endian format.
413 * Get a 48-bit integer, stored in big-endian format in a potentially
426 * @brief Get a 64-bit integer stored in big-endian format.
428 * Get a 64-bit integer, stored in big-endian format in a potentially
[all …]
Dlinear_range.h137 * @param[out] val Where value will be stored.
160 * @param[out] val Where value will be stored.
181 * If the value falls outside the range, the nearest index will be stored and
188 * @param[out] idx Where index will be stored.
225 * @param[out] idx Where index will be stored.
252 * intersect), the nearest index will be stored and -ERANGE returned.
257 * @param[out] idx Where index will be stored.
309 * @param[out] idx Where index will be stored.
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/api/mesh/
Dcore.rst51 which RPL entries are to be stored in this case.
75 the change needs to be stored persistently, the stack schedules a work item.
81 When IV index, Sequence Number or CDB configuration have to be stored, the work
87 stored, the delay is set to :kconfig:option:`CONFIG_BT_MESH_RPL_STORE_TIMEOUT`.
88 If other stack configuration has to be stored, the delay defined by
104 workqueue, while the stack configuration is being stored.
/Zephyr-Core-3.4.0/doc/kernel/data_structures/
Dspsc_pbuf.rst7 buffer, whose contents are stored in first-in-first-out order. Variable size
8 packets are stored in the buffer. Packet buffer works under assumption that there
/Zephyr-Core-3.4.0/drivers/ieee802154/
DKconfig.nrf542 bool "Support usage of EUI64 value stored in UICR registers"
47 stored in User information configuration registers (UICR).
61 section in which custom EUI64 is stored.
/Zephyr-Core-3.4.0/include/zephyr/xen/
Dgeneric.h30 ({ __typeof__(*ptr) stored = old; \
31 __atomic_compare_exchange_n(ptr, &stored, new, 0, __ATOMIC_SEQ_CST, \
/Zephyr-Core-3.4.0/include/zephyr/drivers/
Dcoredump.h31 * stored in core dump at the time it is generated
105 * @brief Register a region of memory to be stored in core dump at the
124 * @brief Unregister a region of memory to be stored in core dump at the
/Zephyr-Core-3.4.0/tests/bsim/bluetooth/host/gatt/ccc_store/
Dprj_2.conf24 # Test that CCC is stored even if BT_SETTINGS_DELAYED_STORE is enabled
/Zephyr-Core-3.4.0/doc/services/storage/nvs/
Dnvs.rst6 Elements, represented as id-data pairs, are stored in flash using a
14 at least one id-data pair stored in flash at all time.
19 Each element is stored in flash as metadata (8 byte) and data. The metadata is
28 During initialization NVS will verify the data stored in flash, if it
/Zephyr-Core-3.4.0/include/zephyr/storage/
Dstream_flash.h38 * This enables verifying that the data has been correctly stored (for
57 size_t buf_bytes; /* Number of bytes currently stored in write buf */
133 * @brief Load persistent stream write progress stored with key
162 * @brief Clear persistent stream write progress stored with key
/Zephyr-Core-3.4.0/samples/boards/reel_board/mesh_badge/
DREADME.rst42 word (name) of the stored text will be sent to all other boards in
45 To reset a board to its initial state (disable mesh, erase the stored
/Zephyr-Core-3.4.0/tests/subsys/shell/shell_history/src/
Dshell_history_test.c138 /* Function for getting maximal buffer size that can be stored in the history */
160 /* Test verifies that line that cannot fit into history buffer is not stored.
179 /*validate that nothing is stored */ in ZTEST()
192 /* Test verifies that same line as the previous one is not stored in the
211 /* only one line stored. */ in ZTEST()
/Zephyr-Core-3.4.0/tests/kernel/device/src/
Dmain.c275 * sequence number that each driver stored during initialization. If the
276 * sequence of initial level stored is corresponding with our expectation, it
285 /* we check if the stored executing sequence for different level is in ZTEST()
302 * sequence number that each driver stored during initialization. If the
303 * sequence of initial priority stored is corresponding with our expectation, it
312 /* we check if the stored pexecuting sequence for priority is correct, in ZTEST()
/Zephyr-Core-3.4.0/samples/sensor/grow_r502a/
DREADME.rst11 #. Shows the number of fingerprints stored in the sensor.
59 Fingerprint successfully stored at #0
/Zephyr-Core-3.4.0/drivers/i2s/
DKconfig.litex28 bool "Received data will be stored as big endian"
/Zephyr-Core-3.4.0/include/zephyr/bluetooth/mesh/
Dcdb.h100 * Remove all nodes, subnets and app-keys stored in the database and mark
108 * The IV Index stored in the CDB will be the one used during provisioning
188 * @param node Node to be stored.
251 * @param sub Subnet to be stored.
298 * @param key Application key to be stored.
/Zephyr-Core-3.4.0/include/zephyr/bluetooth/
Dtesting.h68 * be stored by Friend node.
79 * subscription list. Messages sent to those addresses will not be stored
/Zephyr-Core-3.4.0/boards/posix/nrf52_bsim/cmsis/
Dcmsis_instr.h112 * instead just loads the stored value
125 * instead just loads the stored value
138 * instead just loads the stored value

12345678910>>...18