[nrf noup] soc: nrf54l: Non XIP KMU reserved memory fix #2512
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
tomi-font
approved these changes
Feb 20, 2025
The linker script inclusion which places the KMU reserved buffer on the top of RAM doesn't work for non-XIP builds. The Zephyr linker script will firstly load the code for an non-XIP build in RAM and then include this KMU related linker script which results in an unpredictable placement of the KMU reserved area and a failed build. In order to support non-XIP builds the linker file is not included and the a DTS reserved-memory entry should be used. To limit the scope, the DTS reserved memory region is currently only supported for non-XIP builds. This is a noup since the KMU is not supported upstream. Signed-off-by: Georgios Vasilakis <[email protected]>
Vge0rge
force-pushed
the
add_kmu_region_for_non_xip
branch
from
c564adf to
fd5030e
Compare
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.
The linker script inclusion which places the KMU reserved buffer on the top of RAM doesn't work for non XIP builds. The Zephyr linker script will firstly load the code for an non XIP build in RAM and then include this KMU related linker script which results in an unpredictable placement of the KMU reserved area and a failed build.
In order to support non XIP builds the linker file is not included and the a DTS reserved-memory entry should be used.
To limit the scope, the DTS reserved memory region is currently only supported for non XIP builds.
This is a noup since the KMU is not supported upstream.