-
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-requestor-app] Reference implementation for AnnounceOTAProvider command #10434
[ota-requestor-app] Reference implementation for AnnounceOTAProvider command #10434
Conversation
uncomment and fill in after #7976 is fixedconnectedhomeip/examples/ota-requestor-app/ota-requestor-common/ExampleRequestorDelegate.cpp Lines 51 to 61 in 51a9052
This comment was generated by todo based on a
|
PR #10434: Size comparison from 05c3a35 to d094004 8 builds (for k32w, p6, qpg, telink)
|
PR #10434: Size comparison from 05c3a35 to d84ef38 5 builds (for p6, qpg, telink)
5 builds (for k32w, mbed)
4 builds (for efr32)
12 builds (for esp32, nrfconnect)
|
examples/ota-requestor-app/ota-requestor-common/ExampleRequestorDelegate.cpp
Outdated
Show resolved
Hide resolved
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.
Thanks for the quick turnaround!
PR #10434: Size comparison from 0c16976 to c6249e6 Increases above 1.0% from 0c16976 to c6249e6:
18 builds (for k32w, linux, mbed, p6, qpg, telink)
4 builds (for efr32)
2 builds (for esp32)
10 builds (for nrfconnect)
|
Currently blocked by #10818 |
@holbrookt I can fast track this, can you resolve the build failures? |
examples/ota-requestor-app/ota-requestor-common/BDXDownloader.cpp
Outdated
Show resolved
Hide resolved
examples/ota-requestor-app/ota-requestor-common/BDXDownloader.cpp
Outdated
Show resolved
Hide resolved
examples/ota-requestor-app/ota-requestor-common/BDXDownloader.cpp
Outdated
Show resolved
Hide resolved
@woody-apple #10888 needs to be merged first. Then it should be good to go after a rebase |
PR #10434: Size comparison from febbaa6 to b751b49 Increases above 1.0% from febbaa6 to b751b49:
16 builds (for k32w, linux, p6, qpg, telink)
4 builds (for efr32)
4 builds (for mbed)
2 builds (for esp32)
10 builds (for nrfconnect)
|
…command (project-chip#10434) * implement ota-requestor command handlers and delegate class * fix ota requestor delegate comment * logging improvements from Tennessee's suggestions * logging improvements/fixes and some name changes * change AnnounceOTAProvider providerLocation field to chip::NodeID * suggestions from Sergei - handle default in announcementReason switch statement - use auto & in emberAf callback * use kUndefined values instead of Optional for FabricIndex and NodeId * remove accidental esp32 folder * restyling * use DecodeableType in OTA Requestor Delegate * regen with pep8 installed * move emberAf handler for AnnounceOtaProvider to application code * apply new timer argument fix * rename providerId to providerNodeId * remove ota-requestor directory (no longer used) * use CHIP_ERROR_FORMAT
Problem
ota-requestor-app
does not currently implement the OTA Requestor cluster nor does it accept or handle theAnnounceOTAProvider
command.In addition, the current
ota-requestor-app
implementation starts the OTA process immediately, which is not realistic or feasible for all platforms and not useful for certification or testing.AnnounceOTAProvider
can be used to trigger the beginning of the OTA process.Change overview
providerLocation
inAnnounceOTAProvider
to be typeNODE_ID
instead ofBYTE_SPAN
emberAf*
callback forAnnounceOTAProvider
andExampleOTARequestor
class for reusable application logicTesting
Tested using an additional incoming PR which adds esp32 support. The linux
ota-requestor-app
cannot be used for testing because it cannot be commissioned and cannot receive commands fromchip-tool
.