You are reading a single comment by @DrAzzy 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.
@DrAzzy
"w/e" is common abbreviation for "whatever" - As in, if we can't split the f/w up, there'd have been at least one wasted 16k page. I guess two, since you're citing 80kb (I forgot how much was "overhead" for the stack/etc)
Why does the bootloader need to be replaced in order to support using a different page for saved code? Doesn't the firmware tell the bootloader where the data needs to go? Or does Pico_Extra_Ram take the 16k page used by the bootloader, rather than the 64k page + a 16k page?