Home
last modified time | relevance | path

Searched refs:wear (Results 1 – 8 of 8) sorted by relevance

/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dcore.rst42 can make flash wear out sooner or later. To mitigate this,
54 switch off the timer, which can help to significantly reduce flash wear out.
61 vulnerability and flash wear out.
Daccess.rst153 increased wear of flash. To reduce the wear, the model can postpone storing of
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst72 Flash wear
75 When writing data to flash a study of the flash wear is important. Flash has a
/Zephyr-latest/subsys/fs/
DKconfig.littlefs65 For dynamic wear leveling, the number of erase cycles before data
/Zephyr-latest/doc/services/storage/zms/
Dzms.rst364 - Add the possibility to retrieve the wear out value of the device based on the cycle count value
397 life expectancy of the device described in this section: `Wear leveling <#wear-leveling>`_.
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig772 might wear out persistent memory.
1877 may wear out flash sooner or later. However, if the RPL gets
1885 may reduce a risk of security vulnerability and flash wear out.
/Zephyr-latest/subsys/bluetooth/host/
DKconfig745 time a successful pairing occurs. This increases flash wear out but offers
/Zephyr-latest/doc/releases/
Drelease-notes-1.12.rst212 * Mesh-specific optimizations to avoid flash wear