Skip to content

clarified why .data is listed as both ROM and RAM in the FAQ #47

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 1 commit into from
Oct 28, 2025
Merged

clarified why .data is listed as both ROM and RAM in the FAQ #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,8 @@ Total 555960
Of the standard sections, `.vector_table`, `.text`, `.rodata` and `.data` 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
the target device memory. (`.data` is initially placed in
Flash / ROM, but copied to RAM during startup to make it writable.) For the other sections you'll have to check your
dependencies' docs.

In this example the uploaded software will occupy `2008` bytes of Flash.
Expand Down
Loading