Skip to content

Conversation

karstenkoenig
Copy link
Contributor

No description provided.

jonathannilsen and others added 15 commits July 1, 2025 10:49
Board is being removed and merged into the regular
nrf54h20dk/nrf54h20/cpuapp.

Signed-off-by: Jonathan Nilsen <[email protected]>
Since we don't yet have a complete replacement for nrf-regtool based
resource configuration, a temporary solution has been added to the
post_cmake hook that generates an old style UICR with nrf-regtool
and then migrates it to the PERIPHCONF format supported by IronSide.

Signed-off-by: Grzegorz Swiderski <[email protected]>
Signed-off-by: Jonathan Nilsen <[email protected]>
Pull in changes from zephyr that update nrf54h20 to be compatible
with IronSide SE.

Also adapt kconfig, samples and tests accordingly:

Add a sample at nrf54h20/empty_app_core sample for booting radiocore via
the IronSide CPUCONF service, integrated with the existing NCS sysbuild
machinery.

Add CONFIG_SOC_NRF54H20_CPURAD_ENABLE=y to all multicore tests and
samples that need to start the radio core. Also adapt devicetree
overlays according to the updated memory layout on nrf54h20.

Disable the following functionality on nrf54h20 due to it no longer
being supported:

* SUIT, which is replaced by MCUboot.
* SSF, which is replaced by IronSide calls.

Signed-off-by: Jonathan Nilsen <[email protected]>
Signed-off-by: Grzegorz Swiderski <[email protected]>
Signed-off-by: Karsten Koenig <[email protected]>
Update the memory map overlay to account for changes to the memory
layout coming in with the IronSide support for nrf54h20.
The radio settings partition has been left where it was since it
doesn't conflict with anything, though it probably should be updated
when the new nrf54h20 memory map is a bit more final.

Signed-off-by: Jonathan Nilsen <[email protected]>
Having it at POST_KERNEL level appears to cause issues on nrf54h20,
possibly due to the application core now starting the radio core in
soc_late_init_hook() which is after POST_KERNEL. Changing the level
to APPLICATION makes it so the radio core has been booted when this
hook executes.

Signed-off-by: Jonathan Nilsen <[email protected]>
Needed to be aligned with the updated nrf54h20 memory map.

Signed-off-by: Jonathan Nilsen <[email protected]>
With IronSide there is enough memory without updating the default memory
map.

Ref: NCSDK-NONE
Signed-off-by: Håkon Amundsen <[email protected]>
It needs alignment to work with MCUBoot on nRF54H.

Ref: NCSDK-NONE
Signed-off-by: Håkon Amundsen <[email protected]>
Align with changes to the nrf54h20 RAM memory layout where nodes like
cpuapp_ram0x_region, cpurad_ram0x_region, ram21_region,
cpuppr_ram3x_region etc. no longer exist, and cpuapp_data now starts
at the beginning of RAM0x (2f000000) and has a much larger size (760K).

Signed-off-by: Jonathan Nilsen <[email protected]>
It is not needed with IronSide as memory map is flat (for now).

Ref: NCSDK-NONE
Signed-off-by: Håkon Amundsen <[email protected]>
Remove unused partition and place fast pair partition in unused
memory.

Ref: NCSDK-NONE
Signed-off-by: Håkon Amundsen <[email protected]>
There is no support for this API on nRF54H.

Ref: NCSDK-NONE
Signed-off-by: Håkon Amundsen <[email protected]>
DPPIC130 ch.0 is temporarily reserved for Radiocore in the default
PERIPHCONF table. Select ch.1 instead, for both DPPIC130 and DPPIC133
symmetrically, as expected by `nrfx_gppi`.

Signed-off-by: Grzegorz Swiderski <[email protected]>
TDD support added in branch.

Signed-off-by: Karsten Koenig <[email protected]>
@karstenkoenig karstenkoenig added the CI-disable Disable CI for this PR label Jul 1, 2025
@github-actions github-actions bot added doc-required PR must not be merged without tech writer approval. manifest labels Jul 1, 2025
@github-actions
Copy link

github-actions bot commented Jul 1, 2025

Since quarantine was modified, please make sure you are following the process described in Quarantine Process.

@NordicBuilder
Copy link
Contributor

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
zephyr nrfconnect/sdk-zephyr@d7b901d nrfconnect/sdk-zephyr#2938 nrfconnect/sdk-zephyr#2938/files

DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@NordicBuilder
Copy link
Contributor

CI Information

To view the history of this post, clich the 'edited' button above
Build number: 1

Inputs:

Sources:

more details

Github labels

Enabled Name Description
ci-disabled Disable the ci execution
ci-all-test Run all of ci, no test spec filtering will be done
ci-force-downstream Force execution of downstream even if twister fails
ci-run-twister Force run twister
ci-run-zephyr-twister Force run zephyr twister
List of changed files detected by CI (0)

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

  • ◻️ Toolchain
  • ◻️ Build twister
  • ◻️ Integration tests

Note: This message is automatically posted and updated by the CI

@github-actions
Copy link

github-actions bot commented Jul 1, 2025

You can find the documentation preview for this PR here.

Preview links for modified nRF Connect SDK documents:

https://ncsdoc.z6.web.core.windows.net/PR-23073/nrf/drivers/mspi_sqspi.html

@NordicBuilder
Copy link
Contributor

This pull request has been marked as stale because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 7 days. Note, that you can always re-open a closed pull request at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI-disable Disable CI for this PR DNM doc-required PR must not be merged without tech writer approval. manifest manifest-zephyr Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants