[ota-provider-app] Support for error/timeout midway in transfer and later resume #11760
Comments
|
@holbrookt could you help to take a look? |
|
This seems necessary for cert and 1.0. Can you confirm @ukatira ? |
|
I think Resume functionality got moved to post V1.0 so this will be needed when Requestors can support resuming a transfer previously aborted. |
|
I think even without resume supported, this part can still be validated:
|
isiu-apple
added a commit
to isiu-apple/connectedhomeip
that referenced
this issue
Mar 3, 2022
…ut midway in transfer
isiu-apple
added a commit
to isiu-apple/connectedhomeip
that referenced
this issue
Mar 3, 2022
…ut midway in transfer
isiu-apple
added a commit
to isiu-apple/connectedhomeip
that referenced
this issue
Mar 3, 2022
…ut midway in transfer
isiu-apple
added a commit
to isiu-apple/connectedhomeip
that referenced
this issue
Mar 4, 2022
…ut midway in transfer
woody-apple
pushed a commit
that referenced
this issue
Mar 5, 2022
…out (#15768) * Issue #11760 - [ota-provider-app] Support for error/timeout midway in transfer * restyle-diff.sh changes * Code review changes. - Moved mTimeout to BDXDownloader class. - Moved prevPercentageComplete to BDXDownloader class. - Renamed StartTimeoutTimerHandler to TransferTimeoutCheckHandler. - Added sanity checks. * Code review changes. - Moved mTimeoutSec to a constant define kTimeoutSec. - Moved resetting of timeout timer and prevPercentageComplete to a Reset() function. * Code review changes. - Renamed prevPercentageComplete to mPrevPercentageComplete * Code review changes. - Renmed CheckTransferTimeout() to HasTransferTimedOut(). - Calculate timeout using block counter instead of percentage complete. - Use 5*60 instead of 300 for timeout value for readability. * Fix merge issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
There is no way right now to trigger an error/timeout midway in OTA file transfer.
Proposed Solution
Add support for error/timeout midway in OTA file transfer in the ota-provider-app to verify requestor handles these correctly and can resume transfer successfully.
Section 11.20.3.5 Pg 665: Idle time-out SHALL be no less than 5 minutes for either Receiver-Driver or Asynchronous mode, before aborting a transfer.
Section 11.20.3.5 Pg 666: The ReceiveInit message from the OTA Requestor MAY have the RC[STARTOFS] bit set and associated STARTOFS field set to indicate the resumption of a transfer previously aborted, or to affect partial windowed access to the portion of a Software Image desired.
The text was updated successfully, but these errors were encountered: