Skip to content

Fix which sections of binary belong to Flash/ROM vs RAM #39

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 26, 2025
Merged

Fix which sections of binary belong to Flash/ROM vs RAM #39

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8f9f13c
Fix which sections of binary belong to Flash/ROM vs RAM
iampi31415 Oct 22, 2025
fc6b97e
Rephrase: memory occupied by binary upon uploading it to device.
iampi31415 Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -242,12 +242,12 @@ section size addr
Total 555960
```

Of the standard sections, `.text`, `.rodata` and `.data` will occupy Flash /
Of the standard sections, `vector_table`, `.text`, `.rodata` will occupy Flash /
ROM; `.bss` and `.data` will occupy RAM; `.debug_*`, `.ARM.attributes` and
`.comments` can be ignored as they won't be loaded into the target device
memory. For the other sections you'll have to check your dependencies' docs.

In this examples the program will occupy `2008` bytes of Flash.
In this example the uploaded software will occupy `2008` bytes of Flash.

Note that most (all?) runtime crates, like `cortex-m-rt`, will check at link
time that the program fits in the target device memory. If it doesn't fit you'll
Expand Down
Loading