-
Notifications
You must be signed in to change notification settings - Fork 4
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
Firmware update modifications #85
Comments
alvieboy
added a commit
that referenced
this issue
May 11, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 14, 2021
alvieboy
added a commit
that referenced
this issue
May 21, 2021
alvieboy
added a commit
that referenced
this issue
May 21, 2021
alvieboy
added a commit
that referenced
this issue
May 21, 2021
alvieboy
added a commit
that referenced
this issue
Jun 25, 2021
alvieboy
added a commit
that referenced
this issue
Jun 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Multiple enhancements shall be provided for firmware update:
a) Change the web firmware update so we can report status progress back. This should be done via web socket instead of POST, however POST shall still be supported for fallback.
b) Add a digest/checksum/crc to each individual file on the firmware file, so it can be checked.
c) In case we know that parts of the firmware are wrong (most notably /spiffs), use a fallback spiffs with a simple web interface for firmware upload.
d) Ensure the spiffs is the correct version by adding the build tag to a root file which can be checked on power-up.
e) The validity for spifss shall be stored in the nvram, invalidated when we start the process, and only validated after we check all digests/checksums/crc
The text was updated successfully, but these errors were encountered: