You are reading a single comment by @tve and its replies.
Click here to read the full conversation.
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.
@tve
Mhh, you seem to be taking a very stm32-centric view. On the esp8266 the flash_start and flash_length values don't make a ton of sense because there are multiple areas with settings and such. Flash_start+Flash_length=Flash_end, basically, so you can't put anything beyond that. So the way this is coded, a user has to go and look up the memory map and decide into which gap to put the 4KB eeprom page.
If you would allow process.memory() to have an "eeprom" field, or "scratch_flash" field that could be populated by the device dependent code then it could be coded to just work. As it is, it only "just works" on the pico and for the esp8266 the user has to (a) discover that there's a problem and (b) dig out the answer, and (c) modify the code. That doesn't make for portable code (consider what happens when someone publishes a module that uses the flasheeprom).