CC1352P: Getting started with CHIP using the CC1352P

Hello YiKai Chen 

As the CHIP example supports the CC13X2 family. Why we are not able to use the CC1352P for the development

CC1352P supports both Zigbee & Thread protocol. 

Is there any specific reason not to go with CC1352P?

I suppose this is about resource constrains. The CC13x2x7 or CC26x2x7 is pin compatible with, and functionally identical to, their respective CC13x2x1 or CC26x2x1 devices but with an additional 352 kB of flash memory and extra 64 kB of RAM.

Our application is ready with the CC1352P,

Is there any way that we can use CC1352P to integrate with the CHIP SDK?

CHIP is opensource so you can try to do it by yourself.

Will CHIP supports CC1312R7?

Since CHIP is now working on 2.4G only, I don't think it will support CC1312R7 which is subG Hz SOC.

As I am able to see the CC1352P & CC1352R have the same memory constraints.

Why only CC1352R supported instead of CC1352P?

CC1352P7 and CC2652R7 are SimpleLink Arm Cortex-M4F multiprotocol wireless MCU with 704k flash.

Hello YiKai Chen

I have compared the CC1352P1  CC1352P7 block diagram & I am able to see both have the same configurations in terms of memory & architecture as follows.

How they differ from each other.

How would I get the correct document for the CC1352P7?

Wait TI release.

@Toby Pan & @Ryan Brown1,

Will you please help me to get more information related to CC1352P7?

What is the reason behind including additional flash & RAM memory to CC1352P for supporting the matter(CHIP)?

@YiKai Chen & @Ryan Brown1

Will you please help me to know the specific reason for,

1. Why matter (CHIP) is not supporting the CC1352P1?

2. Is that memory is only the issue?  If yes, How It affects the matter?

Though the CC1352P1 is a multiprotocol IC, I just want to implement the thread protocol using the CC1352P1 to interface with the matter (CHIP).

Why it's not possible?

matter (CHIP) would use large flash so CC1352P1 internal flash size is not enough. What's the point to argue why a previous designed SOC CC1352P1 has to support a newly release matter (CHIP) protocol?

matter (CHIP) would use large flash so CC1352P1 internal flash size is not enough.

>> Is that mean the matter(CHIP) SDK will be integrated over CC1352P7?

I would like to run matter(CHIP) SDK over Raspberry PI & then try to communicate with the Thread Border Router to establish the thread network.

Please correct me, If I am wrong.

We are using separate CC1352P1 SOC to design for each protocol like Zigbee, Thread & Sub1 Dongles.

As the thread does not have any standard protocol, we would like to use the matter for it in the future.

If the matter will not support the CC1352P1 then how can we make our thread dongle matter compatible if you say cc1352P1 doesn't support matter.

If you mean to run matter(CHIP) SDK over Raspberry PI which would act as Thread Border Router. I suppose you can make CC1352P as RCP to do this. CC1352P7 or CC2652R7 is only needed when you want to run matter(CHIP) on SOC mode.

yes, I would like to use the matter(CHIP) SDK over raspberry pi to control the CC1352P Thread Broder Router,
as the Zigbee Linux Gateway used for the CC1352P ZNP.

That's why I am asking, Will matter supports CC1352P1 or not?

If Yes, Is there any document for getting started with CC1352P1 & matter(CHIP)

Hi,

Perhaps you will find our accessory device README helpful : https://github.com/project-chip/connectedhomeip/tree/master/examples/lock-app/cc13x2x7_26x2x7

We do have the NCP example for CC1352P : https://dev.ti.com/tirex/explore/node?node=APIEuJmrIgn0VOCN454xew__pTTHBmu__LATEST

Additionally : https://github.com/openthread/ot-cc13x2-cc26x2

Thanks,
Toby

We do have the NCP example for CC1352P: https://dev.ti.com/tirex/explore/node?node=APIEuJmrIgn0VOCN454xew__pTTHBmu__LATEST

>> Will this NCP example works with matter? We still not clear with the matter implementation with the SOCs.

Is there any core person who guides us to start the development?

NCP will be replaced by RCP which is for connecting to border router and the Matter implementation won't be on RCP/NCP.

As the matter is open source code, Is it possible to run it over raspberry pi?

Yes, it's possible.

Then how will it provide a communication interface over the Thread network?

Border router is designed for bridging internet/intranet with Thread network.

Are you meaning to say that,

the matter will work over raspberry pi & the thread border router will connected to the same network without any physical contact with the raspberry pi.

I couldn't understand what you mean without any physical contact with the raspberry pi. Maybe you can refer to https://training.ti.com/ti-matter-technology-demo-unified-standard-connected-objects to have a better understanding on use scenario.

I couldn't understand what you mean without any physical contact with the raspberry pi.

>> physical contact in the sense of UART or USB communication with the raspberry pi

If Matter runs on Raspberry Pi and you mean to communicate with Matter/Thread device, the RCP connecting through UART is still mandatory.

Thanks for sharing this link https://training.ti.com/ti-matter-technology-demo-unified-standard-connected-objects
Now I am somehow cleared with the matter.

Please correct me If I am wrong...

As the demo video explaining the CC2652R1 is used as a border router & communicating the matter which is running over BBB.

We have the same use case, just difference is we want to use CC1352P1 instead of CC2652R1 & raspberry pi instead of the BBB.

Is that possible?

Yes, that's possible and you can refer to https://openthread.io/guides/border-router/raspberry-pi to setup up Raspberry Pi border router.

Is there any referenced document for the setup matter over BBB or raspberry pi?

No but you can refer to my similar test in sunmaysky.blogspot.com/.../project-connected-home-over-ip-chip.html

Thanks for the information,

Is the OTBR & WIFI Access Point setup momentary with the matter (CHIP)? 
I thought the matter (CHIP) SDK itself manages thread border router?

I would say NO. If you don't use OpenThread node in your Matter(CHIP) system, you don't need OTBR.