-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EMS-ESP randomly reverts from firmware 3.6.4 back to firmware 3.5.1 #1645
Comments
I've just loaded 3.6.5 dev 15 to see if the problem persists. |
esp have 2 program partitions, on update the non-active is written and made active on successfull upload. IIn a intermediate version the ota_data was corrupted, resulting in boot from first partition on every reset. |
I've uploaded the update twice but the issue still persists. Do I really need to flash it with USB? (I thought I was on 3.6.4 already but it seems the issues stays for quite long).
|
yes, your flash is corrupted and the only way to fix it is a) export settings and any configurations b) flash with USB and c) export back the settings. You're one of the unfortunate people to have a bugged firmware. Sorry about that. But you should be up and running in minutes, provided you have a USB cable |
Looks fine after flashing with USB, thanks! |
I flashed with USB, but didn't resolve the issue. |
PROBLEM DESCRIPTION
I upgraded EMS-ESP on my Gateway S32 to 3.6.4 on November 28, 2023.
Since then, once in a while the Gateway seems to revert automatically back to 3.5.1. When I upgrade it again, the same happens after a while.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
TO REPRODUCE
No idea.
EXPECTED BEHAVIOUR
Not reverting back to an old firmware
SCREENSHOTS
Export from influx wrt the version number over time.
You can see on December 14th, January 14th and February 27th that the version goes back to 3.5.1 without me touching the device.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: