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
FCB support for non-0xFF flash erase values #28693
Comments
Also newly proposed flash_area_ersed_val() might be usefull. |
Also we should consider importing |
Does the fcb2 support the original fcb or this is parallel? |
|
OK then, we will have to add it as an alternative. Do you want me to create enhancement request for importing |
Please go ahead and do it! :-) |
^^ Please count benefits of having fcb2 in compassion to FCB and NVS. |
Is your enhancement proposal related to a problem? Please describe.
Currently FCB is able to work with flash devices that erase to 0xFF values.
Since it's implementation new devices have appeared that use non-0xFF erase values (0x00), which is not supported
by the FCB as it relies on 0xFF as an erased/empty value in some cases.
Describe the solution you'd like
Make FCB flash erase value independent.
Describe alternatives you've considered
There is none as long as FCB is to be used.
Additional context
The flash API now supports
flash_get_parameters
that returnsflash_parameters
structure that haserase_value
member, which is initialized by driver with the erase value.The text was updated successfully, but these errors were encountered: