[sw-sysemu] fix wrong SRAM_BASE in pma_bootrom_cacheop test - #118
Merged
glguida merged 1 commit intoApr 1, 2026
Merged
Conversation
Member
|
LGTM. @vidas? |
vidas
approved these changes
Mar 31, 2026
Member
Author
|
@vidas Added it, thanks for the catch! |
Member
|
Please squash the commits in a single one. |
AFOliveira
force-pushed
the
fix/pma-bootrom-cacheop-sram
branch
from
April 1, 2026 08:26
10a4e0c to
0f6d280
Compare
Member
Author
|
Done |
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
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.
0x0200E000 is outside the SRAM region (0x0200C000-0x0200CFFF), causing cache operations to hit an unmapped region and report a spurious PMA error.
I caught this while using #80 flow.