-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[TI] Update Example Applications and TI Documentation (#34060)
* Update TI Applications with correct OTA startup handling * Update Linker command files and NV regions * Add test event trigger delegate * Fix pairing failure in TI applications * Update TI Matter documentation * Update Openthread OT-TI commit * Apply restyled updates * Update Image spelling * Apply restyled * Update workflow to perform recursive clone * Update nvocmp.c to fix formatting issue --------- Co-authored-by: Andrei Litvin <[email protected]>
- Loading branch information
Showing
75 changed files
with
6,466 additions
and
339 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
# 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/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. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
# Configure The Board Files with SysConfig | ||
|
||
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/reserve-peripheral-panel.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/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/hardware_view.png" width=30%> | ||
</div> |
4 changes: 2 additions & 2 deletions
4
docs/guides/ti/enabling_icd_on_ti_devices.md → ...users-guide/enabling_icd_on_ti_devices.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.