|
1 |
| -# Running Matter Examples on the TI SimpleLink CC2674P10 and CC2674R10 |
2 |
| - |
3 |
| -The existing Matter project examples are based on LP_EM_CC1354P10_6. If using |
4 |
| -the CC2674P10, the following migration steps are required. Developers are |
5 |
| -strongly encouraged to start with a `cc13x4_26x4` example and migrate the |
6 |
| -project accordingly. Example projects can be found in the following location: |
7 |
| -`matter/examples/[application]/cc13x4_26x4` |
8 |
| - |
9 |
| -## Dependencies |
10 |
| - |
11 |
| -The following must be installed on your system before proceeding: |
12 |
| - |
13 |
| -- [SysConfig](https://www.ti.com/tool/SYSCONFIG) v1.16.2 or later |
14 |
| -- [SIMPLELINK-LOWPOWER-F2-SDK](https://www.ti.com/tool/SIMPLELINK-LOWPOWER-SDK) |
15 |
| - v7.10.01.24 |
16 |
| - |
17 |
| -## Matter source code changes |
18 |
| - |
19 |
| -The following are changes to the Matter source code files which should be |
20 |
| -applied to convert a `matter/examples/[application]/cc13x4_26x4` project to the |
21 |
| -CC2674P10 device |
22 |
| - |
23 |
| -- `examples/[application]/cc13x4_26x4/args.gni`, modify/add the following |
24 |
| - defines for the CC2674 |
25 |
| - - `ti_simplelink_board = CC2674` |
26 |
| - - `ti_simplelink_device = CC2674P10RGZ` |
27 |
| -- `third_party/ti_simplelink_sdk/repo_cc13xx_cc26xx`, replace this folder |
28 |
| - contents with the 7.10.01.24 version from |
29 |
| - [TI's downloads page](https://www.ti.com/tool/download/SIMPLELINK-LOWPOWER-F2-SDK/7.10.01.24) |
30 |
| - which is required to add support SDK for the CC2674P10 device. |
31 |
| - |
32 |
| -## Configuring `chip.syscfg` in the SysConfig GUI |
33 |
| - |
34 |
| -1. To open `matter/examples/[application]/cc13x4_26x4/chip.syscfg` in the GUI, |
35 |
| - add the following line to the top of the file: |
36 |
| - |
37 |
| -``` |
38 |
| - // @cliArgs --product <path to SDK>/.metadata/product.json --board /ti/boards/LP_EM_CC1354P10_6 --rtos freertos |
39 |
| -``` |
40 |
| - |
41 |
| -2. Open the `syscfg` file using the standalone Sysconfig GUI |
42 |
| - (`sysconfig_gui.sh`) from the SysConfig installation folder. |
43 |
| -3. Click on _Show Device View_ and then click _Switch_. |
44 |
| -4. Select _Board_ as _None_ and _Device_ as _`CC2674P10RGZ`_, Unselect |
45 |
| - _`Lock PinMux`_, and click _Confirm_. |
46 |
| -5. To fix errors, make the following module changes: |
47 |
| - - _RF Design_ and _RF Stacks -> BLE -> Radio_: click on _accepting the |
48 |
| - current value_, which should be _`LP_CC2674P10_RGZ`_ in the drop down menu |
49 |
| - for _Based On RF Design_ |
50 |
| - - _TI DEVICES -> Device Configuration_: Clear |
51 |
| - _`XOSC Cap Array Modification`_ |
52 |
| - - _TI DRIVERS -> RF_: Set _Global Event Mask_ as _None_ and _No. of Antenna |
53 |
| - Switch Control Pins_ as _0_ |
54 |
| - - _TI DRIVERS -> UART2 -> `PinMux`_: Set _UART Peripheral_ to _UART0_, _TX |
55 |
| - Pin_ to _`DIO_13/19`_, and _RX Pin_ to _`DIO_12/18`_ |
56 |
| - - _TI DRIVERS APPS -> Button_: Set _`PinMux`_ of _CONFIG_BTN_LEFT_ to |
57 |
| - _`DIO_15`_ and _CONFIG_BTN_RIGHT_ to _`DIO_14`_ |
58 |
| - - _TI DRIVERS APPS -> LED_: Set _`PinMux`_ of _CONFIG_LED_RED_ to _`DIO_6`_ |
59 |
| - and _CONFIG_LED_RIGHT_ to _`DIO_7`_ |
60 |
| -6. Save the SysConfig file (click on _Save As_) and ensure the file name matches |
61 |
| - the reference from `BUILD.gn` (default project name is `chip.syscfg`). |
62 |
| -7. Open the new SysConfig file with a text editor and remove the generated |
63 |
| - arguments. |
64 |
| - ``` |
65 |
| - /** |
66 |
| - * These arguments were used when this file was generated. They will be automatically applied on subsequent loads |
67 |
| - * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments. |
68 |
| - * @cliArgs --device "CC2674P10RGZ" --package "RGZ" --part "Default" --rtos "freertos" --product "simplelink_cc13xx_cc26xx_sdk@7.10.01.24" |
69 |
| - * @versions {"tool":"1.18.0+3130"} |
70 |
| - */ |
71 |
| - ``` |
72 |
| -8. Move the `*.syscfg` file into the |
73 |
| - `matter/examples/[application]/cc13x4_26x4/` folder. Make sure that the |
74 |
| - `args.gni` parameters are aligned for the `CC2674P10RGZ` as detailed above, |
75 |
| - and build the example using the `README.md` instructions. |
76 |
| -
|
77 |
| -## Modifications required for the CC2674R10 |
78 |
| -
|
79 |
| -After applying all items in the "Configuring `chip.syscfg` in the SysConfig GUI" |
80 |
| -section, additional steps must also be applied to generate Matter project for |
81 |
| -the CC2674R10. |
82 |
| -
|
83 |
| -- `examples/[application]/cc13x4_26x4/args.gni` should have |
84 |
| - `ti_simplelink_board` as `CC2674` and `ti_simplelink_device = CC2674R10RGZ`. |
85 |
| -- `examples/[application]/cc13x4_26x4/chip.syscfg` opened with a Text Editor |
86 |
| - should change `ble.radioConfig.codeExportConfig.$name` to |
87 |
| - `ti_devices_radioconfig_code_export_param2` and `ble.rfDesign` to |
88 |
| - `LP_EM_CC1354P10_1` |
89 |
| -
|
90 |
| -Furthermore, the subsequent changes apply specifically for the CC2674R10 and |
91 |
| -should be addressed from a SysConfig Editor. |
92 |
| -
|
93 |
| -1. Pins will need to be reconfigured as such: |
94 |
| -
|
95 |
| - | SysConfig pin name | R10 `PinMux` | |
96 |
| - | ------------------ | ------------ | |
97 |
| - | UART_RX | `DIO_2` | |
98 |
| - | UART_TX | `DIO_3` | |
99 |
| - | CONFIG_BTN_LEFT | `DIO_13` | |
100 |
| - | CONFIG_BTN_RIGHT | `DIO_14` | |
101 |
| - | CONFIG_LED_RED | `DIO_6` | |
102 |
| - | CONFIG_LED_GREEN | `DIO_7` | |
103 |
| -
|
104 |
| -2. _Custom -> IEEE 802.15.4-2006, `250 kbps`, `OQPSK`, `DSSS = 1:8` -> Code |
105 |
| - Export Configuration_, acknowledge and dismiss the PA radio setup error |
106 |
| -3. _Custom -> IEEE 802.15.4-2006, `250 kbps`, `OQPSK`, `DSSS = 1:8` -> RF |
107 |
| - Command Symbols_, change `CMD_RADIO_SETUP` from `RF_cmdRadioSetup` to |
108 |
| - `RF_cmdIeeeRadioSetup` and add the following functions from the drop-down: |
109 |
| - `CMD_TX_TEST`,`CMD_IEEE_ED_SCAN`, `CMD_IEEE_CSMA`, and `CMD_IEEE_RX_ACK`. |
| 1 | +# Running Matter Examples on the TI SimpleLink CC2674P10 and CC2674R10 |
| 2 | + |
| 3 | +The existing Matter project examples are based on LP_EM_CC1354P10_6. If using |
| 4 | +the CC2674P10, the following migration steps are required. Developers are |
| 5 | +strongly encouraged to start with a `cc13x4_26x4` example and migrate the |
| 6 | +project accordingly. Example projects can be found in the following location: |
| 7 | +`matter/examples/[application]/cc13x4_26x4` |
| 8 | + |
| 9 | +## Dependencies |
| 10 | + |
| 11 | +The following must be installed on your system before proceeding: |
| 12 | + |
| 13 | +- [SysConfig](https://www.ti.com/tool/SYSCONFIG) v1.16.2 or later |
| 14 | +- [SIMPLELINK-LOWPOWER-F2-SDK](https://www.ti.com/tool/SIMPLELINK-LOWPOWER-SDK) |
| 15 | + v7.10.01.24 |
| 16 | + |
| 17 | +## Matter source code changes |
| 18 | + |
| 19 | +The following are changes to the Matter source code files which should be |
| 20 | +applied to convert a `matter/examples/[application]/cc13x4_26x4` project to the |
| 21 | +CC2674P10 device |
| 22 | + |
| 23 | +- `examples/[application]/cc13x4_26x4/args.gni`, modify/add the following |
| 24 | + defines for the CC2674 |
| 25 | + - `ti_simplelink_board = CC2674` |
| 26 | + - `ti_simplelink_device = CC2674P10RGZ` |
| 27 | +- `third_party/ti_simplelink_sdk/repo_cc13xx_cc26xx`, replace this folder |
| 28 | + contents with the 7.10.01.24 version from |
| 29 | + [TI's downloads page](https://www.ti.com/tool/download/SIMPLELINK-LOWPOWER-F2-SDK/7.10.01.24) |
| 30 | + which is required to add support SDK for the CC2674P10 device. |
| 31 | + |
| 32 | +## Configuring `chip.syscfg` in the SysConfig GUI |
| 33 | + |
| 34 | +1. To open `matter/examples/[application]/cc13x4_26x4/chip.syscfg` in the GUI, |
| 35 | + add the following line to the top of the file: |
| 36 | + |
| 37 | +``` |
| 38 | + // @cliArgs --product <path to SDK>/.metadata/product.json --board /ti/boards/LP_EM_CC1354P10_6 --rtos freertos |
| 39 | +``` |
| 40 | + |
| 41 | +2. Open the `syscfg` file using the standalone Sysconfig GUI |
| 42 | + (`sysconfig_gui.sh`) from the SysConfig installation folder. |
| 43 | +3. Click on _Show Device View_ and then click _Switch_. |
| 44 | +4. Select _Board_ as _None_ and _Device_ as _`CC2674P10RGZ`_, Unselect |
| 45 | + _`Lock PinMux`_, and click _Confirm_. |
| 46 | +5. To fix errors, make the following module changes: |
| 47 | + - _RF Design_ and _RF Stacks -> BLE -> Radio_: click on _accepting the |
| 48 | + current value_, which should be _`LP_CC2674P10_RGZ`_ in the drop down menu |
| 49 | + for _Based On RF Design_ |
| 50 | + - _TI DEVICES -> Device Configuration_: Clear |
| 51 | + _`XOSC Cap Array Modification`_ |
| 52 | + - _TI DRIVERS -> RF_: Set _Global Event Mask_ as _None_ and _No. of Antenna |
| 53 | + Switch Control Pins_ as _0_ |
| 54 | + - _TI DRIVERS -> UART2 -> `PinMux`_: Set _UART Peripheral_ to _UART0_, _TX |
| 55 | + Pin_ to _`DIO_13/19`_, and _RX Pin_ to _`DIO_12/18`_ |
| 56 | + - _TI DRIVERS APPS -> Button_: Set _`PinMux`_ of _CONFIG_BTN_LEFT_ to |
| 57 | + _`DIO_15`_ and _CONFIG_BTN_RIGHT_ to _`DIO_14`_ |
| 58 | + - _TI DRIVERS APPS -> LED_: Set _`PinMux`_ of _CONFIG_LED_RED_ to _`DIO_6`_ |
| 59 | + and _CONFIG_LED_RIGHT_ to _`DIO_7`_ |
| 60 | +6. Save the SysConfig file (click on _Save As_) and ensure the file name matches |
| 61 | + the reference from `BUILD.gn` (default project name is `chip.syscfg`). |
| 62 | +7. Open the new SysConfig file with a text editor and remove the generated |
| 63 | + arguments. |
| 64 | + ``` |
| 65 | + /** |
| 66 | + * These arguments were used when this file was generated. They will be automatically applied on subsequent loads |
| 67 | + * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments. |
| 68 | + * @cliArgs --device "CC2674P10RGZ" --package "RGZ" --part "Default" --rtos "freertos" --product "simplelink_cc13xx_cc26xx_sdk@7.10.01.24" |
| 69 | + * @versions {"tool":"1.18.0+3130"} |
| 70 | + */ |
| 71 | + ``` |
| 72 | +8. Move the `*.syscfg` file into the |
| 73 | + `matter/examples/[application]/cc13x4_26x4/` folder. Make sure that the |
| 74 | + `args.gni` parameters are aligned for the `CC2674P10RGZ` as detailed above, |
| 75 | + and build the example using the `README.md` instructions. |
| 76 | +
|
| 77 | +## Modifications required for the CC2674R10 |
| 78 | +
|
| 79 | +After applying all items in the "Configuring `chip.syscfg` in the SysConfig GUI" |
| 80 | +section, additional steps must also be applied to generate Matter project for |
| 81 | +the CC2674R10. |
| 82 | +
|
| 83 | +- `examples/[application]/cc13x4_26x4/args.gni` should have |
| 84 | + `ti_simplelink_board` as `CC2674` and `ti_simplelink_device = CC2674R10RGZ`. |
| 85 | +- `examples/[application]/cc13x4_26x4/chip.syscfg` opened with a Text Editor |
| 86 | + should change `ble.radioConfig.codeExportConfig.$name` to |
| 87 | + `ti_devices_radioconfig_code_export_param2` and `ble.rfDesign` to |
| 88 | + `LP_EM_CC1354P10_1` |
| 89 | +
|
| 90 | +Furthermore, the subsequent changes apply specifically for the CC2674R10 and |
| 91 | +should be addressed from a SysConfig Editor. |
| 92 | +
|
| 93 | +1. Pins will need to be reconfigured as such: |
| 94 | +
|
| 95 | + | SysConfig pin name | R10 `PinMux` | |
| 96 | + | ------------------ | ------------ | |
| 97 | + | UART_RX | `DIO_2` | |
| 98 | + | UART_TX | `DIO_3` | |
| 99 | + | CONFIG_BTN_LEFT | `DIO_13` | |
| 100 | + | CONFIG_BTN_RIGHT | `DIO_14` | |
| 101 | + | CONFIG_LED_RED | `DIO_6` | |
| 102 | + | CONFIG_LED_GREEN | `DIO_7` | |
| 103 | +
|
| 104 | +2. _Custom -> IEEE 802.15.4-2006, `250 kbps`, `OQPSK`, `DSSS = 1:8` -> Code |
| 105 | + Export Configuration_, acknowledge and dismiss the PA radio setup error |
| 106 | +3. _Custom -> IEEE 802.15.4-2006, `250 kbps`, `OQPSK`, `DSSS = 1:8` -> RF |
| 107 | + Command Symbols_, change `CMD_RADIO_SETUP` from `RF_cmdRadioSetup` to |
| 108 | + `RF_cmdIeeeRadioSetup` and add the following functions from the drop-down: |
| 109 | + `CMD_TX_TEST`,`CMD_IEEE_ED_SCAN`, `CMD_IEEE_CSMA`, and `CMD_IEEE_RX_ACK`. |
| 110 | +
|
| 111 | +## Building examples for the CC1354P10-1 |
| 112 | +
|
| 113 | +To migrate the CC1354P10-6 examples to the CC1354P10-1 platform, there are only |
| 114 | +two steps: |
| 115 | +
|
| 116 | +1. `examples/[application]/cc13x4_26x4/args.gni` should have |
| 117 | + `ti_simplelink_board` as `CC1354P10-1` |
| 118 | +2. `examples/[application]/cc13x4_26x4/chip.syscfg` opened with a Text Editor |
| 119 | + should change `ble.radioConfig.codeExportConfig.$name` to |
| 120 | + `ti_devices_radioconfig_code_export_param2` and `ble.rfDesign` to |
| 121 | + `LP_EM_CC1354P10_1` |
| 122 | +
|
| 123 | +After this, the example's `README.md` instructions can be followed to produce |
| 124 | +the executable needed. |
0 commit comments