Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

usbarmory-rt: add Cargo feature to move .text and .rodata to DDR RAM #47

Merged
merged 1 commit into from
Mar 6, 2020

Conversation

japaric
Copy link
Collaborator

@japaric japaric commented Mar 6, 2020

the default is to place all linker sections: instructions (.text),
constants (.rodata), data (.bss / .data) and stack in On-Chip RAM (OCRAM,
128 KB)

when this Cargo feature is enabled the instructions and the constants will be
placed in DDR RAM, which has a capacity of 512 MB

the use of DDR RAM is currently capped at 32 MB to avoid .text and .rodata being
loaded into the staging area that u-boot uses to hold ELF files

closes #45
note that this doesn't address #31

the default is to place all linker sections: instructions (`.text`),
constants (`.rodata`), data (`.bss` / `.data`) and stack in On-Chip RAM (OCRAM,
128 KB)

when this Cargo feature is enabled the instructions and the constants will be
placed in DDR RAM, which has a capacity of 512 MB

the use of DDR RAM is currently capped at 32 MB to avoid .text and .rodata being
loaded into the staging area that u-boot uses to hold ELF files
@japaric japaric merged commit 55f5db0 into develop Mar 6, 2020
@japaric japaric deleted the use-dram branch April 2, 2020 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

put .text, and maybe .rodata, in DRAM
1 participant