zephyr_code_relocate() now supports the NOCOPY_DATA flag to inhibit data relocation #86628
Conversation
zephyrbot
requested review from
57300,
andyross,
ceolin,
cfriedt,
dcpleung,
jeremybettis,
nashif,
nordicjm,
npitre,
peter-mitsis,
TaiJuWu and
tejlmand
|
Hello @rhaberkorn, and thank you very much for your first pull request to the Zephyr project! |
This is activated by passing NOCOPY_DATA to zephyr_code_relocate(). It helps when building firmwares for coprocessors, where the image is loaded completely into SRAM from Linux-land using the remoteproc framework. Fixes: zephyrproject-rtos#86530 Signed-off-by: Robin Haberkorn <haberkorn@metratec.com>
rhaberkorn
force-pushed
the
relocate-nocopy-data
branch
from
c2c7015 to
1118aa3
Compare
| @@ -149,14 +149,18 @@ XIP area. | |||
|
|
|||
| This example will place the .text section of the ``xip_external_flash.c`` file | |||
| to the ``EXTFLASH`` memory region where it will be executed from (XIP). The | |||
| .data will be relocated as usual into SRAM. | |||
| .data will be relocated as usual into SRAM, since XIP flash does not | |||
There was a problem hiding this comment.
| .data will be relocated as usual into SRAM, since XIP flash does not | |
| .data will be relocated as usual into SRAM, since Flash in XIP mode does not |
| @@ -149,14 +149,18 @@ XIP area. | |||
|
|
|||
| This example will place the .text section of the ``xip_external_flash.c`` file | |||
| to the ``EXTFLASH`` memory region where it will be executed from (XIP). The | |||
| .data will be relocated as usual into SRAM. | |||
| .data will be relocated as usual into SRAM, since XIP flash does not | |||
| allow random write access and variables do not have to be persisted. | |||
There was a problem hiding this comment.
| allow random write access and variables do not have to be persisted. | |
| allow random write access and variables do not have to persist. |
This helps when building firmwares for coprocessors, where the image is loaded completely into SRAM in Linux-land using the remoteproc framework.
For a motivation of this change, see #86530.