bm_zms: fix a bug in case of read after a write#778
Merged
eivindj-nordic merged 1 commit intonrfconnect:mainfrom Apr 28, 2026
Merged
bm_zms: fix a bug in case of read after a write#778eivindj-nordic merged 1 commit intonrfconnect:mainfrom
eivindj-nordic merged 1 commit intonrfconnect:mainfrom
Conversation
52eb5e4 to
3cdeff3
Compare
|
You can find the documentation preview for this PR here. |
When a read is triggered immediately after a write it can start just after a sector is closed and picks up the wrong address to start the search from. Fix this by storing a backup read address before closing a sector. Signed-off-by: Riadh Ghaddab <riadh.ghaddab@nordicsemi.no>
3cdeff3 to
1cc328f
Compare
anhmolt
approved these changes
Apr 27, 2026
lemrey
approved these changes
Apr 28, 2026
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
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.
When a read is triggered immediately after a write it can start just after a sector is closed and picks up the wrong address to start the search from.
Fix this by storing a backup read address before closing a sector.