@roccomuso, I'm not saying it is not possible, but as @Gordon mentions: it get's tight with current implementations.
@Kolban, inpressive the list and details about RAM figures.
@Gordon, last time you mentioned executing code from EEPROM, I understood it as 'exectute directly from ROM'. Is that not an option at all? I know that some information about the code needs to be in the RAM, such as symbolic entry points and their (EEPROM) address, vars, etc. *'jump' addresses for conditional and loop consturcts, etc... What else more would have to go into the RAM? Is it too far fetched to make that step from source-interpretation of source in RAM to source-interpretation to source in EPROM? May be the overhead eats up (almost all) the yield...?
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.
@roccomuso, I'm not saying it is not possible, but as @Gordon mentions: it get's tight with current implementations.
@Kolban, inpressive the list and details about RAM figures.
@Gordon, last time you mentioned executing code from EEPROM, I understood it as 'exectute directly from ROM'. Is that not an option at all? I know that some information about the code needs to be in the RAM, such as symbolic entry points and their (EEPROM) address, vars, etc. *'jump' addresses for conditional and loop consturcts, etc... What else more would have to go into the RAM? Is it too far fetched to make that step from source-interpretation of source in RAM to source-interpretation to source in EPROM? May be the overhead eats up (almost all) the yield...?