Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Firmware file not found error #1130

Open
selankon opened this issue Sep 17, 2024 · 2 comments
Open

Firmware file not found error #1130

selankon opened this issue Sep 17, 2024 · 2 comments
Assignees
@javierbrk
Labels
altermundi Development is being done for Altermundi
Milestone
mesh-wide

Comments

@selankon
Copy link
Collaborator

If you don't confirm, the firmware is supposed to be rollback.

However after reboot the error shown is firmware_file_not_found. Is this expected?

image

Either, abort won't work because shared state is to slow
@selankon selankon added this to the mesh-wide milestone Sep 17, 2024
@selankon
Copy link
Collaborator Author

Abort works when shared state has enough info

@javierbrk
Copy link
Collaborator

yes.
when the scheduled is performed, the status is stored in the old partition and in the new partition.
When you reboot into the old partition after not confirming the firmware verifies the status and finds it inconsistent since there is no fimware anymore. Something went wrong ... so i think its OK to manually abort the previous upgrade.

@ilario ilario added the altermundi Development is being done for Altermundi label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@javierbrk javierbrk

Labels
altermundi Development is being done for Altermundi
Projects
None yet
Milestone
mesh-wide
Development

No branches or pull requests
3 participants
@ilario @javierbrk @selankon