nRF54L15: Add initial TF-M support #1571
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
Vge0rge
force-pushed
the
nrf54l_initial_tfm
branch
from
cda3940 to
34b1a20
Compare
Vge0rge
force-pushed
the
nrf54l_initial_tfm
branch
2 times, most recently
from
0152b06 to
78b5bd6
Compare
Vge0rge
changed the title
NordicBuilder
requested review from
anangl,
hubertmis,
jukkar,
nordic-krch and
rlubos
Vge0rge
force-pushed
the
nrf54l_initial_tfm
branch
from
8b776d6 to
0057071
Compare
jciupis
approved these changes
Mar 18, 2024
|
if we use a fixup for the noup it will be easier to identify that it should be squashed later. See https://nordicsemi.atlassian.net/wiki/spaces/NCS/pages/108201225/Pull+Requests for how to format the commit message of the fixup. |
SebastianBoe
approved these changes
Mar 18, 2024
Vge0rge
force-pushed
the
nrf54l_initial_tfm
branch
5 times, most recently
from
a6558aa to
2b25897
Compare
The option SOC_NRF54L_GLITCHDET_WORKAROUND is not needed anymore becuase the glitch detector is already disabled in the Nordic MDK in the hal_nordic repo. File path in hal_nordic: nrfx/mdk/system_nrf54l.c Signed-off-by: Georgios Vasilakis <[email protected]> (cherry picked from commit 0bc547ea3bb3f2d254c0ecb0e06583f04be71366)
The soc_secure_* function are used by the non-secure application to access hardware resources which are mapped as secure. Using these functions for hardware resources mapped as non-secure is missleading. We have some soc_secure_* functions which read FICR values. In nRF91 and nRF53 platforms this made sense since FICR has hardware fixed mapping as secure. For nRF54 though the FICR has hardware fixed mapping as non-secure. This change refactors the soc_secure.h to exclude the functions which read FICR values from being included when FICR is mapped as non-secure. Also updates the hwinfo and ieee802154 drivers to adjust to this change. Upstream PR: zephyrproject-rtos/zephyr#69968 Signed-off-by: Georgios Vasilakis <[email protected]>
Add SOC_NRF54LX_DISABLE_FICR_TRIMCNF and SOC_NRF54LX_SKIP_GLITCHDETECTOR_DISABLE config options. Signed-off-by: Magdalena Pastula <[email protected]> (cherry picked from commit b0b4bc0)
Add support for propagating SOC_NRF54LX_DISABLE_FICR_TRIMCNF and SOC_NRF54LX_SKIP_GLITCHDETECTOR_DISABLE values to nrfx. Signed-off-by: Magdalena Pastula <[email protected]> (cherry picked from commit 92f1b3f)
fixup! [nrf noup] modules: mbedtls: add PSA configurations PSA_HAS_KEY_AGREEMENT needs to be selected if at least one of the two key agreement algorithms ECDH/FFDH is enabled. Ref: NCSDK-26277 Signed-off-by: Georgios Vasilakis <[email protected]>
Vge0rge
force-pushed
the
nrf54l_initial_tfm
branch
from
2b25897 to
b763682
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.