Feature: Adding support for pushing cache images for SUIT updates #190
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.
This PR adds a new feature to DFU updates using SUIT bootloader.
SUIT
In general, a SUIT (Software Update for Internet of Things) allows a .suit file (an Envelope) to contain multiple firmware images or fetch them from different locations given with a URI. #160 added support for polling additional images from the phone. In some cases, a device with SUIT bootloader requires all images to be present before the update is started (e.g. to decrease required memory). For that, nRF Connect SDK 2.8 added support for raw cache images. This PR is adding support for this feature in the Android library.
Changes:
target_id
parameterdefer_install
. When false (default) the update will start immediately after uploading the .suit file (SUIT Envelope). When true, the device will wait for cache images and another call of Upload Envelope, this time withlen=0, off=0, defer_install=false
, which will initiate processing the Envelope.Note
This change should not break backward compatibility with previous devices with SUIT group, which don't support defering installation nor cache images.
Image manager
Additionally, for slome purposes, like device recovery, it is possible for a device to support SUIT update, but with Image manager instead of SUIT manager. The implementation will fall back to Image manager if a command sent to SUIT group will return an error, e.g. NOT SUPPORTED.
For that case, the Firmware Update Manager using Image manager was also modified:
ImageSet
.confirm
command withconfirm=true
parameter, but withouthash
to begin the update. Note, that the reply to this command does not contain image details, like it does in MCUboot variant. The device reboots immediately after receiving aconfirm
command (it may validate the Envelope before doing so).Changes in the sample app
It is possible to: