feat(non-unified-mem): introduce support for non unified memory platforms #218
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
danielRep
requested review from
AfonsoSantos96,
DavidMCerdeira,
josecm,
ninolomata and
sandro2pinto
as code owners
danielRep
force-pushed
the
feat/non-unified-mem
branch
2 times, most recently
from
3b7f781 to
d467724
Compare
miguelafsilva5
force-pushed
the
ref/vmpu
branch
5 times, most recently
from
063a1b2 to
2f167aa
Compare
danielRep
force-pushed
the
feat/non-unified-mem
branch
2 times, most recently
from
dbed9aa to
3b8f45e
Compare
danielRep
force-pushed
the
feat/non-unified-mem
branch
from
3b8f45e to
d3eccd8
Compare
|
In the PR description, alongside the other modifications, I also suggest adding that it is now possible to setup memory permissions to reflect platform's memory restrictions (e.g., flash is read-only) |
danielRep
force-pushed
the
feat/non-unified-mem
branch
from
d3eccd8 to
22f719f
Compare
josecm
requested changes
Aug 19, 2025
miguelafsilva5
force-pushed
the
ref/vmpu
branch
from
658439b to
44db8da
Compare
danielRep
force-pushed
the
feat/non-unified-mem
branch
from
374e494 to
9ad59e5
Compare
4 tasks
danielRep
force-pushed
the
feat/non-unified-mem
branch
from
9ad59e5 to
474545c
Compare
danielRep
force-pushed
the
feat/non-unified-mem
branch
6 times, most recently
from
3d1e91a to
53e6ea9
Compare
josecm
requested changes
Sep 9, 2025
|
@danielRep please rebase on main and clean up commit history before proceeding |
Signed-off-by: Daniel Oliveira <[email protected]>
Signed-off-by: Daniel Oliveira <[email protected]>
Signed-off-by: Daniel Oliveira <[email protected]>
Signed-off-by: Daniel Oliveira <[email protected]>
These variables must be initialized in the boot.S of each arch. Both are global variables, therefore we removed the passing as argument of the load address throughout the internal APIs of Bao. Signed-off-by: Daniel Oliveira <[email protected]>
Signed-off-by: Daniel Oliveira <[email protected]>
danielRep
force-pushed
the
feat/non-unified-mem
branch
from
04f6748 to
1a50d5c
Compare
josecm
approved these changes
Sep 10, 2025
|
@DavidMCerdeira @miguelafsilva5 please give another pass when possible |
@josecm I've given it another pass and rebased it to TC4. Everything is working and seems OK |
miguelafsilva5
approved these changes
Sep 10, 2025
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.
PR Description
This PR builds on top of PR #216 and adds support for platforms with non-unified memory architectures—i.e., platforms where code (e.g., flash) and data (e.g., SRAM) reside in separate memory regions. Previously, Bao only supported platforms with unified DRAM-based memory.
To support this architectural change, the following modifications were made:
load_addrargument from function calls withinmem.c, as it is now a constant global variable. Passing it explicitly no longer made sense in the context of non-unified memory platforms.Refactored LinkerScript
The following table details the difference between the memory layout of unified vs non-unified platforms. Unified platforms keep the same layout as expected while non-unified platforms split addresses between VMA and LMA addresses to cope with the typical separation of code and data memory architecture.
Unified Platforms
fvp-r-aarch32
qemu-aarch64-virt
Non-Unified Platform
tricore tc49