nrf_802154: nRF54L15 use non-secure SL library for builds with CONFIG_TRUSTED_EXECUTION_NONSECURE
#1431
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For builds with Kconfig option
CONFIG_TRUSTED_EXECUTION_NONSECURE
the non-secure binaries of nRF 802.15.4 SL library must be used.To allow this with current
nrfxlib_calculate_lib_path
cmake function, the function is given additional parameter NS_PROVIDED.This approach does not force other users to provide non-secure versions of their libraries (for example if their libs are secure-agnostic).
The nrfxlib_calculate_lib_path adds
_ns
suffix to the returned library path when the SoC is nRF54L15 andCONFIG_TRUSTED_EXECUTION_NONSECURE
is enabled.Other SoCs are out of scope now.
The nRF 802.15.4 SL library for nRF54L non-secure is deployed already with the PR:
#1430