michaelh/zephyr
1
0
Fork 0
Code Releases Activity

arc: CONFIG_XIP can work with ICCM

Browse source 
I've tested that CONFIG_XIP does work with Harvard.
User's can build CONFIG_XIP=y, and then have their bootable image
be placed in SPI-FLASH. A bootloader will load up ICCM contents.
Zephyr will then copy remaining data from ICCM to DCCM.
This takes a bit of ICCM memory to do it, but it will work.

Change-Id: Ic1cd201d19aab9083d63334527d9d68f4edc6075
Signed-off-by: Chuck Jordan <cjordan@synopsys.com>
This commit is contained in:
Chuck Jordan 2016-05-18 17:43:18 -07:00 • committed by Anas Nashif
commit 7b42324e77
1 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
include/arch/arc/v2/linker_harvard.ld
View file

@ -35,15 +35,13 @@
/* physical address of RAM */ /* physical address of RAM */
#ifdef CONFIG_XIP #ifdef CONFIG_XIP
#error "CONFIG_XIP is not supported at this time." #define ROMABLE_REGION ICCM
#define RAMABLE_REGION DCCM
#else #else
#define ROMABLE_REGION ICCM #define ROMABLE_REGION ICCM
#define RAMABLE_REGION DCCM #define RAMABLE_REGION DCCM
#endif #endif
/* TODO: For Harvard, probably want data in ICCM but have startup code
* that copies it to DCCM.
*/
#if defined(CONFIG_XIP) #if defined(CONFIG_XIP)
#define _DATA_IN_ROM __data_rom_start #define _DATA_IN_ROM __data_rom_start
#else #else