-
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
Switch to Telink Zephyr main branch (get rid of maintaining special Zephyr branch) #25940
Conversation
35e5a03
to
71f1c20
Compare
PR #25940: Size comparison from 7ccd5d4 to 71f1c20 Increases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
71f1c20
to
5d4e80f
Compare
Please review this PR its touches only Telink vendor and focused on getting rid of special Zephyr branch for Matter project switching to main one (Due to resources it's difficult to maintain special branch) |
8308b4f
to
403b500
Compare
Hi @andriy-bilynskyy Devices are unable to be commissioned, since there is no BLE packet sent. Do you have any idea to fix it? |
On which platform have you observed the issue? All merged files are relative only to Telink. Telink nightly CI tests (includung BLE) are OK as I know. |
@andriy-bilynskyy Yes. telink platform. But acturally, devices does not send BLE advertisement packets. |
In that case please create ticket with your case details (used commit hashes, zephyr hash if yo are not using docker, sample app you are using, changes in configs). Because mainly it works as I already told all commissioning tests on our CI are passed. |
BTW: if you are using docker please change it's version. Commit introduces new docker version. With old docker it definitely not working. |
Thanks @andriy-bilynskyy . After updating zephyr, it works! |
Change overview
Update the Telink BLEManagerImpl module
Update the Telink ThreadStackManagerImpl module
Update telink image to 0.6.52 (use Telink main Zephyr branch)
Testing
Tested manually with chip-tool.
Steps:
Run: $ chip-tool pairing ble-thread <...>
Wait till success
Run: $ chip-tool onoff on ${NODE_ID }1
Wait till success
Run: $ chip-tool onoff off ${NODE_ID }1
Wait till success