Skip to content
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

Implement EEPROM Emulation block device on NOR/NAND Flash #15466

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

daniel-0723
Copy link

Summary of changes

EEPROMs have the ability to update individual bytes of memory million times over and the programmed locations retain the data over a long period even when the system is powered down.
We create a VEE(vitual EEPROM Emulation) on Flash to approaches to Flash like EEPROM.
The Flash could be SPI/QSPI/OSPI NOR Flash or SPI NAND Flash.

Impact of changes

Migration actions required

Documentation


Pull request type

[] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[x] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[x] Tests / results supplied as part of this PR

This driver is tested on DISCO_L4R9I.
target platform_name test suite test case passed failed result elapsed_time (sec)
DISCO_L4R9I-GCC_ARM DISCO_L4R9I storage-blockdevice-tests-tests-blockdevice-vee_block_device Testing background thread 1 0 OK 619.72
DISCO_L4R9I-GCC_ARM DISCO_L4R9I storage-blockdevice-tests-tests-blockdevice-vee_block_device Testing read write random blocks 1 0 OK 1.15

Reviewers


@daniel-0723 daniel-0723 changed the title add VEE block device driver Implement EEPROM Emulation block device on NOR/NAND Flash Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants