SWUpdate successful boot check and rollback #75
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zehnm
force-pushed
the
swupdate-bootflags
branch
from
4b95de9 to
517c099
Compare
martonborzak
approved these changes
Mar 20, 2021
Use U-Boot boot limit functionality to detect a system update and failed startups.
This uses the following U-Boot env variables:
- `bootlimit`: defines the maximum number of reboot cycles allowed. Default value: 3
- `bootcount`: will be incremented at each reboot IF `upgrade_available` is set to 1
- `upgrade_available`: indicates that a system update has been applied.
- SWUpdate sets this value to 1 after a new system update has been written.
- Verified after boot with a systemd timer:
If after a system update the remote app is still running after 3 minutes after boot up,
the update is considered successful and `upgrade_available` and `bootcount` U-Boot env vars are cleared.
- `rootfspart`: holds the current active root filesystem partition number to boot from.
- `altbootcmd`: alternative U-Boot boot command if bootlimit is exceeded.
- Switches the `rootfspart` to the old partition number to restore the old system.
zehnm
force-pushed
the
swupdate-bootflags
branch
from
517c099 to
825aa97
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
U-Boot boot count limit support
Use U-Boot boot count limit functionality to detect a system update and failed startups.
This uses the following U-Boot env variables:
bootlimit: defines the maximum number of reboot cycles allowed. Default value: 3bootcount: will be incremented at each reboot IFupgrade_availableis set to 1upgrade_available: indicates that a system update has been applied.If after a system update the remote app is still running after 3 minutes after boot up, the update is considered successful and
upgrade_availableandbootcountU-Boot env vars are cleared.rootfspart: holds the current active root filesystem partition number to boot from.altbootcmd: alternative U-Boot boot command if bootlimit is exceeded.rootfspartto the old partition number to restore the old system.This closes #69
Remote app auto restart
Changed the systemd service file:
This closes #23
SWUpdate version update
Open issues
This PR is part of #29