Repository navigation
[nrf toup] Derive BDX download timeout from session round trip - #760
Merged
kkasperczyk-no merged 1 commit intoOct 1, 2026
Merged
Conversation
|
none Note: This comment is automatically posted and updated by the Contribs GitHub Action. |
| constexpr System::Clock::Timeout kExpectedProviderProcessingTime = System::Clock::Seconds16(2); | ||
|
|
||
| // Number of round trips without any BDX progress that is treated as a stalled download. | ||
| constexpr uint32_t kDownloadTimeoutRoundTrips = 2; |
Contributor
There was a problem hiding this comment.
I'm not sure whether this value is not too aggressive. As far as I understand how does it work, we may have a very small round trip time for the device with small communication interval (SED with 1 s sleep, or FTD without sleeping). 2 * roundtrip can be still a very small value, so even short hiccup on the OTA provider side could lead to timeout. Would it make sense to have some lower value to not timeout too often? Some value that we can consider as temporary lag in communication, e.g 7-10 s or something.
Contributor
Author
There was a problem hiding this comment.
Agreed, I added 10s lower bound for download timeout.
dominik-michalczyk-nordic
force-pushed
the
fix_bdx_timeout
branch
from
September 30, 2026 08:52
2353f02 to
66e3b29
Compare
The OTA requestor used a fixed five-minute BDX download timeout, which is far too long for sessions with short retransmission intervals and does not adapt to the peer's advertised session parameters. Compute the timeout from the session round trip time plus the expected provider processing time. Signed-off-by: Dominik Michalczyk <dominik.michalczyk@nordicsemi.no>
dominik-michalczyk-nordic
force-pushed
the
fix_bdx_timeout
branch
from
September 30, 2026 08:55
66e3b29 to
92daf85
Compare
kkasperczyk-no
approved these changes
Oct 1, 2026
ArekBalysNordic
approved these changes
Oct 1, 2026
dominik-michalczyk-nordic
added a commit
to dominik-michalczyk-nordic/ncs-matter
that referenced
this pull request
Oct 1, 2026
From PR: nrfconnect/sdk-connectedhomeip#760 Signed-off-by: Dominik Michalczyk <dominik.michalczyk@nordicsemi.no>
ArekBalysNordic
pushed a commit
to nrfconnect/ncs-matter
that referenced
this pull request
Oct 1, 2026
From PR: nrfconnect/sdk-connectedhomeip#760 Signed-off-by: Dominik Michalczyk <dominik.michalczyk@nordicsemi.no>
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
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.
Summary
The OTA requestor used a fixed five-minute BDX download timeout, which is far too long for sessions with short retransmission intervals and does not adapt to the peer's advertised session parameters. Compute the timeout from the session round trip time plus the expected provider processing time.
Testing
ncs-matter
manifest-pr-skip