cache: flush cache on reset #22
Open
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.
Right now, this core does not do anything special on reset to the memory backing the instruction and data caches. After asserting
ResetSignal()
, the caches remain intact.I'm using the reset signal to stop the processor, load a new program, and restart the processor with the new program. Since the caches are intact, this can lead to the core running a mix of stale and new code.
To avoid this, I think it makes sense for the caches to flush themselves on reset. I've chosen to do this by initializing the caches in the
"FLUSH"
state. This works with the designs I'm using and passes the test suite, but I'd like a second opinion on this solution. This fix also adds a few dozen cycles of delay between reset and the first instruction fetch, but I think that's unavoidable.I've also added a commit to get the formal tests running with Amaranth 0.5.7 and recent Yosys.