Flash simulator callbacks #100512
Open
Flash simulator callbacks #100512
+421
−11
Conversation
This file contains hidden or 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
zephyrbot
added
area: Tests
rkel
force-pushed
the
flash_simulator_callbacks
branch
from
9789d4c to
f92c25c
Compare
Contributor
Author
|
I need to work on it little more - I did not realize that FLASH simulator is used in samples. First I will fix the errors, and then add an option to enable the callbacks functionality. |
rkel
force-pushed
the
flash_simulator_callbacks
branch
2 times, most recently
from
812995f to
7f6e275
Compare
Add the functionality that allows to register write and erase callbacks. The callbacks can modify the behaviour of this operations. It are meant to be used during testing of the situation when the memory starts to generate errors or the data cannot be trusted anymore. It expands the testing possibility, for a situation when the module is tested that checks the data integrity and and we cannot just jump in between its internal write and read operations to inject an error. Signed-off-by: Radosław Koppel <[email protected]>
rkel
force-pushed
the
flash_simulator_callbacks
branch
from
7f6e275 to
ec9a43c
Compare
This test checks the functionality of the callbacks for erase and write operations. The callbacks allows the modification of the simulated flash behaviour during this operations. Signed-off-by: Radosław Koppel <[email protected]>
rkel
force-pushed
the
flash_simulator_callbacks
branch
from
ec9a43c to
cdcdff5
Compare
Contributor
Author
|
I had added test teardown function to callbacks test that removes the registered callbacks. |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Implement a functionality to set write and erase callbacks that can modify the simulation on the fly when the operations are in progress. This allows simulation for modules that takes care about data integrity and should react when anything breaks when accessing FLASH.
I did not implement read operation callback as when reading we can usually modify the memory content before calling a module operation that uses it.