esp-idf/components/wear_levelling
2017-10-19 21:35:21 +08:00
..
doc add wear_levelling component and example 2017-04-17 11:01:17 +08:00
include add wear_levelling component and example 2017-04-17 11:01:17 +08:00
private_include Added component to change standard size of the flash device. Now the sector size could be less. The configuration supports it. 2017-07-31 13:19:36 +03:00
test unit test: adapt tests to single core configuration 2017-10-19 21:35:21 +08:00
test_wl_host wear_levelling: run host side test in CI 2017-04-17 11:01:18 +08:00
.gitignore nvs_flash, wear_levelling: ignore host test files 2017-04-17 11:01:18 +08:00
component.mk add wear_levelling component and example 2017-04-17 11:01:17 +08:00
crc32.cpp add wear_levelling component and example 2017-04-17 11:01:17 +08:00
crc32.h add wear_levelling component and example 2017-04-17 11:01:17 +08:00
Kconfig Fix: tests now process correct. The length of written array now fit to the defined range. 2017-08-09 09:35:32 +03:00
Partition.cpp add wear_levelling component and example 2017-04-17 11:01:17 +08:00
README.rst Typos correction. 2017-07-31 13:19:41 +03:00
SPI_Flash.cpp add wear_levelling component and example 2017-04-17 11:01:17 +08:00
wear_levelling.cpp Added component to change standard size of the flash device. Now the sector size could be less. The configuration supports it. 2017-07-31 13:19:36 +03:00
WL_Ext_Perf.cpp Fix: tests now process correct. The length of written array now fit to the defined range. 2017-08-09 09:35:32 +03:00
WL_Ext_Safe.cpp Log level changed to remove useless info. 2017-08-09 10:25:40 +03:00
WL_Flash.cpp wear_levelling: fix write and read length for single access was wrong. 2017-07-17 12:00:40 +03:00

Wear Levelling APIs
===================

Overview
--------
Most of the flash devices and specially SPI flash devices that are used in ESP32
have sector based organization and have limited amount of erase/modification cycles
per memory sector. To avoid situation when one sector reach the limit of erases when
other sectors was used not often, we have made a component that avoid this situation.
The wear levelling component share the amount of erases between all sectors in the
memory without user interaction.
The wear_levelling component contains APIs related to reading, writing, erasing,
memory mapping data in the external SPI flash through the partition component. It
also has higher-level APIs which work with FAT filesystem defined in
the :doc:`FAT filesystem </api-reference/storage/fatfs>`.

The wear levelling component, together with FAT FS component, works with FAT FS sector size 4096
bytes which is standard size of the flash devices. In this mode the component has best performance,
but needs additional memoty in the RAM. To save internal memory the component has two additional modes
to work with sector size 512 bytes: Performance and Safety modes. In Performance mode by erase sector
operation data will be stored to the RAM, sector will be erased and then data will be stored
back to the flash. If by this operation power off situation will occur, the complete 4096 bytes
will be lost. To prevent this the Safety mode was implemented. In safety mode the data will be first
stored to the flash and after sector will be erased, will be stored back. If power off situation will
occur, after power on, the data will be recovered.
By default defined the sector size 512 bytes and Performance mode. To change these values please use
the configuration menu.


The wear levelling component does not cache data in RAM. Write and erase functions
modify flash directly, and flash contents is consistent when the function returns.


Wear Levelling access APIs
--------------------------

This is the set of APIs for working with data in flash:

- ``wl_mount`` mount wear levelling module for defined partition
- ``wl_unmount`` used to unmount levelling module
- ``wl_erase_range`` used to erase range of addresses in flash
- ``wl_write`` used to write data to the partition
- ``wl_read`` used to read data from the partition
- ``wl_size`` return size of avalible memory in bytes
- ``wl_sector_size`` returns size of one sector

Generally, try to avoid using the raw wear levelling functions in favor of
filesystem-specific functions.

Memory Size
-----------

The memory size calculated in the wear Levelling module based on parameters of
partition. The module use few sectors of flash for internal data.