So this is for ESP8266? On ESP8266 512k builds you only have 12KB flash memory anyway, so it wouldn't gain you a lot! You can always just write a bunch of data somewhere else in flash and then just save some bootloader code like eval(E.memoryArea( addr, len ))): http://www.espruino.com/Reference#l_E_memoryArea
At the moment there isn't anything, but you could potentially write to the saved memory area yourself. It's only a two uint32s with 2 lengths in, then the data, then a 'magic byte' at the end:
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.
So this is for ESP8266? On ESP8266 512k builds you only have 12KB flash memory anyway, so it wouldn't gain you a lot! You can always just write a bunch of data somewhere else in flash and then just save some bootloader code like
eval(E.memoryArea( addr, len )))
: http://www.espruino.com/Reference#l_E_memoryAreaAt the moment there isn't anything, but you could potentially write to the saved memory area yourself. It's only a two uint32s with 2 lengths in, then the data, then a 'magic byte' at the end:
https://raw.githubusercontent.com/espruino/Espruino/09cdeafc4447b16c6f1758e0e2c7119a6e60543a/targets/esp32/docs/SaveAndLoad.md
Potentially
E.setBootCode
could be modified and the IDE could split data up and write it separately though.