Architecture: Semantic meaning of the definition of SAVE_ON_FLASH

You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.

•

Gordon

Yes - although ideally if you're targeting different boards with different setups then you'd have different board.py files?

With 4MB it can move up beyond the firmware partition, which will help with ensuring that upgrades don't wipe it out.

Presumably it could stay in the same place and everything would be fine? The storage of the data changes between versions - so realistically even if you kept the saved data between updates it probably wouldn't work with the new one.

Do you have an high-level overview of how this works?

Have you read the docs linked from the readme?

Internals and performance might help?

•

tve in reply to @Gordon

I've read these pages but there really isn't much there about how code is executed. Is the code stored as strings in JsVars or is that external to JsVars? One string or one per line or ...? Is each statement recursive-descent-parsed each time it is executed? What does the compiler produce?

About

Avatar for Gordon @Gordon started