-
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 Refactoring -- Part 1 #12119
OTA Requestor Refactoring -- Part 1 #12119
Conversation
…uestor_refactoring_1
This can be removed once OperationalDeviceProxy can resolve the IP Address from Node IDconnectedhomeip/examples/ota-requestor-app/linux/main.cpp Lines 86 to 96 in 28f991b
This comment was generated by todo based on a
|
enable SetDownloaderInstance(downloaderCore);connectedhomeip/examples/ota-requestor-app/linux/main.cpp Lines 225 to 235 in 28f991b
This comment was generated by todo based on a
|
Determine where this should be instantiatedconnectedhomeip/src/app/clusters/ota-requestor/OTARequestor.cpp Lines 256 to 266 in 28f991b
This comment was generated by todo based on a
|
…essfully. The top-level build fails for all-cluster app.
…estor app Update .gn files so that clusters/ota-requestor is not built for all example apps (this is different from the rest of the clusters). Instead, explicitly specify clusters/ota-requestor sources in the OTA-Requestor example app
…uestor_refactoring_1
…uestor_refactoring_1
PR #12119: Size comparison from 2bd6bd6 to 1543a39 Increases above 0.2%:
Increases (29 builds for esp32, k32w, linux, mbed, nrfconnect, p6, qpg)
Decreases (20 builds for esp32, k32w, linux, mbed, nrfconnect, p6, qpg)
Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, 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.
Fast tracking given this has been in review for a while.
Problem
OTA Requestor needs to have a proper Application and Platform API
Change overview
Note that this is the first in a series of PRs that will fully refactor the Requestor functionality, more changes are coming.
Testing
Confirmed that the Requestor/Provider scenario works in a single Linux node. Commands:
rm -r /tmp/chip_*
./out/debug/chip-ota-provider-app -f /tmp/ota.txt
./out/chip-tool pairing onnetwork 1 20202021
./out/debug/chip-ota-requestor-app -u 5560 -d 42 -i ::1
./out/chip-tool pairing onnetwork-long 2 20202021 42
./out/chip-tool otasoftwareupdaterequestor announce-ota-provider 1 0 0 2 0