Skip to content
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.

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

[nrf noup] samples: code_relocation_nocopy: Support NS variant of nRF5340 DK #2545

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

anangl
Copy link
Contributor

@anangl anangl commented Feb 21, 2025

Add Kconfig fragment that allows using the sample with the non-secure variant of the board.
Applied as a noup because upstream the build fails on signing the image.

…5340 DK

Add Kconfig fragment that allows using the sample with the non-secure
variant of the board.
Applied as a noup because upstream the build fails on signing the image.

Signed-off-by: Andrzej Głąbek <[email protected]>
@anangl anangl force-pushed the code_relocation_nrf5340dk_ns branch from 7c01861 to ca97fe7 Compare February 21, 2025 12:27
Copy link
Contributor

@SeppoTakalo SeppoTakalo left a comment

Choose a reason for hiding this comment

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

I would approve as [noup] because of following reasons:

  • Split XIP build support only exist in NCS as a sysbuild scripts.
  • Split XIP build requires PartitionManager which exist only in NCS.
  • Our chip requires our fork of TF-M and all required pieces are in NCS.

Therefore TF-M build with all the required Partition Manager and Sysbuild support only exist in nRF Connect SDK. So this would not work on upstream.

@nordicjm
Copy link
Contributor

I don't know what the intention is here but this does absolutely nothing for QSPI split image support, as can be seen by trying to build https://github.com/nrfconnect/sdk-nrf/tree/main/samples/nrf5340/extxip_smp_svr for an ns board target:

CMake Error at /tmp/bb/nrf/cmake/sysbuild/image_signing_split.cmake:147 (message):
  TFM is not currently supported with QSPI XIP

All this does is allow a single sample to build which does not support updates in any way

@SeppoTakalo
Copy link
Contributor

I see.
So the problem is not about having TF-M, but a build scripts that do not handle the image signing.

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.

3 participants