arm: rename default RAM region from 'SRAM' to 'RAM'
It's useful for RAMABLE_REGION to have a uniform name when CODE_DATA_RELOCATION is supported, because otherwise the build system needs to be aware of how the region name differs between architectures. Since architectures tend to prefer one of 'SRAM' or 'RAM' for that region, prefer to use 'RAM' as the more general term. Signed-off-by: Peter Marheine <pmarheine@chromium.org>
This commit is contained in:
parent
c82d66f319
commit
5eb75b81f7
8 changed files with 22 additions and 37 deletions
|
@ -8,22 +8,16 @@ project(code_relocation)
|
|||
FILE(GLOB app_sources src/*.c)
|
||||
target_sources(app PRIVATE ${app_sources})
|
||||
|
||||
if (CONFIG_ARM)
|
||||
set(RAM_SECTION SRAM)
|
||||
else()
|
||||
set(RAM_SECTION RAM)
|
||||
endif()
|
||||
|
||||
# Code relocation feature
|
||||
zephyr_code_relocate(src/test_file1.c SRAM2)
|
||||
|
||||
zephyr_code_relocate(src/test_file2.c ${RAM_SECTION})
|
||||
zephyr_code_relocate(src/test_file2.c RAM)
|
||||
|
||||
zephyr_code_relocate(src/test_file3.c SRAM2_TEXT)
|
||||
zephyr_code_relocate(src/test_file3.c ${RAM_SECTION}_DATA)
|
||||
zephyr_code_relocate(src/test_file3.c RAM_DATA)
|
||||
zephyr_code_relocate(src/test_file3.c SRAM2_BSS)
|
||||
|
||||
zephyr_code_relocate(../../../kernel/sem.c ${RAM_SECTION})
|
||||
zephyr_code_relocate(../../../kernel/sem.c RAM)
|
||||
|
||||
if (CONFIG_RELOCATE_TO_ITCM)
|
||||
zephyr_code_relocate(../../../lib/libc/minimal/source/string/string.c ITCM_TEXT)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue