ESP8266 Community Forum

- Mon Mar 14, 2016 11:08 am #43099 Using the unofficial Windows Development environment, all has been well for months - aside from running a little close to the wall as far as RAM is concerned (the type that functions are stored in)

3 .text 00007eae 40100000 40100000 00002fc0 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE

But that's fine thanks to using the ICACHE_FLASH_ATTR compiler directive just about everywhere. I've loads of other types of RAM left but this one has been getting near the limit...

Until... the latest SDK from Espressif - which refuses to compile my program as I'm now out of TEXT ram. I can only assume they've added some stuff.... is there any way to get some of this back? For example - am I compiling AT code which I'm not using? Or is the compiler already only pulling in what it needs? Is there any way around this - I don't want to have to start going backwards...

Pete.

Peter Scargill - http://tech.scargill.net

- Mon Mar 14, 2016 6:07 pm #43149 I haven't used the new SDK yet but it would be interesting to compile an application with the new SDK and the previous SDK and compare the .lss files. By doing so you should be able to see what is contributing to the increase in size of the various sections.

Don Kinzer
ZBasic Microcontrollers
http://www.zbasic.net

- Mon Jul 18, 2016 2:18 am #50951 The "now" newest SDK's have freed up a lot of IRAM space. Maybe it works again. But I've found that if you mark "everything" as "IRAM", there is really enough IRAM space left for "everything".