Memory map updated for v1.0 #345
Merged
Conversation
This file contains 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
marnovandermaas
force-pushed
the
memory_map_changes
branch
from
5fe3e47 to
f342342
Compare
elliotb-lowrisc
approved these changes
Nov 12, 2024
SRAM is now 128 KiB. Only 2 KiB of revocation tags are needed to cover this. Untagged RAM are not accessible. HyperRAM controller has no memory mapped configuration.
marnovandermaas
force-pushed
the
memory_map_changes
branch
from
f342342 to
7bfe88d
Compare
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.
7 MiB of HyperRAM is not accessible yet, so is marked as reserved instead. Also there is now only 128 KiB of SRAM. HyperRAM control and debug module are not available either so these are just marked as reserved for now.