Skip to content

Commit fd5030e

Browse files
committed
[nrf noup] soc: nrf54l: Non-XIP KMU reserved memory fix
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]>
1 parent 107f9f0 commit fd5030e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

soc/nordic/nrf54l/CMakeLists.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ zephyr_include_directories(.)
1010
# We need a buffer in memory in a static location which can be used by
1111
# the KMU peripheral. The KMU has a static destination address, we chose
1212
# this address to be 0x20000000, which is the first address in the SRAM.
13-
if(NOT CONFIG_BUILD_WITH_TFM AND CONFIG_PSA_NEED_CRACEN_KMU_DRIVER)
13+
if(NOT CONFIG_BUILD_WITH_TFM AND CONFIG_PSA_NEED_CRACEN_KMU_DRIVER AND CONFIG_XIP)
1414
# Exclamation mark is printable character with the lowest number in ASCII table.
1515
# We are sure that this file will be included first.
1616
zephyr_linker_sources(RAM_SECTIONS SORT_KEY ! kmu_push_area_section.ld)

0 commit comments

Comments
 (0)