Yes, it'd be good if you could come up with a bit of code that showed the problem. When the Pico freezed, did it work when you reset it, or did you have to re-flash it?
process.memory().flash_code_start save - can I start using the 16kb there ?
Yes and no... That is the area of memory used by save()... So you can use it, but if you do it'll destroy any program code you saved (which is probably not what you want).
Unfortunately due to the page arrangement on the Pico, pretty much everything apart from that final 128kb is used.
One solution would be to treat the whole 128kB as a 16kB page. If you needed to change something you could then read the whole 16kB into a Uint8Array in RAM, erase the flash, and then write the new data back.
Thanks. Upps. Yes i do not want to use flashmem where save() stores data itself. ;-).
After a reset() the pico worked as expected. Will try to give some code examples this evening.
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.
Yes, it'd be good if you could come up with a bit of code that showed the problem. When the Pico freezed, did it work when you reset it, or did you have to re-flash it?
Yes and no... That is the area of memory used by
save()
... So you can use it, but if you do it'll destroy any program code you saved (which is probably not what you want).Unfortunately due to the page arrangement on the Pico, pretty much everything apart from that final 128kb is used.
One solution would be to treat the whole 128kB as a 16kB page. If you needed to change something you could then read the whole 16kB into a
Uint8Array
in RAM, erase the flash, and then write the new data back.edit: I'll update the docs for
process.memory
too