boards: st: stm32l5: Fix TF-M by restricting Libc malloc area #80977
Conversation
This file contains hidden or 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
zephyrbot
requested review from
FRASTM,
GeorgeCGV,
gautierg-st,
marwaiehm-st and
mathieuchopstm
Contributor
mathieuchopstm
left a comment
mathieuchopstm
left a comment
There was a problem hiding this comment.
LGTM functionally, but I would document in the files themselves why we're doing this (e.g., by linking to the issue).
erwango
changed the title
mathieuchopstm
previously approved these changes
Nov 6, 2024
Contributor
mathieuchopstm
left a comment
mathieuchopstm
left a comment
There was a problem hiding this comment.
Minor non-blockers:
By default, libc malloc allocated area is using all available RAM. For some yet unknown reason, this conflicts with TF-M resulting in a Hard Fault before jumping in the non secure application. For now, define a Libc malloc area defined to 2048 which is the default in some other typical applications (ARMv7 targets enabling USERSPACE). Fixes zephyrproject-rtos#77847 Signed-off-by: Erwan Gouriou <[email protected]>
mathieuchopstm
approved these changes
Nov 7, 2024
FRASTM
approved these changes
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
By default, libc malloc allocated area is using all available RAM. For some yet unknown reason, this conflicts with TF-M resulting in a Hard Fault before jumping in the non secure application.
Fow now, define a Libc malloc area defined to 2048 which is the default in some other typical applications (ARMv7 targets enabling USERSPACE).
Fixes #77847
Thanks to @norrathep for the hint.