-
Notifications
You must be signed in to change notification settings - Fork 1.4k
manifest: Bring Zephyr and TF-M with fixed 54L10 RRAM size #24234
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
Conversation
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:trusted-firmware-m: PR head: 3533b12eae4b681da8357ba0dc030da5a9dd6ff6 more detailstrusted-firmware-m:
sdk-nrf:
zephyr:
Github labels
List of changed files detected by CI (7)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR here. |
d56a378
to
524aaae
Compare
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.
LGTM pending correct sha
ping @nrfconnect/ncs-code-owners |
This fixes an issue where the non volatile storage size was wrong for the nRF54L10 non secure target. Signed-off-by: Georgios Vasilakis <[email protected]>
524aaae
to
ce0f875
Compare
This fixes an issue where the non volatile
storage size was wrong for the nRF54L10
non secure target.