You can store code on the EEPROM, and then load it off the EEPROM and execute it immediately - so you still need the memory free to hold the function while it's running, but not any other time. That's what this does.
And you can of course write large blobs of data to the EEPROM, and then read it later when you need it - in this case, you're swapping stuff in and out of RAM.
You can't have it access the EEPROM like it can main memory - you'll always have to swap stuff in and out.
But these can help with it, by storing some function code on the EEPROM (in my projects, code is where much of my memory goes). It's probably significantly slower, making it best for code not frequently used.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Take a look at the writeup here, which has been updated to new version of the AT24 modules:
http://www.espruino.com/run_code_from_eeprom
You can store code on the EEPROM, and then load it off the EEPROM and execute it immediately - so you still need the memory free to hold the function while it's running, but not any other time. That's what this does.
And you can of course write large blobs of data to the EEPROM, and then read it later when you need it - in this case, you're swapping stuff in and out of RAM.
You can't have it access the EEPROM like it can main memory - you'll always have to swap stuff in and out.
But these can help with it, by storing some function code on the EEPROM (in my projects, code is where much of my memory goes). It's probably significantly slower, making it best for code not frequently used.