-
Notifications
You must be signed in to change notification settings - Fork 1
Eeprom interface #355
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
base: main
Are you sure you want to change the base?
Eeprom interface #355
Conversation
EEPROM Directory API Usage GuideOverviewThe EEPROM Directory API provides a simple interface for managing a key-value directory stored on an EEPROM device. This API allows you to persistently store, retrieve, and delete values associated with fixed-size (4-byte) keys, with values up to 16 bytes in size. Key Features
Inputs and OutputsInputs
Outputs
API Functions1.
|
|
This repository includes the same code for this API, as well as additional test code (though it's a bit messy). |
Changes
Completely refactored the EEPROM directory architecture from a partition-based system to a key-value storage system with dynamic block allocation. The new implementation provides a more flexible and efficient way to store and retrieve data in EEPROM.
Notes
middleware/inc/eeprom_directory.h. All other header files (eeprom_alloc.h,eeprom_storage.h,eeprom_directory_struct.h) are internal implementation details and should not be used directly by application code.eeprom_get_base_address()etc. will need to be migrated.Test Cases
To Do
Checklist
It can be helpful to check the
ChecksandFiles changedtabs.Please reach out to your Project Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
Closes # (issue #)