Charge SOM: Add firmware chapter #39
Merged
Conversation
This file contains hidden or 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
As long as the mountpoint graphic is generic move it to the includes. Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
These screenshots are product specific, but are used from a generic include. While at this use PNG instead of JPG. Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
FaHaGit
approved these changes
Mar 13, 2025
Contributor
FaHaGit
left a comment
FaHaGit
left a comment
There was a problem hiding this comment.
Only a suggestions. Everthing else LGTM
docs/source/firmware.rst
Outdated
| Partitioning | ||
| ------------- | ||
|
|
||
| The internal eMMC storage of a chargebyte device is divided into several partitions. The main aim is to have two independent systems available, i.e. system A and system B. This allows to running firmware updates in background while performing normal charging operation, and then switching to the updated system with a fast restart of the device. This also allows to supporting a rollback mechanism in case of failures during firmware updates. In other words, during a firmware update, the active root file system switches from A to B or vice versa, leaving the other as rollback. |
Contributor
There was a problem hiding this comment.
Only a suggestion, think this sounds better. I know that this should also be changed in CCC.
Suggested change
| The internal eMMC storage of a chargebyte device is divided into several partitions. The main aim is to have two independent systems available, i.e. system A and system B. This allows to running firmware updates in background while performing normal charging operation, and then switching to the updated system with a fast restart of the device. This also allows to supporting a rollback mechanism in case of failures during firmware updates. In other words, during a firmware update, the active root file system switches from A to B or vice versa, leaving the other as rollback. | |
| The internal eMMC storage of a chargebyte device is divided into several partitions to support two independent systems: system A and system B. This setup enables firmware updates to run in the background while the device continues normal charging operations. Once the update is complete, the system can switch to the updated version with a reboot of the device. Additionally, this approach supports a rollback mechanism in case of update failures. In other words, during a firmware update, the active root file system switches from A to B (or vice versa), leaving the other partition available for rollback if needed. |
Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
barsnick
approved these changes
Mar 14, 2025
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.
After this pull request the RAUC jpg files in the CCC branch needs to be converted.