Skip to content

Re-wording of ATOMIC_FS_UPDATE documenation #6693

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

Merged
merged 2 commits into from
Oct 31, 2019
Merged

Re-wording of ATOMIC_FS_UPDATE documenation #6693

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b2af38a
Re-wording of ATOMIC_FS_UPDATE documenation
pfeerick Oct 31, 2019
cbe5198
Merge branch 'master' into patch-1
earlephilhower Oct 31, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/ota_updates/readme.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -646,7 +646,7 @@ Update process - memory view
- the new sketch is now copied "over" the old one.
- the new sketch is started.

By default, filesystem updates are overriding the target flash directly. In order to use the same two step process set the `ATOMIC_FS_UPDATE` flag.
By default, OTA filesystem updates overwrite the target flash directly. This can lead to the file system being corrupted if there is a power outage during the update process. In order to use the same two step process that is used for OTA application firmware updates, set the `ATOMIC_FS_UPDATE` flag. Note that you will need to have enough unused space for the new filesystem image to be stored, hence is why this is not the default behaviour.

.. figure:: update_memory_copy.png
:alt: Memory layout for OTA updates
Expand Down