- Fri Jun 19, 2015 1:08 pm
#20952
Did you try compiling with -Os instead of -O3, by the way (optimise for size not speed).
- Fri Jun 19, 2015 1:14 pm
#20955
My code is compiled using .Os
Peter Scargill - http://tech.scargill.net
- Mon Jun 22, 2015 12:38 pm
#21245
Hmmm no.
The attribute means that it is stored in and run from flash using a 32k ram cache.
Without it it is run from 32k instruction ram.
The former is called irom, the later iram.
Interrupt called code and flash controlling code must me run from iram.
Cal
eriksl wrote:Yes agree. I ended up marking nearly all of my functions with the irom attribute (which is very misleadingly called "ICACHE_FLASH_ATTR" and imho suggests the function will be cached in RAM which ultimately is NOT the case, the absence attribute does that!)
Hmmm no.
The attribute means that it is stored in and run from flash using a 32k ram cache.
Without it it is run from 32k instruction ram.
The former is called irom, the later iram.
Interrupt called code and flash controlling code must me run from iram.
Cal
- Mon Jun 22, 2015 3:17 pm
#21271
Interesting you say that Cal... I'm running the backup and restore - using Espressif routines - using the prefix to hold the code in Flash.
See below..
void ICACHE_FLASH_ATTRCFG_Load()
{
iprintf(DEBUG,"\r\nConfig load ...\r\n");
system_param_load(CFG_LOCATION,0,(uint32 *)&sysCfg, sizeof(SYSCFG));
if(sysCfg.cfg_holder != CFG_HOLDER){
See below..
void ICACHE_FLASH_ATTRCFG_Load()
{
iprintf(DEBUG,"\r\nConfig load ...\r\n");
system_param_load(CFG_LOCATION,0,(uint32 *)&sysCfg, sizeof(SYSCFG));
if(sysCfg.cfg_holder != CFG_HOLDER){
Peter Scargill - http://tech.scargill.net
