Skip to content

Conversation

tomchy
Copy link
Contributor

@tomchy tomchy commented Sep 12, 2025

If the area, dedicated for the interrupt stack is not available, allow to specify a memory region that will be used as the stack for the S2RAM resume logic.

Upstream PR #: 95914

manifest-pr-skip

ref.: NCSDK-35410

@tomchy tomchy force-pushed the bugfix/reset/NCSDK-35410_Dedicated_s2ram_stack_ncs branch from 3803d86 to 5a96446 Compare September 15, 2025 07:35
@maciejpietras maciejpietras requested review from ahasztag, de-nordic and michalek-no and removed request for ahasztag, de-nordic and michalek-no September 15, 2025 07:44
@tomchy tomchy force-pushed the bugfix/reset/NCSDK-35410_Dedicated_s2ram_stack_ncs branch from 5a96446 to e5d5510 Compare September 15, 2025 09:27
@nvlsianpu nvlsianpu added this to the 3.2.0-preview1 milestone Sep 15, 2025
@tomchy tomchy force-pushed the bugfix/reset/NCSDK-35410_Dedicated_s2ram_stack_ncs branch from 40c0962 to 7e71a69 Compare September 15, 2025 12:54
@tomchy tomchy force-pushed the bugfix/reset/NCSDK-35410_Dedicated_s2ram_stack_ncs branch 2 times, most recently from 2912b8e to 9b13ac0 Compare September 16, 2025 12:50

/* Trim this RAM block for making room on all run-time common S2RAM cpu context. */
&cpuapp_ram0 {
reg = <0x22000000 (DT_SIZE_K(32)-32)>;
Copy link
Contributor

@nordicjm nordicjm Sep 16, 2025

Choose a reason for hiding this comment

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

temp. block until input from @carlescufi - this places random burdens on VV commit 79bffff:

[nrf noup] boards: Align board DTS with upstream.

This alignment cannot be done through nrf fromlist commit, since it was
introduced in the tree-wide commit:
2d22884f52a01236d404fb2e6910d3683f680af6
Once tried to pull all changes to merge it cleanly, the chain ended up
in the doc/releases/migration-guide-4.3.rst file, which would bring
nearly all of the changes from the Zephyr 4.3 release, making a small PR
with just 4 white characters a Zephyr upmerge PR.
Feel free to drop this commit during the next Zephyr upmerge.

Copy link
Contributor

Choose a reason for hiding this comment

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

@tomchy can't you wait until the current upmerge is complete?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, we need it for the release that will be tomorrow.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Keep in mind that it is a separate commit that adds 4 spaces and should be more than trivial to handle during the upmerge (either way - noup commits create conflicts).

Copy link
Contributor

Choose a reason for hiding this comment

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

@nordicjm - I don't understand why you block this PR. It is bugfix. Its urgent, needed for preview tag tomorrow. There is ref. to internal ticket even you can check.

Copy link
Contributor

Choose a reason for hiding this comment

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

This places the blame of going through noup's on whomever is doing the upmerge, we have over 100 noup commits in sdk-zephyr, it is not nor should it be their responsibility to go through these 100+ commits, read their descriptions, apply possible action and then try to get them to apply. If things are needed then the required commits should be cherry-picked with them, if that takes 1 or 30 commits isn't VV's problem, it's on the person submitting to deal with and bring those in. An exception is being made for this due to urgency, future usage will be blocked and users will be asked to fromlist/fromtree cherry pick the required commits for a commit to be cleanly applied

This alignment cannot be done through nrf fromlist commit, since it was
introduced in the tree-wide commit:
2d22884
Once tried to pull all changes to merge it cleanly, the chain ended up
in the doc/releases/migration-guide-4.3.rst file, which would bring
nearly all of the changes from the Zephyr 4.3 release, making a small PR
with just 4 white characters a Zephyr upmerge PR.
Feel free to drop this commit during the next Zephyr upmerge.

Signed-off-by: Tomasz Chyrowicz <[email protected]>
If the area, dedicated for the interrupt stack is not available, allow
to specify a memory region that will be used as the stack for the S2RAM
resume logic.

Upstream PR #: 95914

Signed-off-by: Tomasz Chyrowicz <[email protected]>
Add the definition of pm_s2ram_stack memory region for nRF54H20.

Upstream PR #: 95914

Signed-off-by: Tomasz Chyrowicz <[email protected]>
@tomchy tomchy force-pushed the bugfix/reset/NCSDK-35410_Dedicated_s2ram_stack_ncs branch from 9b13ac0 to c812077 Compare September 17, 2025 07:06
@carlescufi carlescufi dismissed nordicjm’s stale review September 17, 2025 10:28

Discussed offline, this will be tracked for the next upmerge

Added support for hardening decision on resume from
S2RAM by MCUboot bootloader.
Application sets additional variable to MCUBOOT_S2RAM_RESUME_MAGIC
which allows the bootloader to doublecheck.

Signed-off-by: Andrzej Puzdrowski <[email protected]>
(cherry picked from commit 08e0cf4)
@tomchy tomchy force-pushed the bugfix/reset/NCSDK-35410_Dedicated_s2ram_stack_ncs branch from c812077 to 2dc2c8f Compare September 17, 2025 11:02
@carlescufi carlescufi merged commit d4bb1c6 into nrfconnect:main Sep 17, 2025
18 checks passed
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.

7 participants