[nrf noup] drivers: flash: nrf_mram: wait until mramc is ready before write #3613
+106
−7
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
NordicBuilder
added a commit
to NordicBuilder/sdk-nrf
that referenced
this pull request
Dec 5, 2025
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-zephyr#3613 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
rghaddab
force-pushed
the
rghaddab-sdk-zephyr/mram-wait-ready
branch
from
823cd28 to
c389b3f
Compare
NordicBuilder
added a commit
to NordicBuilder/sdk-nrf
that referenced
this pull request
Dec 5, 2025
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-zephyr#3613 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
NordicBuilder
added a commit
to NordicBuilder/sdk-nrf
that referenced
this pull request
Dec 8, 2025
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-zephyr#3613 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
rghaddab
force-pushed
the
rghaddab-sdk-zephyr/mram-wait-ready
branch
2 times, most recently
from
921ba32 to
a21e162
Compare
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
github-actions
bot
added
manifest
manifest-hal_nordic
and removed
manifest
manifest-hal_nordic
labels
… write When writes are issued to the mram controller without verifying that it is ready, it can cause the reads to be stalled until all writes finish. Fix this by adding a wait busy loop before each MRAM_WORD aligned write and disable autopowerdown before starting the write. Signed-off-by: Riadh Ghaddab <riadh.ghaddab@nordicsemi.no>
Lilium targets do not support No-Multithreading scenarios. Disable the corresponding test in MSPI. Signed-off-by: Riadh Ghaddab <riadh.ghaddab@nordicsemi.no>
Multithreading should be enabled by default for nrf54h20_cpuapp target Signed-off-by: Riadh Ghaddab <riadh.ghaddab@nordicsemi.no>
rghaddab
force-pushed
the
rghaddab-sdk-zephyr/mram-wait-ready
branch
from
a21e162 to
d54af07
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 writes are issued to the mram controller without verifying that it is ready, it can cause the reads to be stalled until all writes finish. Fix this by adding a wait busy loop before each MRAM_WORD aligned write and disable autopowerdown before starting the write.