-
Notifications
You must be signed in to change notification settings - Fork 605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[nrf fromlist] ZMS a new memory storage system #2045
Open
rghaddab
wants to merge
9
commits into
nrfconnect:main
Choose a base branch
from
rghaddab:rghaddab/zms-sdk-zephyr
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NordicBuilder
requested review from
anangl,
gmarull,
jaz1-nordic,
kl-cruz,
magp-nordic,
masz-nordic and
nika-nordic
September 24, 2024 15:27
rghaddab
changed the title
ZMS a new memory storage system
[nrf fromlist] ZMS a new memory storage system
Sep 24, 2024
rghaddab
force-pushed
the
rghaddab/zms-sdk-zephyr
branch
3 times, most recently
from
September 25, 2024 15:06
daaddbc
to
51b6183
Compare
NordicBuilder
requested review from
akredalen,
alxelax,
Andrewpini,
HaavardRei,
jfischer-no,
omkar3141 and
PavelVPV
September 25, 2024 15:07
This was referenced Sep 25, 2024
rghaddab
force-pushed
the
rghaddab/zms-sdk-zephyr
branch
7 times, most recently
from
September 27, 2024 20:11
65890a5
to
2e1916d
Compare
rghaddab
force-pushed
the
rghaddab/zms-sdk-zephyr
branch
from
September 28, 2024 05:33
2e1916d
to
64981a6
Compare
rghaddab
force-pushed
the
rghaddab/zms-sdk-zephyr
branch
3 times, most recently
from
October 1, 2024 00:20
b573411
to
d7c1422
Compare
The commit adds and no_explicit_erase capability to flash_parameters, that indicates whether device is program-erase type device; such devices, like Flash type devices, require erase prior to writing random data at any previously programmed location. This capability should only be set by drivers. The flash_params_get_erase_cap() function has been added, for parsing flash_parameters object to obtain erase capabilities of device. The function returns capabilities as combination of bits representing them. Currently it will return: 0 -- no erase capabilities FLASH_ERASE_C_EXPLICIT -- erase required before write of random data. Additional capabilities have been reserved but are not yet used. There are following Kconfig options added: FLASH_HAS_EXPLICIT_ERASE FLASH_HAS_NO_EXPLICIT_ERASE that should be selected by device driver to indicate whether devices served by driver needs erase prior to write. The above Kconfigs are used to figure out whether app is built for hardware that requires erase prior to write. They can be also used to detect that it is attempted to build some subsystem that will not work with provided hardware, for example file system that has not been prepared to work with devices that do not require erase. Signed-off-by: Dominik Ermel <[email protected]> (cherry picked from commit b3c9f95)
…RASE Select CONFIG_FLASH_HAS_EXPLICIT_ERASE for the NRF driver. Signed-off-by: Dominik Ermel <[email protected]> (cherry picked from commit 6d75bc5)
…ty to true NRF RRAM does not require erase prior to re-programming already written area. Signed-off-by: Dominik Ermel <[email protected]> (cherry picked from commit 127bc5e)
…ty to true NRF MRAM does not require erase prior to re-programming already written area. Signed-off-by: Dominik Ermel <[email protected]> (cherry picked from commit 0e970c8)
Add a Kconfig.constants file that defines variables for different known integer minimum and maximum values. Signed-off-by: Pieter De Gendt <[email protected]> (cherry picked from commit dfdebc9)
rghaddab
force-pushed
the
rghaddab/zms-sdk-zephyr
branch
from
October 1, 2024 09:02
d7c1422
to
23e9623
Compare
de-nordic
approved these changes
Oct 3, 2024
de-nordic
requested review from
tomi-font and
Damian-Nordic
and removed request for
Andrewpini
October 3, 2024 10:57
ZMS is the abreviation of Zephyr Memory Storage. It is a storage developed to target especially the non erasable devices. The new memory storage system inherit from the NVS storage multiple features and introduce new ones : * Inherited features : - light key-value based storage - cache for entries - Wear Leveling of flash memory - Resilience to power failures * New features : - cycle counter for non erasable devices (instead of erase emulation) - Keys up to 32-bit - Built-in support of CRC32 for data - Small size data (<= 8 bytes) integrated within entries Upstream PR: zephyrproject-rtos/zephyr#77930 Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit 7bf5d179cc5d586fb3cf4564f92cea7b66b0e964)
List of added tests : - zms.test_delete - zms.test_zms_cache_collission - zms.test_zms_cache_gc - zms.test_zms_cache_hash_quality - zms.test_zms_cache_init - zms.test_zms_corrupted_sector_close_operation - zms.test_zms_corrupted_write - zms.test_zms_full_sector - zms.test_zms_gc - zms.test_zms_gc_3sectors - zms.test_zms_gc_corrupt_ate - zms.test_zms_gc_corrupt_close_ate - zms.test_zms_mount - zms.test_zms_write Upstream PR: zephyrproject-rtos/zephyr#77930 Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit 1f4e92c3da4b738d2dd203348d7a93f5ccdb5b99)
This adds a user application that shows the usage of ZMS The sample app shows three main functions of ZMS: - read/write/delete key/value pairs - fill all storage and delete it - calculate free remaining space Upstream PR: zephyrproject-rtos/zephyr#77930 Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit c479fadad817a84da18ea2f2e1873cebbd9c1f12)
…orage) This adds the initial backend support for the ZMS storage system. Upstream PR: zephyrproject-rtos/zephyr#78632 Signed-off-by: Riadh Ghaddab <[email protected]> (cherry picked from commit 85bc1f8cd205fc3de17ebca2774acaf595cac16c)
rghaddab
force-pushed
the
rghaddab/zms-sdk-zephyr
branch
from
October 3, 2024 19:59
23e9623
to
84144c6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new storage system ZMS and its backend for settings.
It adds as well all the dependencies for this storage fromtree zephyrproject-rtos:main