On 5/3/26 06:04, Michael Balzer via OvmsDev wrote:
please find attached the improved version of the UI:
The progress bar is a nice touch (even it's only counting down an estimate).
This needs to be tested in combination with a firmware including the latest commits to master.
Could the partition page parse the running firmware version and refuse to upgrade if it is not at least the required version?
Everything went well with my test except the browser reconnect never happened (I got the "The expected upgrade time has passed" alert). I was watching the serial console so I could see when activity died down and things were quiet for awhile before the progress bar hit 100%.
I didn't look at how you actually implement the "reconnect to browser" feature but I did a couple of searches and found results where firefox (what I was using) can fail to reconnect; that might be why it failed for me with this and the previous version:
On 5/1/26 15:27, Craig Leres wrote:
Eventually I logged into module via ssh and could see that it had completed successfully.
The instructions should probably tell the user to first try manually reconnecting to the web gui (and logging in) and checking the partition upgrade page and only unplug/replug the module if the browser can't reconnect?
Be aware that due to the build partition table now being updated, doing "make flash" on "master" is no longer sufficient to reset a module to the previous partitioning. To revert to the old partitioning including the latest changes, switch to the new test branch "partitioning-v3-30", and do the "make flash" from there.
Since "edge" now uses the new partition layout I updated my ovmsinstall.sh script (attached) to use the old v3-30 when the -o flag is given. By default you end up with the new v3-35 layout.
Craig