Update TI Matter documentation

Author: adabreuti

docs/guides/images/matter_ti_overview_wifi.png

@@ -50,7 +50,7 @@ The GPIO pin values for SPI will need to be adjusted based on your design.
 4. Select _Board_ as _None_ and _Device_ as _`CC2674P10RGZ`_, Unselect
    _`Lock PinMux`_, and click _Confirm_.
 5. To fix errors, make the following module changes:
-    - _RF Design_ and _RF Stacks -> BLE -> Radio_: click on _accepting the
+    - _RF Design_ and _RF Stacks -> Bluetooth LE -> Radio_: click on _accepting the
       current value_, which should be _`LP_CC2674P10_RGZ`_ in the drop down menu
       for _Based On RF Design_
     - _TI DEVICES -> Device Configuration_: Clear

docs/guides/ti/matter_cc2674_migration.md docs/guides/ti/matter-migration-guide/matter_cc2674_migration.md

@@ -0,0 +1,59 @@
+# Get started with SysConfig
+
+System Configuration Tool (SysConfig) is a graphical interface for
+configuring your project. Configuration files, C source files and header
+files are generated based on the parameters configured in the SysConfig
+dashboard.
+
+SysConfig should be used as a standalone tool for script-based builds (such as for Matter).
+
+The document will help for getting started in tailoring the syscfg file to your application needs.
+
+## Using Stand-alone SysConfig
+
+You can find the standalone SysConfig tool on the [SysConfig Standalone
+Installer Download Page](https://www.ti.com/tool/SYSCONFIG).
+
+The location of the Matter syscfg file is located here: `/examples/<name>/cc13x4_26x4/chip.syscfg`
+For example, on the github web: https://github.com/project-chip/connectedhomeip/blob/master/examples/lock-app/cc13x4_26x4/chip.syscfg
+The local file in your cloned repository should be used.
+
+This file is used by Matter build scripts, when it invokes SysConfig CLI.
+In order to edit the file for your custom application configurations, you'll need to open the file with the SysConfig GUI.
+Before doing so, you should add the following line above the `/* Modules */` comment:
+
+```
+// @cliArgs --product <path to SDK>/.metadata/product.json --board /ti/boards/LP_EM_CC1354P10_6 --rtos freertos
+```
+
+As an example, after adding the necessary `<path to SDK>`, it would look like:
+
+```
+// @cliArgs --product /home/Documents/repos/connectedhomeip/third_party/ti_simplelink_sdk/repo_cc13xx_cc26xx/.metadata/product.json --board /ti/boards/LP_EM_CC1354P10_6 --rtos freertos
+```
+
+If the file is not found, then you may need to first initialize the submodules:
+
+```
+git submodule update --init
+```
+
+Now you can open the file in SysConfig GUI.
+Once you are done, remove the `@cliArgs` line then save the file. Now the Matter build scripts will use the updated .syscfg file.
+
+## Viewing SysConfig Output
+
+To preview the code to be generated reference the `Generated Files` image, the button at the top of
+the `Configuration` pane you will find a list of Generated Files. After
+selecting a file you will be able, in real-time, to identify how the
+changes in the GUI affect the generated files. This will help you review
+the relationship between the GUI and the code.
+
+<div style="text-align: center;">
+  <img src="images/syscfg_generated_files_ble.png" alt="Generated Files" width=30%>
+  <div class="caption">Generated Files</div>
+</div>
+
+Whenever you re-build the project, SysConfig will re-generate the files.
+Because of this, any changes made directly in the generated files will
+be overwritten.

docs/guides/ti/matter-syscfg/getting-started.md

@@ -0,0 +1,75 @@
+# Configure The Board Files with SysConfig
+
+## Table of Contents
+
+* [Reserve Peripherals](#Reserve-Peripherals)
+* [Hardware View](#Hardware-View)
+
+The board view shows you what pins are available on your board, and what
+peripherals are assigned to what pins. Hover over each pin for more
+information.
+
+<div style="text-align: center;">
+  <img src="./images/board_view.png" width=20%>
+</div>
+
+Enabled and configured peripherals are displayed with green symbols.
+To add a new peripheral, press the plus sign next to the peripheral
+type. The \"Show generated files\" tab lets you see the files generated
+based on SysConfig. Generated files are dynamically updated every time
+you make a change in SysConfig. When you build your project, the
+generated files are exported into the output folder of your project.
+
+<div style="text-align: center;">
+  <img src="images/show_generated_files_tab.png">
+</div>
+
+## Reserve Peripherals 
+
+Certain use cases may require preventing SysConfig from generating the
+configuration of specific peripherals.
+
+Examples of use cases requiring to reserve peripherals are:
+
+-   dynamic re-configuration of a peripheral
+-   leveraging the Sensor Controller (on devices enabling it)
+-   already handling certain peripherals configuration
+-   with hardware constraints preventing to use certain peripherals
+    (typically GPIOs)
+-   peripherals reserved for future use
+
+Below are the steps required to utilize the Reserve Peripherals feature.
+
+1.  Open the `.syscfg` file using the SysConfig GUI
+
+2.  Open the panel \"Reserve Peripherals\"
+
+    <div style="text-align: center;">
+      <img src="images/syscfg-reserve-peripheral-pannel.png" width=30%>
+    </div>
+
+3.  Reserve the resources
+
+    Reserve a peripheral using SysConfig. This image shows how
+    to reserve DIO 15
+
+    <div style="text-align: center;">
+      <img src="images/syscfg-reserve-gpio.png" width=30%>
+    </div>
+
+
+SysConfig ensures no resource conflict occurs. In case no solution can
+be found, an error is raised.
+
+## Hardware View
+
+The Hardware view may be used to add software modules for supporting
+hardware resources on EVMs or LaunchPads. The same capability could be
+done in the Software view by adding a Hardware. However the Hardware
+view provides a hardware-first perspective to show which software could
+be used with hardware resources.
+
+Sysconfig Hardware View:
+<div style="text-align: center;">
+  <img src="images/syscfg_hardware_view.png" width=30%>
+</div>

docs/guides/ti/matter-syscfg/images/board_view.png

@@ -1,12 +1,12 @@
-# Configuring Intermittently Connected Devices on TI CC13x4 Platforms
+# Configuring Intermittently Connected Devices on TI SimpleLink CC13x4_CC26x4 Platforms
 
 ## Overview
 
 Intermittently Connected Devices are devices in a network that do not always
 need to be active. Matter has defined a cluster that helps capture this
 behavior; this configuration is ideal for devices that need to operate with low
 power consumption or do not have a need to always be on the network. Matter
-examples on the TI CC13x4 platform can be configured to act as ICDs.
+examples on the TI CC13x4_CC26x4 platform can be configured to act as ICDs.
 
 ## Platform Code Changes
 

docs/guides/ti/matter-syscfg/images/show_generated_files_tab.png

@@ -16,8 +16,7 @@ programming infrastructure for their Matter devices.
 TI Matter examples allow the use of factory data in the following two ways:
 
 -   **Example Out of Box Factory Data** : Use TI example DAC values to get
-    started. This is intended to be used when just starting with Matter or
-    during development until customer or product specific data is not required.
+    started. This is intended to be used during development.
 -   **Custom factory data** : Allows users to configure custom factory data via
     a JSON file. The custom values are then processed by a script provided by TI
     and merged with the Matter application to create a binary that can be
@@ -50,8 +49,8 @@ Each element is described in more detail below:
 
 ## How to use
 
-Out of box factory data location is configured to be on second last page of
-flash. For CC13x4, the starting address is `0xFE800`. This can be configured in
+Out of box factory data location is configured to be on second to last page of
+flash. For CC13x4_CC26x4, the starting address is `0xFE800`. This can be configured in
 the linker file.
 
 To configure:
@@ -94,7 +93,7 @@ FLASH_FACTORY_DATA (R)  : ORIGIN = 0x000fe800, LENGTH = 0x00000900
 
 3. In the example's args.gni file, set 'custom_factory_data' to true
 
-It is recommended to keep 2 dedicated pages for CC13x4 for factory data.
+It is recommended to keep 2 dedicated pages for CC13x4_CC26x4 for factory data.
 
 ### Formatting certs and keys for JSON file
 

docs/guides/ti/matter-syscfg/images/syscfg-reserve-gpio.png

@@ -0,0 +1,171 @@
+# Texas Instruments platform overview
+
+The Texas Instruments Matter platform is based on the TI SimpleLink™ SDK.
+
+The following diagram is a simplified representation of a Matter application
+which is built on the TI Platform.
+
+<div style="text-align: center;">
+  <img src="./.././../images/matter_ti_overview_simplified.png" width=30%>
+</div>
+
+## Texas Instruments SimpleLink SDK
+
+This Texas Instruments Matter GitHub repository contains the software
+development components and tools that enable engineers to develop Matter based
+products. This repository is the starting point for Matter development on all
+SimpleLink Thread and Wi-Fi wireless microcontrollers (MCUs).
+
+The SimpleLink MCU portfolio offers a single development environment that
+delivers flexible hardware, software, and tool options for customers developing
+wired and wireless applications. With 100 percent code reuse across host MCUs,
+Wi-Fi™, Bluetooth Low Energy, 2.4GHz, Sub-1GHz devices and more, choose the MCU
+or connectivity standard that fits your design. A one-time investment with the
+SimpleLink software development kit allows you to reuse often, opening the door
+to create unlimited applications. For more information, visit
+www.ti.com/simplelink.
+
+<hr>
+
+## Bluetooth LE and Thread stacks
+
+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 CC13XX and
+CC26XX families. This Bluetooth LE software is distributed in binary form within
+the TI SimpleLink SDK. The Bluetooth LE stack leverages code that is present in
+the device ROM for certain common Bluetooth LE operations.
+
+These applications leverage the OpenThread stack available within the Matter
+repository for Thread communication. Platform support source is built from the
+SimpleLink SDK.
+
+These connection protocols can be run concurrently by using the Texas
+Instruments Dynamic Multi-protocol Manager.
+
+<hr>
+
+## LwIP stack
+
+The Lightweight IP stack interfaces with the OpenThread stack to offer standard
+IP connectivity protocols that OpenThread does not natively support. This offers
+a standard socket based interface to the Matter platform.
+
+<hr>
+
+## MbedTLS
+
+The MbedTLS library is used by OpenThread and Matter for a wide variety of
+protocols. This ranges from basic AES and SHA to cryptographic protocols like
+ECDSA and ECDH.
+
+The MbedTLS library is hardware accelerated using the TI SimpleLink SDK drivers.
+This is achieved through the usage of `_ALT` defines in the MbedTLS
+configuration file.
+
+<hr>
+
+## Matter Stack to TI Platform Interface
+
+Matter Stack interacts with LwIP, OpenThread, and the TI-BLE stack to achieve
+the protocol and application functionality. A Bluetooth LE profile is registered
+with the TI-BLE stack to enable provisioning and configuration. Once the device
+is provisioned Matter will configure the OpenThread interface to connect to an
+existing Thread network or to start its own network. From there the Matter IP
+messages are sent to the LwIP stack to be routed to the OpenThread stack for
+transmission. Matter Impl (Implementation) layer acts as an interface between
+Matter stack and the TI platform components such as BLE stack, OpenThread,
+FreeRTOS. It also supports components such as connectivity manager that provides
+the implementation for functionality required by Matter stack. Overall,
+applications generally only need to interface with the Cluster Library from
+Matter. The transport of messages and configuration of the device is all handled
+by the platform implementation files.
+
+<hr>
+
+## Matter Development Resources
+
+Below are several resources available for Matter development:
+
+-   [Matter Protocol Overview](https://handbook.buildwithmatter.com/howitworks/roles/)
+-   [Matter Build Guide](../../BUILDING.md)
+-   [Matter over Thread Getting Started](https://dev.ti.com/tirex/explore/node?node=A__AciOYyNq9gli.nsvJzBtQg__com.ti.SIMPLELINK_ACADEMY_CC13XX_CC26XX_SDK__AfkT0vQ__LATEST)
+-   [TI Matter over Wi-Fi Getting Started](https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1122413/faq-cc3235sf-matter----getting-started-guide)
+-   [TI Matter Application Development](https://dev.ti.com/tirex/explore/node?node=A__AXNOPYikmtBCHJ-L6eRivA__com.ti.SIMPLELINK_ACADEMY_CC13XX_CC26XX_SDK__AfkT0vQ__LATEST)
+-   [TI Matter OTA Guide](https://dev.ti.com/tirex/explore/node?node=A__AYTiKtu5heqgH4KPFa.6RQ__com.ti.SIMPLELINK_ACADEMY_CC13XX_CC26XX_SDK__AfkT0vQ__LATEST)
+
+<hr>
+
+## Matter Example Applications
+
+Sample Matter applications are provided for the TI platform. These can be used
+as reference for your own application.
+
+-   [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)
+-   [lighting-app](../../../../examples/lighting-app/cc13x4_26x4/README.md)
+<hr>
+
+### Build system
+
+The TI platform uses GN to generate ninja build scripts. Build files have
+already been written to build and link the TI specific code within the
+SimpleLink SDK.
+
+<hr>
+
+## CC2674 Migration
+
+For instructions on how to migrate the CC1354P10-6 examples to either the
+CC2674P10 or the CC2674R10, please refer to the guide linked below.
+
+-   [TI CC2674 Migration Guide](../matter-migration-guide/matter_cc2674_migration.md)
+
+<hr>
+
+## Factory Data Programming Tool
+
+For instructions on how to program custom factory data on TI devices, please
+refer to the guide linked below.
+
+-   [TI Factory Data User Guide](./ti_factory_data_user_guide.md)
+
+<hr>
+
+## Intermittently Connected Devices
+
+For instructions on how to use the Matter ICD feature on TI devices, please
+refer to the guide linked below.
+
+-   [Enabling ICD On TI Devices](./enabling_icd_on_ti_devices.md)
+
+<hr>
+
+## Matter OpenThread Library Configuration
+
+For instructions on how to configure the OpenThread build configuration for a
+Matter application, please refer to the guide linked below.
+
+-   [OpenThread Library Configuration](./ti_openthread_library_usage.md)
+
+<hr>
+
+## TI Matter Product Certification
+
+For instructions on how to certify both Software and Hardware Matter components,
+please refer to the guide linked below.
+
+-   [TI Matter Product Certification](./ti_matter_product_certification.md)
+
+<hr>
+
+### TI Support
+
+For technical support, please consider creating a post on TI's [E2E forum][e2e].
+Additionally, we welcome any feedback.
+
+[e2e]: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread
+[matter_gh]: https://github.com/project-chip/connectedhomeip