Skip to content

Conversation

nordicjm
Copy link
Contributor

No description provided.

nordicjm added 4 commits May 28, 2025 07:48
Adds line gaps where they should be

Signed-off-by: Jamie McCrae <[email protected]>
RAM is not a fixed partition

Signed-off-by: Jamie McCrae <[email protected]>
Fixes wrongly using Kconfigs

Signed-off-by: Jamie McCrae <[email protected]>
Adds offsets when MCUboot is enabled

Signed-off-by: Jamie McCrae <[email protected]>
@nordicjm nordicjm requested a review from lemrey as a code owner May 28, 2025 12:11
Copy link
Contributor

@MirkoCovizzi MirkoCovizzi left a comment

Choose a reason for hiding this comment

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

Is using fixed-partition wrong for RAM when we separate the memory in partitions, e.g. for SoftDevice? I would like to understand the reason for the change.

@nordicjm
Copy link
Contributor Author

nordicjm commented May 28, 2025

Is using fixed-partition wrong for RAM when we separate the memory in partitions, e.g. for SoftDevice? I would like to understand the reason for the change.

yes, fixed-partition is for flash devices and goes into the flash map, it is wrong to use this binding with RAM. From the devicetree binding:

description: |
  Fixed partitions of a flash (or other non-volatile storage) memory.

Enables GPREGRET1 and assigns it as a retention device for use
with boot mode selection

Signed-off-by: Jamie McCrae <[email protected]>
Copy link
Contributor

Choose a reason for hiding this comment

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

Generally we would like to use the devicetree as little as possible. Though, I guess there is no good way to do this without?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

correct, this is used by MCUboot

Copy link
Contributor

Choose a reason for hiding this comment

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

I saw you fixed the start address of the gpregret registers in zephyr upstream. Do we need some patch until this has trickled down? Or do we expect it to be available downstream soon?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nordicjm
Copy link
Contributor Author

nordicjm commented Jun 9, 2025

@lemrey please review

@lemrey lemrey merged commit 0210b39 into nrfconnect:main Jun 10, 2025
6 checks passed
@nordicjm nordicjm deleted the fixnrf54l branch August 15, 2025 10:44
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.

5 participants