CC2652R: Matter controller and commissioner, how to use DMM / BLE / Thread ?

Hi,

James Austrial said:

   I also find that DMM / BLE / Thread example exist in third_party directory in TI openthread SDK.

Are you referring to this one?
https://github.com/TexasInstruments/ot-ti/tree/thread-v1.x-ti-eng/examples/apps/dmm

To build that, you must first follow here: https://github.com/TexasInstruments/ot-ti/tree/thread-v1.x-ti-eng?tab=readme-ov-file#toolchain

Then, follow this: https://github.com/TexasInstruments/ot-ti/blob/thread-v1.x-ti-eng/examples/apps/dmm/README.md

(NOTE: for building, I recommend to use an x86 or Intel -based linux environment).

This RCP-HCI project is a proof of concept which shows that a single CC1354P10-6 LP can act as both Thread RCP and BLE HCI at same time.

Currently we do not have Matter commissioner enabled here, but it may be enabled in future.

I welcome you to try the example out, as detailed in its README.

Thanks,
Toby

Hi Toby :

  Thanks for your information.
 
  This feature (RCP-HCI) meets our specifications but doesn't seem to execute on the
  cc2652r1 development board.
 
  According to description of the document, the feature currently seems to only be executed on cc1354p10-6.
  How can I make it execute on cc2652r1 ?
  Can it be ported to the cc2652r1 development board ?
 
  cc2652r1 datasheet shows that there are 2 build-in uart interface.
 
  Harrison Yeh

Hi Harrison,

Harrison Yeh said:

This feature (RCP-HCI) meets our specifications but doesn't seem to execute on the
  cc2652r1 development board.

You are correct, currently it is not developed on CC2652R1.

Harrison Yeh said:

  How can I make it execute on cc2652r1 ?
  Can it be ported to the cc2652r1 development board ?

It may be possible, but there may be some RAM limitations... you could try to take these code changes to port it to CC2652R1: https://github.com/TexasInstruments/ot-ti/commit/5d561ba2bb769912203b9548d43a2e3c672c01b2

Thanks,
Toby

Hi Toby :

I compile ti  thread SDK and select cc1354p10-6 board as target.

I got some compilation issues.

There are aligment and function link issues.

I am not sure if the compilation procedures are completed or not ?

Do you see any output files from the build?
https://github.com/TexasInstruments/ot-ti/tree/thread-v1.x-ti-eng?tab=readme-ov-file#flash-binaries

Did the initialization steps all pass?
https://github.com/TexasInstruments/ot-ti/tree/thread-v1.x-ti-eng?tab=readme-ov-file#toolchain

What Linux distribution are you using? What is the underlying ISA (Arm? x86?)

Hi Toby :

1. I can see the following .out files in build/bin directory.

    i) ot-cli-ftd.out

    ii) ot-cli-mtd.out

    iii) ot-cli-radio.out

    vi) ot-rcp.out

    During compilation, there are error messages showed above. I am not sure if they are executable files or not ?

2. Initialization steps are all passed.

3. I use ubuntu 22.04 and ISA is x86.

I find compiler difference between main and thread-v1.x-ti-eng branches.

gcc-arm-none-eabi-9-2020-q2-update is used in main branch.

arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi is used in thread-v1.x-ti-eng branch.

I can compile successfully in main branch but rcp_hci is not included in main branch.

Another questions !!

1. How can I port rcp_hci feature from cc1354p10-6 to cc2652r1by using thread-v1.x-ti-eng branch ?

    Are there any porting guides that I can consult to it ?

Thanks !

Harrison Yeh

Hi Harrison,

Harrison Yeh said:

1. I can see the following .out files in build/bin directory.

    i) ot-cli-ftd.out

    ii) ot-cli-mtd.out

    iii) ot-cli-radio.out

    vi) ot-rcp.out

    During compilation, there are error messages showed above. I am not sure if they are executable files or not ?

All the .out files can be loaded to the device.

But I do not see the ot-rcp-hci.out file -- did you build with the --DBLE_HCI=1 option?
Please see here: https://github.com/TexasInstruments/ot-ti/tree/thread-v1.x-ti-eng?tab=readme-ov-file#building

Harrison Yeh said:

3. I use ubuntu 22.04 and ISA is x86.

I find compiler difference between main and thread-v1.x-ti-eng branches.

gcc-arm-none-eabi-9-2020-q2-update is used in main branch.

arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi is used in thread-v1.x-ti-eng branch.

I can compile successfully in main branch but rcp_hci is not included in main branch.

Yes, we used updated compiler for the new branch.

I see the same build warnings on my side. These are not significant warnings, and the firmware should still work as intended.

Harrison Yeh said:

1. How can I port rcp_hci feature from cc1354p10-6 to cc2652r1by using thread-v1.x-ti-eng branch ?

    Are there any porting guides that I can consult to it ?

Currently there are no porting guide, as CC2652R1 was not scoped for this engineering release.
For now the entire changes to enable it for CC1354P10-6 are conveniently shown here: https://github.com/TexasInstruments/ot-ti/commit/5d561ba2bb769912203b9548d43a2e3c672c01b2#diff-99b83631df533ea1d9c97396a043a4670464f523d0c1e60b0a1cab6dddd440f9

The script/build and script/bootstrap apply to all devices, so probably no changes needed there.
But, there are some library files here: https://github.com/TexasInstruments/ot-ti/commit/5d561ba2bb769912203b9548d43a2e3c672c01b2#diff-1e5b116c24a2ee059c21b84417af4e094145ac5300dbc210e86a8d1a25fc8c97

Those library files may not be compatible for CC2652R1. So I recommend for now to do development with CC1354P10-6 (eventually this is more easily ported to CC2674R10).

Thanks,
Toby