It's a little unclear at what point in the project you are from this. First off, I assume you mean updating the application code (the javascript), not the firmware (the Espruino interpreter itself)
So you've got your code to read off the serial, and you've got it save()'ed, so it loads on power-on?
And now you want it to save the state in response to code sent down the serial? Depending on the rest of your code, you might be able to just send a save();, which will save the code (replacing what was previously saved) and rebooting the Espruino.
Now - if you're just sending code over serial, is there a reason you're not using the console instead? You can move the console onto a UART by doing something like Serial3.setConsole()...
What's your overall goal/plan with this project?
What is it going to be doing, and over what medium will it be getting the updates?
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.
It's a little unclear at what point in the project you are from this. First off, I assume you mean updating the application code (the javascript), not the firmware (the Espruino interpreter itself)
So you've got your code to read off the serial, and you've got it save()'ed, so it loads on power-on?
And now you want it to save the state in response to code sent down the serial? Depending on the rest of your code, you might be able to just send a save();, which will save the code (replacing what was previously saved) and rebooting the Espruino.
Now - if you're just sending code over serial, is there a reason you're not using the console instead? You can move the console onto a UART by doing something like Serial3.setConsole()...
What's your overall goal/plan with this project?
What is it going to be doing, and over what medium will it be getting the updates?