You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OTA Requestor needs to do various things with the software version it is updating to. A few examples:
During QueryImageResponse, if the software version supplied is the same as current version, ignore and do not proceed - refer to 11.20.3.2. Querying the OTA Provider
After a software update has been applied successfully, the software version should be updated in the OTA Requestor core as well as the Basic clusters SoftwareVersion attribute (the OTA Requestor core should keep this value to support (1) above)
Proposed Solution
Add the following to OTARequestorInterface:
States for the current version vs target version (the new version that provider wants to supply)
Logic to determine when to ignore an image when QueryImageResponse is received
New API in OTARequestorInterface to update the software version when necessary (like after a successful apply)
Maybe in the new API introduced above, it should call Basic::Attributes::SoftwareVersion::Set
The new API should be called by various implementations of OTA after an Apply has succeeded. For instance, in Linux, the OTAImageProcessorImpl::Apply is a no op and should call the new API directly from there with the software version it obtained maybe from the image header. For other platforms, this new API should be called after restarting the app.
The text was updated successfully, but these errors were encountered:
Problem
OTA Requestor needs to do various things with the software version it is updating to. A few examples:
QueryImageResponse
, if the software version supplied is the same as current version, ignore and do not proceed - refer to11.20.3.2. Querying the OTA Provider
SoftwareVersion
attribute (the OTA Requestor core should keep this value to support (1) above)Proposed Solution
Add the following to OTARequestorInterface:
QueryImageResponse
is receivedBasic::Attributes::SoftwareVersion::Set
The new API should be called by various implementations of OTA after an Apply has succeeded. For instance, in Linux, the
OTAImageProcessorImpl::Apply
is a no op and should call the new API directly from there with the software version it obtained maybe from the image header. For other platforms, this new API should be called after restarting the app.The text was updated successfully, but these errors were encountered: