-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
[OTA] Update README wth a more detailed multiple fabrics example #19198
[OTA] Update README wth a more detailed multiple fabrics example #19198
Conversation
PR #19198: Size comparison from cb5b1b3 to ea88535 Full report (39 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, p6, telink)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Every 60 seconds from when ...
- Is this referring to the periodic query timer? Why 60 seconds?
This is listed under the example for triggering via the DefaultOTAProviders attribute which requires that a periodic query timer be used. 60 seconds was arbitrarily picked so that if someone were to follow the example, they weren't waiting too long before seeing the trigger occur. That sentence was only there as an explanation for the sequence of commands listed in the above example. |
PR #19198: Size comparison from cb5b1b3 to cd3f006 Increases above 0.2%:
Increases (37 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, p6, telink)
Decreases (5 builds for cc13x2_26x2, efr32, linux)
Full report (39 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, p6, telink)
|
Problem
There has been some confusion as to how to execute some test plans when it comes to multiple fabrics and OTA
Change overview
Add a detailed example of how to commission two providers onto two fabrics and one requestor onto each of those fabrics
Testing
No functional change. Tree compiles.