I think whichever state file was last saved or loaded before an update gets reloaded automatically after an update.
The STATE.f42 file that has been saved is automatically loaded after an update. State files saved with other names are NOT loaded.
That doesn't seem to agree with the source code. From what I can tell it does the following when you save the state:
Saves the state file name via a DMCP syscall.
Saves the state to the state file.
Forces a system reset via DMCP syscall.
Then on reloading DM42PGM:
Gets the current state file name via a DMCP syscall.
Loads the state file (if it exists).
(Some details skipped, obviously.)
I've never delved into the source code, but I can see how you would be correct. I have several state files saved with different names, but always save one with the default STATE.f42 name just prior to a firmware update and this is the one that is automatically loaded after the update is complete. It never prompts me to choose from a list of names, so I assumed incorrectly that it would not load an alternatively named state file. Thanks for the clarification.
Yes, that is what I meant too.
I started to write a reply this morning, but couldn't doublecheck, sp cancelled.
But if I recall correctly, it'll load last active statefile. My files are called "one", "two", "three", etc and none of them "STATE". So always last loaded when updated. I checked, and my current statefile is "four". (Which means I've had 4 updates since statefiles emerged)
Esben
DM42 SN: 00245, WP43 Pilot SN:00002, DM32 SN: 00045 (Listed in obtained order).