[TI] Remove TI CC13x2 Platform Support (project-chip#32877)

* Removal of TI CC13x2 Platform Support

* Restyled by clang-format

* Restyled by gn

* Restyled by prettier-markdown

* Restyled by autopep8

* updated index.md

---------

Co-authored-by: Restyled.io <commits@restyled.io>

Author: abiradarti

.github/workflows/examples-cc13x2x7_26x2x7.yaml .github/workflows/examples-cc13xx_26xx.yaml

@@ -12,7 +12,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-name: Build example - TI CC26X2X7
+name: Build example - TI CC13XX_26XX
 
 on:
     push:
@@ -26,11 +26,11 @@ env:
     CHIP_NO_LOG_TIMESTAMPS: true
 
 jobs:
-    cc26x2x7:
-        name: cc26x2x7
+    cc13xx_26xx:
+        name: cc13xx_26xx
 
         env:
-            BUILD_TYPE: gn_cc26x2x7
+            BUILD_TYPE: gn_cc13xx_26xx
 
         runs-on: ubuntu-latest
         if: github.actor != 'restyled-io[bot]'
@@ -97,11 +97,6 @@ jobs:
                     cc13x4_26x4 LP_EM_CC1354P10_6 lighting-app \
                     out/artifacts/ti-cc13x4_26x4-lighting-mtd/chip-LP_EM_CC1354P10_6-lighting-example.out \
                     /tmp/bloat_reports/
-            - name: Uploading Size Reports
-              uses: ./.github/actions/upload-size-reports
-              if: ${{ !env.ACT }}
-              with:
-                platform-name: cc13x2x7_26x2x7
             - name: Uploading Size Reports
               uses: ./.github/actions/upload-size-reports
               if: ${{ !env.ACT }}

README.md

@@ -9,7 +9,7 @@
 [![ASR](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20ASR/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-asr.yaml)
 [![BouffaloLab](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20BouffaloLab/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-bouffalolab.yaml)
 [![Darwin](https://github.com/project-chip/connectedhomeip/workflows/Darwin/badge.svg)](https://github.com/project-chip/connectedhomeip/blob/master/.github/workflows/darwin.yaml)
-[![TI CC26X2X7](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20TI%20CC26X2X7/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-cc13x2x7_26x2x7.yaml)
+[![TI CC26X2X7](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20TI%20CC13XX_26XX/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-cc13xx_26xx.yaml)
 [![TI CC32XX](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20TI%20CC32XX/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-cc32xx.yaml)
 [![EFR32](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20EFR32/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-efr32.yaml)
 [![ESP32](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20ESP32/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-esp32.yaml)

config/cc13x2_26x2/toolchain/BUILD.gn

@@ -213,7 +213,6 @@ pigweed-app/**/README
 :maxdepth: 1
 
 pump-app/**/README
-pump-app/cc13x2x7_26x2x7/doc/programming*
 ```
 
 ## Pump controller example
@@ -223,7 +222,6 @@ pump-app/cc13x2x7_26x2x7/doc/programming*
 :maxdepth: 1
 
 pump-controller-app/**/README
-pump-controller-app/cc13x2x7_26x2x7/doc/programming*
 ```
 
 ## Refrigerator example

docs/examples/index.md

@@ -470,7 +470,7 @@ gn desc out/unified '//src/controller(//build/toolchain/host:linux_x64_clang)'
 > **Note:** Some platforms that can be built as part of the unified build
 > require downloading additional tools. To add these to the build, the location
 > must be provided as a build argument. For example, to add the Simplelink
-> cc13x2_26x2 examples to the unified build, install
+> cc13xx_26xx examples to the unified build, install
 > [SysConfig](https://www.ti.com/tool/SYSCONFIG) and add the following build
 > arguments:
 >

docs/guides/BUILDING.md

@@ -33,43 +33,40 @@ Each element is described in more detail below:
    Developers can configure this per device. Elements in this file are from the
    specification.
 2. Matter Application with dummy factory data: Any TI Matter example application
-3. `BIM`/MCUBoot: Boot Image Manager/MCUBoot image used for OTA. This is built
-   with the Matter application and does not require additional build steps from
-   developers.
+3. MCUBoot: MCUBoot image used for OTA. This is built with the Matter
+   application and does not require additional build steps from developers.
 4. create_factory_data.py: Processes a factory data JSON file and generates a
    hex file with the unique factory data values configured in the JSON file.
 5. factory_data_trim.py: When using the custom factory data option, this script
    removes the dummy factory data which is required to be able to successfully
    compile the application.
 6. `oad`\_and_factory_data_merge_tool.py: Merges the factory data hex, Matter
-   application without factory data and `BIM`/MCUBoot image to generate a
-   functional hex that can be programmed onto the device.
+   application without factory data and MCUBoot image to generate a functional
+   hex that can be programmed onto the device.
 
 ## Flash memory layout
 
-![Memory Layout 1](images/cc13x2_memmap.png)
-
 ![Memory Layout 2](images/cc13x4_memmap.png)
 
 ## How to use
 
 Out of box factory data location is configured to be on second last page of
-flash. For CC13x2, the starting address is `0xAC000`. For CC13x4, the starting
-address is `0xFE800`. This can be configured in the linker file.
+flash. For CC13x4, the starting address is `0xFE800`. This can be configured in
+the linker file.
 
 To configure:
 
 1. Linker file: Set the start address for factory data in the linker file being
    used by the application
 
 ```
-FLASH_FACTORY_DATA (R)  : ORIGIN = 0x000ac000, LENGTH = 0x00000900
+FLASH_FACTORY_DATA (R)  : ORIGIN = 0x000fe800, LENGTH = 0x00000900
 ```
 
 ```
 /* Define base address for the DAC arrays and struct */
     PROVIDE (_factory_data_base_address =
-        DEFINED(_factory_data_base_address) ? _factory_data_base_address : 0xAC000);
+        DEFINED(_factory_data_base_address) ? _factory_data_base_address : 0xFE800);
 ```
 
 2. create_factory_data.py: Set the address of the start of the factory data
@@ -78,7 +75,7 @@ FLASH_FACTORY_DATA (R)  : ORIGIN = 0x000ac000, LENGTH = 0x00000900
 ```
     # there are 17 elements, each element will need 8 bytes in the struct
     # 4 for length of the element, and 4 for the pointer to the element
-    # factory data starts at 0xAC000 or 0xFE800, so the elements will
+    # factory data starts at 0xFE800, so the elements will
     # start 136 bytes after the start address
     factory_data_dict = json.load(args.factory_data_json_file[0])
     factory_data_schema = json.load(args.factory_data_schema[0])
@@ -88,23 +85,16 @@ FLASH_FACTORY_DATA (R)  : ORIGIN = 0x000ac000, LENGTH = 0x00000900
 
     struct_idx = 0
     values_idx = 0
-    if device_family == 'cc13x2_26x2':
-        value_address = 0xAC088
-    else:
-        value_address = 0xFE888
+    value_address = 0xFE888
 ```
 
 ```
-    if device_family == 'cc13x2_26x2':
-        subprocess.call(['objcopy', 'temp.bin','--input-target','binary','--output-target', 'ihex', args.factory_data_hex_file, '--change-addresses=0xac000'])
-    else:
-        subprocess.call(['objcopy', 'temp.bin','--input-target','binary','--output-target', 'ihex', args.factory_data_hex_file, '--change-addresses=0xfe800'])
+   subprocess.call(['objcopy', 'temp.bin','--input-target','binary','--output-target', 'ihex', args.factory_data_hex_file, '--change-addresses=0xfe800'])
 ```
 
 3. In the example's args.gni file, set 'custom_factory_data' to true
 
-It is recommended to keep a dedicated page (2 pages for CC13x4) for factory
-data.
+It is recommended to keep 2 dedicated pages for CC13x4 for factory data.
 
 ### Formatting certs and keys for JSON file
 
@@ -121,7 +111,6 @@ being copied into the JSON file.
 The example application can be built using the instructions in the example's
 README. The factory data from the JSON file will be formatted into a hex file
 that will then be merged into the final executable. The final executable will be
-named _{example-application}-`bim`.hex_ for CC13x2 and
-_{example-application}-mcuboot.hex_ for CC13x4, and the factory data that was
-inputted into the JSON file will be named
+named _{example-application}-mcuboot.hex_ for CC13x4, and the factory data that
+was inputted into the JSON file will be named
 _{example-application}-factory-data.hex_.

docs/guides/ti/images/cc13x2_memmap.png

@@ -48,8 +48,8 @@ In the TI example applications the Bluetooth Low Energy protocol is used to
 provision the Thread protocol to enable Matter communication. Then Thread is
 used for IP communication with other Matter devices.
 
-The TI applications leverage the Bluetooth Low Energy stack on the CC13X2 and
-CC26X2 families. This BLE software is distributed in binary form within the TI
+The TI applications leverage the Bluetooth Low Energy stack on the CC13XX and
+CC26XX families. This BLE software is distributed in binary form within the TI
 SimpleLink SDK. The BLE stack leverages code that is present in the device ROM
 for certain common BLE operations.
 
@@ -103,9 +103,9 @@ handled by the platform implementation files.
 Sample Matter applications are provided for the TI platform. These can be used
 as reference for your own application.
 
--   [lock-app](../../../examples/lock-app/cc13x2x7_26x2x7/README.md)
--   [pump-app](../../../examples/pump-app/cc13x2x7_26x2x7/README.md)
--   [pump-controller-app](../../../examples/pump-controller-app/cc13x2x7_26x2x7/README.md)
+-   [lock-app](../../../examples/lock-app/cc13x4_26x4/README.md)
+-   [pump-app](../../../examples/pump-app/cc13x4_26x4/README.md)
+-   [pump-controller-app](../../../examples/pump-controller-app/cc13x4_26x4/README.md)
 
 <hr>