Skip to content

Comments

doc: add boards memory layout page#659

Open
lemrey wants to merge 1 commit intonrfconnect:mainfrom
lemrey:memory-layout
Open

doc: add boards memory layout page#659
lemrey wants to merge 1 commit intonrfconnect:mainfrom
lemrey:memory-layout

Conversation

@lemrey
Copy link
Contributor

@lemrey lemrey commented Feb 24, 2026

Add a section to show the memory layout for each board.
The images are automatically generated by a script, which is also committed.

@lemrey lemrey requested review from a team as code owners February 24, 2026 10:10
@github-actions github-actions bot added changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. doc-required PR must not be merged without tech writer approval. labels Feb 24, 2026
@github-actions
Copy link

You can find the documentation preview for this PR here.

@lemrey lemrey force-pushed the memory-layout branch 2 times, most recently from 1ecb0fd to 91d85e6 Compare February 24, 2026 10:31
@@ -0,0 +1,501 @@
#!/usr/bin/env python3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if there is a good way we can run the script to autogenerate the images etc. on doc build instead of running the script manually and adding the files to the repository(?).

Comment on lines 261 to 275
COLORS = {
"boot": "#00a9ce",
"storage": "#e97c25",
"peer_manager": "#d4883a",
"storage0": "#f0a050",
"slot0": "#00b89f",
"slot1": "#0090b0",
"softdevice": "#af7fe4",
"metadata": "#7929d2",
"(unused)": "#d0d5dd",
"KMU reserved": "#8b96a8",
"softdevice_static_ram": "#af7fe4",
"softdevice_dynamic_ram": "#cb99f6",
"app_ram": "#00b89f",
"retained_mem": "#7929d2",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The output does not look like it is Nordic brand.

@lemrey lemrey force-pushed the memory-layout branch 2 times, most recently from 4c7c239 to 0a55281 Compare February 24, 2026 12:16
"storage0": "Storage0 (ZMS)",
"slot0": "Application (slot0)",
"slot1": "FW Loader (slot1)",
"softdevice": "SoftDevice",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to use the short elsewhere.

Suggested change
"softdevice": "SoftDevice",
"softdevice": "SoftDevice (SD)",

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to use the full name in the images

.. rubric:: S145 + MCUboot

.. image:: images/bm_nrf54l15dk_nrf54l05_cpuapp_s145_softdevice_mcuboot.svg
:alt: nRF54L05 S145 + MCUboot memory layout
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would probably be good with a link here to the https://docs.nordicsemi.com/bundle/nrf-bm-latest/page/nrf-bm/app_dev/dfu/memory_partitioning.html documentation to explain the differences for SoftDevice etc.

@lemrey lemrey force-pushed the memory-layout branch 6 times, most recently from bbb564c to b6f10dc Compare February 24, 2026 14:37
@github-actions github-actions bot removed the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 24, 2026
@lemrey
Copy link
Contributor Author

lemrey commented Feb 25, 2026

@nrfconnect/ncs-bm-doc please have a look :)

- ``app_ram``
- RAM available for the application.
* - Retained Mem
- ``RetainedMem``
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not used, did you mean Retained RAM (MCUboot)?

Comment on lines +165 to +166
bm_nrf54lv10dk
==============
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to split on the DK, can we put LV10 together with the rest?

Copy link
Contributor

@eivindj-nordic eivindj-nordic Feb 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively have two levels of tabs, one with the DK and one with the SoC where needed. Though in general I think the user is mostly interested on the SoC.

image

Or even three, I think that makes it a lot easier to compare as you can easily switch between different SoCs and see the images changing.

image

Add a section to show the memory layout for each board.
The images are automatically generated by a script,
which is also committed and can be run with

python doc/_scripts/gen_memory_layouts.py

Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-required PR must not be merged without tech writer approval.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants