-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
samples: openthread: add TF-M support for nrf54l15 #17981
Conversation
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. |
d5ee57a
to
4951009
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: f053df65be2a442bb8c0c14afd683b2de7f8445b more detailssdk-nrf:
nrfxlib:
Github labels
List of changed files detected by CI (108)
Outputs:ToolchainVersion: 3dd8985b56 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
4951009
to
4d32157
Compare
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
CONFIG_NRFX_UARTE0=n | ||
|
||
# Workaround required as Zephyr L2 implies usage of NVS backend for settings. | ||
# It should be removed once the proper fix will be applied in Zephyr. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this ongoing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
switching to ZMS has been added to nrf54l15 target two days ago so I assumed that it is 3ad9997
@kkasperczyk-no this should be selected for TF-M as well, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, i know ZMS should be used always for 54L (both ns an s) but do we need to enable it in all samples? I was more askig about the comment about Zephyr L2 fix.
4d32157
to
4d53b9e
Compare
CONFIG_NRFX_UARTE0=n | ||
|
||
# Workaround required as Zephyr L2 implies usage of NVS backend for settings. | ||
# It should be removed once the proper fix will be applied in Zephyr. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, i know ZMS should be used always for 54L (both ns an s) but do we need to enable it in all samples? I was more askig about the comment about Zephyr L2 fix.
4d53b9e
to
ed2156b
Compare
ed2156b
to
1f5dca2
Compare
2e6d4dc
to
7367d11
Compare
add TF-M support for nrf54l15 and pull nrfxlib with changes allowing building TFM from libraries without warnings Signed-off-by: Maciej Baczmanski <[email protected]>
7367d11
to
f053df6
Compare
add TF-M support for nrf54l15 and pull nrfxlib with changes allowing building TFM from libraries without warnings
test_thread: PR-1229