CC2652R7: Matter with AppleTV

Hi Fredrik,

fredrikgk said:

1) Is there an interoperability issue between TI Matter projects and Apple devices?

I was able to get this working with lighting-app (as recent as last month) on iPad and Apple TV. This was with the latest commit on master branch.

fredrikgk said:

2) This pull request seems to indicate removal of support for CC2652R7. Is that the case? Do we have to change to an x4 device? 

Correct, due to the increased flash consumption of Matter, we now recommend the CC1354/CC2674, such as here: https://github.com/project-chip/connectedhomeip/tree/master/examples/lighting-app/cc13x4_26x4

fredrikgk said:

We have made a Matter Occupancy sensor product with CC2652R7. We have successfully tested it with Google Nest, but we are not able to connect with an AppleTV

fredrikgk said:

We then tried the default TI lock app demo which also did not connect to the AppleTV. 

Which commit are you using? If it is an older one which had supported CC2652R7, then it's possible to have gotten "too far" behind the (auto-updated?) Apple Home / Apple TV OSes.

Can you share a serial log of what you see during commissioning?

Thanks,
Toby

Hi Toby,

Toby said:

I was able to get this working with lighting-app (as recent as last month) on iPad and Apple TV. This was with the latest commit on master branch.

I guess you were running lighting-app on CCxxx4?

Toby said:

Correct, due to the increased flash consumption of Matter, we now recommend the CC1354/CC2674

Does " we recommend the CCxxx4", really mean that Matter will not be supported at all on CC2652R7 going forward? If so, there is some documentation that should be updated accordingly. CC2652R7 is still listed as Matter compatible for example here. Btw. I remember when it was deemed crazy that the BLE Stack required 100 kB in addition to code in ROM. Now we need a 1M device to run a protocol stack? 

I belive we have tried v1.0-ti-branch. I colleague also mentioned trying tag v1.2.0.1. 

I do not have the log from the lock-app available right now, but here is what it looks like from our app:

OpenThread started: OK
Setting OpenThread device type to MINIMAL END DEVICE
Initialize Server
Subscription persistence not supported
Server initializing...
Last Known Good Time: 2023-10-14T01:16:48
AccessControl: initializing
Examples::AccessControlDelegate::Init
AccessControl: setting
DefaultAclStorage: initializing
DefaultAclStorage: 0 entries loaded
Using ZAP configuration...
AccessControlCluster: initializing
Initiating Admin Commissioning cluster.
Cluster callback: 0x0000_0030
Cluster callback: 0x0000_0406
Cluster callback: 0x0000_0406
Updating services using commissioning mode 0
Failed to remove advertised services: 3
Advertise commission parameter vendorID=65521 productID=32775 discriminator=3840/15 cm=0
Failed to advertise extended commissionable node: 3
Failed to finalize service update: 3
CASE Server enabling CASE session setups
Joining Multicast groups
Server Listening...
Initialize LEDs
Initialize buttons
Cluster callback: 0x0000_0406
Cluster callback: 0x0000_0406
Device Configuration:
  Serial Number: TEST_SN
  Vendor Id: 65521 (0xFFF1)
  Product Id: 32775 (0x8007)
  Product Name: TEST_PRODUCT
  Hardware Version: 0
  Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
  Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
  Manufacturing Date: (not set)
  Device Type: 65535 (0xFFFF)
SetupQRCode: [MT:ALG0242C00KA0648G00]
Copy/paste the below URL in a browser to see the QR Code:
https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AALG0242C00KA0648G00
Manual pairing code: [34970112332]
*** Novelda Sensor ID: 0xE6EC03E6 Chip Version: 1 ***

I believe the output from the lock-app looks fairly similar, but it does not include the pairing- and QR-code.

Thanks,
Fredrik

fredrikgk said:

I guess you were running lighting-app on CCxxx4?

Yes.

fredrikgk said:

Does " we recommend the CCxxx4", really mean that Matter will not be supported at all on CC2652R7 going forward? If so, there is some documentation that should be updated accordingly. CC2652R7 is still listed as Matter compatible for example here. Btw. I remember when it was deemed crazy that the BLE Stack required 100 kB in addition to code in ROM. Now we need a 1M device to run a protocol stack? 

Thanks for pointing that ti.com page out. We may have updates pipelined for it, I'll reach out to the web stakeholders.

I'll also ask for an official statement, but yes, to my knowledge CC2652R7 would not be a viable for single-chip Matter application. 

fredrikgk said:

I do not have the log from the lock-app available right now, but here is what it looks like from our app:

The logs shown here are printed at device startup. Are you able to get logs which include the commissioning process?

The logs include commissioning. In other words, nothing happens :-)

I anyway guess that the only path forward is to use a 1 MB device?

Thanks Toby! I have ordered a couple of CC1354P10 LaunchPads