### Setup Repository and Install Dependencies

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-automation/doc/quickstart.rst

Clones the OpenThread repository, navigates to the harness automation directory, and installs required Python libraries using pip.

```bash
git clone https://github.com/openthread/openthread.git
cd openthread/tools/harness-automation
pip install -r requirements.txt
```

--------------------------------

### Build and Install wpantund

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/INSTALL.md

Compiles the wpantund project after configuration and installs the binaries and associated files to the system. Supports parallel building with the -j flag.

```bash
# To speed up build, use -jN where N is number of cores, e.g., make -j4
# For debugging, add --enable-debug to configure: ./configure --sysconfdir=/etc --enable-debug

sudo make install
```

--------------------------------

### OpenThread CoAP CLI Quick Start Example

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_COAP.md

Demonstrates forming a network and performing basic CoAP operations like starting the server, registering a resource, and performing GET and PUT requests between two nodes.

```bash
> coap start
Done
> coap resource test-resource
Done
```

```bash
> coap start
Done
> coap get fdde:ad00:beef:0:d395:daee:a75:3964 test-resource
Done
coap response from [fdde:ad00:beef:0:2780:9423:166c:1aac] with payload: 30
> coap put fdde:ad00:beef:0:2780:9423:166c:1aac test-resource con payload
Done
coap response from [fdde:ad00:beef:0:2780:9423:166c:1aac]
```

```bash
coap request from [fdde:ad00:beef:0:b3:e3f6:2dcc:4b79] GET
coap response sent
coap request from [fdde:ad00:beef:0:b3:e3f6:2dcc:4b79] PUT with payload: 7061796c6f6164
coap response sent
```

--------------------------------

### Starting AP Application Example

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/bluetooth/example_host/bt_host_esl_ap/readme/readme.md

Example command to start the AP application on Windows, specifying a COM port for an NCP connection. Assumes Python is installed and in the PATH.

```bash
python .\app.py COM4
```

--------------------------------

### Setup Configuration File

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-automation/doc/quickstart.rst

Copies the sample settings file and renames it for customization.

```bash
cp autothreadharness/settings_sample.py autothreadharness/settings.py
```

--------------------------------

### Install Dependencies on Arch Linux

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/Simple-web-server/repo/README.md

Installs the Boost libraries required for compiling and running the examples on Arch Linux.

```shell
sudo pacman -S boost
```

--------------------------------

### Start wpantund Daemon

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/INSTALL.md

Launches the wpantund daemon to connect to a Network Co-Processor (NCP). Requires specifying the serial port and optionally the WPAN interface name.

```bash
# Connect to NCP on /dev/ttyUSB0
sudo /usr/local/sbin/wpantund -o NCPSocketName /dev/ttyUSB0

# Connect to wpan0 on /dev/ttyUSB0 and wpan1 on /dev/ttyUSB1
sudo /usr/local/sbin/wpantund -o NCPSocketName /dev/ttyUSB0 -o WPANInterfaceName wpan0
sudo /usr/local/sbin/wpantund -o NCPSocketName /dev/ttyUSB1 -o WPANInterfaceName wpan1
```

--------------------------------

### CMake Packaging Example

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/cJSON/repo/README.md

Example of building and installing cJSON for distribution packaging, setting specific CMake options and using DESTDIR for staging.

```Shell
mkdir build
cd build
cmake .. -DENABLE_CJSON_UTILS=On -DENABLE_CJSON_TEST=Off -DCMAKE_INSTALL_PREFIX=/usr
make
make DESTDIR=$pkgdir install
```

--------------------------------

### Install and Setup wpantund

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/README.md

These commands demonstrate the installation and setup process for wpantund, including bootstrapping and configuring the daemon. It assumes an existing OpenThread Border Router (OTBR) agent setup.

```shell
cd protocol/openthread/
sudo INFRA_IF_NAME=eth0 ./script/bootstrap_wpantund
sudo INFRA_IF_NAME=eth0 ./script/setup_wpantund
```

--------------------------------

### Get Help Information

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-automation/doc/quickstart.rst

Displays help information and available command-line arguments for the harness script.

```bash
./start.sh -h
```

```windows-cmd
start.bat -h
```

--------------------------------

### Bootstrap and Configure wpantund Build

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/INSTALL.md

Prepares the wpantund source code for building by running the bootstrap script and then configuring the build process. Requires libtool, autoconf, and autoconf-archive.

```bash
git checkout origin/master
sudo apt-get install libtool autoconf autoconf-archive
./bootstrap.sh

./configure --sysconfdir=/etc
make
```

--------------------------------

### wpanctl Utility Commands

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/INSTALL.md

Demonstrates common commands for interacting with the wpantund daemon using the wpanctl utility. Includes leaving a network, setting properties, forming a network, and checking status.

```APIDOC
wpanctl:
  Description: Command-line utility to control the wpantund daemon.
  Usage: sudo wpanctl [options] [command]

  Commands:
    leave
      Description: Leaves the current WPAN.
      Example: wpanctl:wpan0> leave

    setprop <property> <value>
      Description: Sets a property for the current interface.
      Parameters:
        property: The name of the property to set (e.g., NetworkKey).
        value: The value for the property. Use --data for raw byte strings.
      Example: wpanctl:wpan0> setprop NetworkKey --data 000102030405060708090a0b0c0d0e0f

    form <network_name> [-c <channel>]
      Description: Forms a new WPAN network.
      Parameters:
        network_name: The name of the network to form.
        -c channel: The channel to use (optional).
      Example: wpanctl:wpan0> form "MyCoolNetwork" -c 26

    permit-join <time> <port>
      Description: Allows new devices to join the network for a specified time.
      Parameters:
        time: Duration in seconds to permit joining.
        port: Commissioning port (TCP/UDP).
      Example: wpanctl:wpan0> permit-join 3600 22

    status
      Description: Displays the current status of the WPAN interface.
      Example: wpanctl:wpan0> status
      Returns:
        AssociationState: Current state (e.g., "joined").
        NetworkName: Name of the current network.
        XPanId: Extended PAN ID.
        PanId: PAN ID.
        Channel: Current channel.
        Prefix: Network prefix.
        NCPVersion: Version information of the NCP.
        HWAddr: Hardware address of the interface.
```

--------------------------------

### Install wpantund Dependencies on Ubuntu

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/INSTALL.md

Installs necessary runtime and build-dependent packages for wpantund on Ubuntu using apt-get. Includes essential tools like gcc, g++, dbus, and boost libraries.

```bash
sudo apt-get update

# Install runtine-dependent packages (libreadline is optional)
sudo apt-get install dbus libreadline

# Install build-dependent packages (libreadline-dev is optional)
sudo apt-get install gcc g++ libdbus-1-dev libboost-dev libreadline-dev
```

--------------------------------

### CMake Packaging Example

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/cjson/README.md

An example demonstrating how to build and package cJSON for a Linux distribution using CMake, specifying build options like disabling tests and setting an installation prefix, and using DESTDIR for installation.

```shell
mkdir build
cd build
cmake .. -DENABLE_CJSON_UTILS=On -DENABLE_CJSON_TEST=Off -DCMAKE_INSTALL_PREFIX=/usr
make
make DESTDIR=$pkgdir install
```

--------------------------------

### Bootloader Installation and Flashing

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/btmesh/documentation/example/btmesh_soc_switch/readme_low_power_rtos.md

Guidance on installing bootloaders for Software Example-based projects and proper flashing procedures to avoid overwriting the bootloader.

```APIDOC
Bootloader Management:

1. Bootloader Requirement: Software Example-based projects require a bootloader.
2. Installation Methods:
   - From Launcher: Build and flash bootloader examples from the EXAMPLE PROJECTS & DEMOS tab.
   - Precompiled Demos: Flash precompiled demos which include bootloader and application.

3. Specific Bootloader Flashing:
   - OTA DFU-capable: Flash the **Bluetooth Mesh - SoC Switch** demo.
   - UART DFU-capable: Flash the **Bluetooth Mesh - NCP Empty** demo.
   - Custom Bootloader: Create and flash a custom bootloader project.

4. Application Flashing:
   - Recommended Files: Use *.hex* or *.s37* output files for flashing the application.
   - Avoid: Flashing *.bin* files can overwrite the bootloader.

5. References:
   - [UG103.6: Bootloader Fundamentals](https://www.silabs.com/documents/public/user-guides/ug103-06-fundamentals-bootloading.pdf)
   - [UG489: Silicon Labs Gecko Bootloader User's Guide for GSDK 4.0 and Higher](https://cn.silabs.com/documents/public/user-guides/ug489-gecko-bootloader-user-guide-gsdk-4.pdf)
```

--------------------------------

### C: Unity Test Main Function Setup

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/cJSON/repo/tests/unity/docs/UnityConfigurationGuide.md

Demonstrates a typical main function for a Unity test module. It initializes the Unity test runner with UNITY_BEGIN(), runs individual tests using RUN_TEST(), and concludes the test run with UNITY_END(). This structure is useful for system-wide setup and teardown.

```C
int main(void) {
    UNITY_BEGIN();
    RUN_TEST(test_TheFirst);
    RUN_TEST(test_TheSecond);
    RUN_TEST(test_TheThird);
    return UNITY_END();
}
```

--------------------------------

### Initialize System and Start FreeRTOS Scheduler in C

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/protocol/openthread/sample-apps/ot-ble-dmp/README.md

Demonstrates the main function initialization process, calling `otrInit` to set up the system and `vTaskStartScheduler` to begin the FreeRTOS scheduler. The `sl_ot_rtos_application_init` callback can be used for custom application setup.

```c
int main(int argc, char *argv[]) {
  otrInit(argc, argv);
  vTaskStartScheduler();
  return 0;
}
```

--------------------------------

### Install Bootloader for Bluetooth Mesh Application

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/btmesh/documentation/example/btmesh_soc_nlc_basic_lightness_controller/readme.md

Instructions on how to install a bootloader for Bluetooth Mesh applications. This is crucial as software example projects expect a bootloader to be present. It details flashing precompiled demos or custom bootloader projects.

```text
Note that Software Example-based projects do not include a bootloader. However, they are configured to expect a bootloader to be present on the device. To install a bootloader, from the Launcher perspective's EXAMPLE PROJECTS & DEMOS tab either build and flash one of the bootloader examples or run one of the precompiled demos. Precompiled demos flash a bootloader as well as the application image.

- To flash an OTA DFU-capable bootloader to the device, flash the **Bluetooth Mesh - SoC Switch CTL** demo.
- To flash a UART DFU-capable bootloader to the device, flash the **Bluetooth Mesh - NCP Empty** demo.
- For other bootloader types, create your own bootloader project and flash it to the device before flashing your application.
- When you flash your application image to the device, use the *.hex* or *.s37* output file. Flashing *.bin* files may overwrite (erase) the bootloader.
```

--------------------------------

### Vcpkg Installation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/cjson/README.md

Steps to download, bootstrap, and install cJSON using the vcpkg dependency manager. It also provides guidance on reporting outdated versions or contributing to the cJSON port in vcpkg.

```shell
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh
./vcpkg integrate install
vcpkg install cjson
```

--------------------------------

### Makefile Build and Install (Deprecated)

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/cjson/README.md

Instructions for building cJSON using the Makefile, which compiles static and shared libraries along with a test program. It also details how to install and uninstall the library, with options to customize the installation prefix and destination directory.

```shell
make all
make install
make PREFIX=/usr DESTDIR=temp install
make PREFIX=/usr DESTDIR=temp uninstall
```

--------------------------------

### Launch Testbed on POSIX

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-simulation/README.md

This command launches the testbed simulation environment on the POSIX machine. It uses the `config.yml` file to define the number and type of simulations (OT FTD, OTBR, sniffer) to start, and specifies the network interface for discovery.

```bash
cd tools/harness-simulation/posix
./launch_testbed.py -c config.yml
```

--------------------------------

### Install Frontend Files (CMake)

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/src/web/web-service/frontend/CMakeLists.txt

Uses CMake's `install` command to copy frontend files, including HTML, JavaScript, and CSS assets, to their designated installation directories. This ensures the web frontend is correctly deployed.

```cmake
install(FILES index.html join.dialog.html
    DESTINATION ${OTBR_WEB_DATADIR}/frontend)

install(DIRECTORY res
    DESTINATION ${OTBR_WEB_DATADIR}/frontend)

install(FILES ${NPM_JS_DEPENDENCIES}
    DESTINATION ${OTBR_WEB_DATADIR}/frontend/res/js)

install(FILES ${NPM_CSS_DEPENDENCIES}
    DESTINATION ${OTBR_WEB_DATADIR}/frontend/res/css)
```

--------------------------------

### Enable Real-time Audio Player

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/bluetooth/example_host/bt_host_voice/scripts/win/README.md

Instructions for starting the VoBLE application and the SoX player for real-time audio playback. These are executed via batch scripts.

```batch
1. Start VoBLE application:
   run_voble_app.sh

2. Start SoX player application:
   run_voble_player.sh
```

--------------------------------

### Small Protothread Example

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/third_party/pt/doc/pt-doc.txt

Illustrates basic protothread programming, initialization, and scheduling. This example shows two protothreads toggling flags to wait for each other.

```c
// Code for example-small.c would go here, demonstrating basic protothread usage.
```

--------------------------------

### Bluetooth Mesh Event Documentation Location

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/btmesh/documentation/example/btmesh_soc_empty/readme_rtos.md

Detailed information on all Bluetooth Mesh events, including their parameters and behavior, can be found in the HTML documentation provided within the Simplicity Studio installation directory. This documentation is crucial for understanding and implementing event handlers.

```APIDOC
Bluetooth Mesh Events Documentation:

Location: <Simplicity-Studio-installation-directory>/offline/com.silabs.sdk.stack.super_4.0.1/app/btmesh/documentation/<SDK-installation-location>/app/btmesh/documentation/

Description:
  This directory contains comprehensive HTML documentation for all Bluetooth Mesh events. It details the structure of `sl_btmesh_msg_t` and the specific message IDs (e.g., `SL_BT_MESH_MODEL_MSG_RECEIVED`) that can be used in the `sl_btmesh_on_event()` switch-case statement. Developers should consult this documentation to implement appropriate responses to stack-generated events.
```

--------------------------------

### Vcpkg Installation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/cJSON/repo/README.md

Instructions for installing cJSON using the Vcpkg dependency manager. This involves cloning Vcpkg, bootstrapping, integrating, and then installing the cjson package.

```Shell
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh
./vcpkg integrate install
vcpkg install cjson
```

--------------------------------

### Build Host Provisioner Example

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/btmesh/example_host/btmesh_host_provisioner/README.txt

Instructions for building the btmesh_host_provisioner sample application using make. Supports optional build parameters for UI mode, remote provisioning, and certificate-based provisioning.

```make
make
```

```make
make UI=1
```

```make
make RPR=1
```

```make
make CBP=1
```

--------------------------------

### Bluetooth NCP Setup

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/bluetooth/example/bt_soc_throughput/readme.md

Instructions for setting up the Bluetooth NCP firmware on an EFR32 device. This involves flashing the Bluetooth - NCP example and installing the LE Power Control component.

```C
/*
 * Example setup for Bluetooth NCP firmware.
 * Requires flashing the 'Bluetooth - NCP' example.
 * Install 'LE Power Control' component via Software Components tab.
 */

// No specific code provided, but describes the setup process.
```

--------------------------------

### CMake Build for Example App and makefsdata

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/lwip/lwip-contrib/ports/unix/example_app/CMakeLists.txt

Configures the build process for the `example_app` and `makefsdata` executables using CMake. It sets up project details, includes necessary LWIP modules, defines compile options and definitions, and links required libraries for the application and utility.

```cmake
cmake_minimum_required(VERSION 3.8)

project(example_app C)

set (CMAKE_EXPORT_COMPILE_COMMANDS ON)

set(LWIP_CONTRIB_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../../..)
set(LWIP_DIR         ${CMAKE_CURRENT_SOURCE_DIR}/../../../../lwip)

include(${LWIP_CONTRIB_DIR}/ports/CMakeCommon.cmake)

set (LWIP_DEFINITIONS -DLWIP_DEBUG)
set (LWIP_INCLUDE_DIRS
    "${LWIP_DIR}/src/include"
    "${LWIP_CONTRIB_DIR}/"
    "${LWIP_CONTRIB_DIR}/ports/unix/port/include"
    "${LWIP_CONTRIB_DIR}/examples/example_app"
)

include(${LWIP_DIR}/src/Filelists.cmake)
include(${LWIP_CONTRIB_DIR}/Filelists.cmake)
include(${LWIP_CONTRIB_DIR}/ports/unix/Filelists.cmake)

add_executable(example_app ${LWIP_CONTRIB_DIR}/examples/example_app/test.c default_netif.c)
target_include_directories(example_app PRIVATE ${LWIP_INCLUDE_DIRS})
target_compile_options(example_app PRIVATE ${LWIP_COMPILER_FLAGS})
target_compile_definitions(example_app PRIVATE ${LWIP_DEFINITIONS} ${LWIP_MBEDTLS_DEFINITIONS})
target_link_libraries(example_app ${LWIP_SANITIZER_LIBS} lwipcontribexamples lwipcontribapps lwipcontribaddons lwipallapps lwipcontribportunix lwipcore)

add_executable(makefsdata ${lwipmakefsdata_SRCS})
target_compile_options(makefsdata PRIVATE ${LWIP_COMPILER_FLAGS})
target_include_directories(makefsdata PRIVATE ${LWIP_INCLUDE_DIRS})
target_link_libraries(makefsdata ${LWIP_SANITIZER_LIBS})
```

--------------------------------

### Run HTTPS Examples

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/Simple-web-server/repo/README.md

Executes the compiled HTTPS server and client examples. Requires server.key and server.crt files to be present.

```shell
./build/https_examples
```

--------------------------------

### Clone and Setup Dependencies

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/protocol/openthread/embedded-otbr/README.md

Clones required repositories (OpenThread, Simplicity SDK, WiseConnect) and sets up environment variables and symbolic links for the project. Ensure correct paths and versions are used.

```bash
git clone git@github.com:openthread/openthread.git <openthread-dir>
checkout @ 67717618b

git clone git@github.com:SiliconLabs/simplicity_sdk.git <sisdk-dir>
checkout @ 36e12f019 (tag: v2024.6.2)

git clone git@github.com:SiliconLabs/wiseconnect.git <wiseconnect-dir>
checkout @ b5d6422f3 (tag: v3.3.2)

export SISDK_PATH=<sisdk-dir>
export PATH=$PATH:<path to ARM gcc-12.2.1/bin containing arm-none-eabi-gcc>
export COMMANDER=<path to commander binary>

ln -s <openthread-dir> openthread
ln -s <sisdk-dir> simplicity_sdk
ln -s <wiseconnect-dir> wiseconnect
```

--------------------------------

### Run HTTP Examples

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/Simple-web-server/repo/README.md

Executes the compiled HTTP server and client examples. Users can then access the server via a web browser.

```shell
./build/http_examples
```

--------------------------------

### Example JSON Structure

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/cjson/README.md

An example of a JSON object structure that can be parsed or generated using the cJSON library.

```json
{
    "name": "Awesome 4K",
    "resolutions": [
        {
            "width": 1280,
            "height": 720
        },
        {
            "width": 1920,
            "height": 1080
        },
        {
            "width": 3840,
            "height": 2160
        }
    ]
}
```

--------------------------------

### Example JSON Structure

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/cJSON/repo/README.md

An example of a JSON object structure that can be parsed or generated using the cJSON library.

```json
{
    "name": "Awesome 4K",
    "resolutions": [
        {
            "width": 1280,
            "height": 720
        },
        {
            "width": 1920,
            "height": 1080
        },
        {
            "width": 3840,
            "height": 2160
        }
    ]
}
```

--------------------------------

### Install Project Dependencies

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/tcat_ble_client/README.md

Installs all project dependencies using Poetry. This command should be run from the project directory and sets up a virtual environment.

```bash
poetry install
```

--------------------------------

### Simplicity SDK LWIP CMake Setup

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/lwip/lwip-contrib/ports/win32/example_app/CMakeLists.txt

Configures a C project using CMake, integrating the LWIP network stack. It sets up the main executable 'example_app' and a utility 'makefsdata', defining include paths, compile options, and linking necessary LWIP libraries.

```cmake
cmake_minimum_required(VERSION 3.8)

project(example_app C)

set (CMAKE_EXPORT_COMPILE_COMMANDS ON)

set(LWIP_CONTRIB_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../../..)
set(LWIP_DIR         ${CMAKE_CURRENT_SOURCE_DIR}/../../../../lwip)

include(${LWIP_CONTRIB_DIR}/ports/CMakeCommon.cmake)

set (LWIP_DEFINITIONS -DLWIP_DEBUG)
set (LWIP_INCLUDE_DIRS
    "${LWIP_DIR}/src/include"
    "${LWIP_CONTRIB_DIR}/"
    "${LWIP_CONTRIB_DIR}/ports/win32/include"
    "${LWIP_CONTRIB_DIR}/examples/example_app"
)

include(${LWIP_DIR}/src/Filelists.cmake)
include(${LWIP_CONTRIB_DIR}/Filelists.cmake)
include(${LWIP_CONTRIB_DIR}/ports/win32/Filelists.cmake)

add_executable(example_app ${LWIP_CONTRIB_DIR}/examples/example_app/test.c default_netif.c)
target_include_directories(example_app PRIVATE ${LWIP_INCLUDE_DIRS})
target_compile_options(example_app PRIVATE ${LWIP_COMPILER_FLAGS})
target_compile_definitions(example_app PRIVATE ${LWIP_DEFINITIONS} ${LWIP_MBEDTLS_DEFINITIONS})
target_link_libraries(example_app ${LWIP_SANITIZER_LIBS} lwipcontribexamples lwipcontribapps lwipcontribaddons lwipallapps lwipcore lwipcontribportwindows)

add_executable(makefsdata ${lwipmakefsdata_SRCS})
target_compile_options(makefsdata PRIVATE ${LWIP_COMPILER_FLAGS})
target_include_directories(makefsdata PRIVATE ${LWIP_INCLUDE_DIRS})
target_link_libraries(makefsdata ${LWIP_SANITIZER_LIBS} lwipcore lwipcontribportwindows)
```

--------------------------------

### Start CoAP Service

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_COAPS.md

Starts the application's CoAP service. Supports optional parameters to control peer certificate checking and connection attempt limits.

```APIDOC
coaps start [check-peer-cert|max-conn-attempts]

  Starts the application coaps service.

  Parameters:
    check-peer-cert: (boolean, optional) Determines if the peer-certificate check is enabled (default: true) or disabled.
    max-conn-attempts: (integer, optional) Sets the maximum number of allowed attempts to connect to the CoAP Secure server (default: 0, meaning no limit).

  Parameter Combinations:
    - No argument: Defaults are used (check-peer-cert=true, max-conn-attempts=0).
    - check-peer-cert=true: Equivalent to no argument.
    - check-peer-cert=false: Sets check-peer-cert=false and max-conn-attempts=0.
    - Specifying a number: Sets check-peer-cert=true and max-conn-attempts to the specified number.

  Returns:
    'Done' upon successful execution.
```

```bash
> coaps start
Done
```

--------------------------------

### Example Application Enablement

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/protocol/z-wave/docs_public/important_changes.md

All example applications are now enabled for all boards, with CLI support defaulting to ensure full feature access, regardless of hardware peripherals like LEDs or buttons.

```APIDOC
Example Application Enablement:

Change:
  - All examples are now enabled for all boards.

Previous Limitation:
  - Some examples required specific hardware (e.g., RGB LED, multiple buttons).

New Behavior:
  - CLI is enabled by default in all example applications.
  - All features can be controlled using the CLI.

Details:
  - Refer to the README file in each application's folder for specific functionality and commands.
```

--------------------------------

### Start CoAPS Server and Resource

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_COAPS.md

Starts the CoAPS server on a node and registers a test resource. This is typically done on the server node before clients attempt to connect.

```bash
> coaps start
Done
> coaps resource test-resource
Done
```

--------------------------------

### Start OpenThread CLI Node 1

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/examples/apps/cli/README.md

Starts the OpenThread CLI Full Thread Device (FTD) process for Node 1. This command launches the simulated device.

```bash
cd <path-to-openthread>/build/simulation/examples/apps/cli
./ot-cli-ftd 1
```

--------------------------------

### VoBLE Configuration Steps

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/bluetooth/example_host/bt_host_voice/scripts/win/README.md

Details the essential configuration steps required before running the VoBLE application. This includes setting audio devices, COM ports, and SoX paths.

```APIDOC
Configuration:
1. Audio Device Priority:
   Ensure the audio device is the first in the playback list (Control Panel->Sound->Playback).
   Alternatively, modify the AUDIODEV variable in config.bat.

2. VOBLE_APP_PARAM COM Port:
   Verify that VOBLE_APP_PARAM variable in config.bat contains the correct COM port.
   Modify if necessary.

3. SoX Path Configuration:
   Confirm the SoX path is correctly set in config.bat via the SOX_APP variable.
```

--------------------------------

### Start OpenThread CLI Node 2

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/examples/apps/cli/README.md

Starts the OpenThread CLI Full Thread Device (FTD) process for Node 2. This command launches the second simulated device.

```bash
cd <path-to-openthread>/build/simulation/examples/apps/cli
./ot-cli-ftd 2
```

--------------------------------

### Start SRP Server Simulation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_SRP.md

Starts an OpenThread simulation node configured as an SRP server and performs initial network setup and SRP server enablement.

```bash
./output/simulation/bin/ot-cli-ftd 1
```

```APIDOC
OpenThread CLI Commands for SRP Server Setup:

- `dataset init new`
  Initializes a new Thread dataset.
  Returns: Done

- `dataset commit active`
  Commits the active dataset.
  Returns: Done

- `ifconfig up`
  Brings the network interface up.
  Returns: Done

- `thread start`
  Starts the Thread stack.
  Returns: Done

- `state`
  Displays the current Thread state.
  Returns: leader

- `ipaddr`
  Displays the IPv6 addresses.
  Returns: List of IPv6 addresses

- `srp server enable`
  Enables the SRP server functionality.
  Returns: Done
```

--------------------------------

### Run All Test Cases

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-automation/doc/quickstart.rst

Executes all available Thread test cases sequentially.

```bash
./start.sh
```

```windows-cmd
start.bat
```

--------------------------------

### Install Windows Harness

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-simulation/README.md

This batch script installs the Thread Test Harness on a Windows machine. It is typically run after copying the `tools/harness-simulation` directory from a POSIX system to the Windows machine.

```batch
harness\install.bat
```

--------------------------------

### Quick Start: Node 1 TCP Initialization and Listen

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_TCP.md

Initializes the TCP CLI module and starts listening for incoming connections on Node 1 using the unspecified IPv6 address.

```bash
> tcp init
> tcp listen :: 30000
```

--------------------------------

### Host Provisioner CLI Commands

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/btmesh/example_host/btmesh_host_provisioner/README.txt

Commands for interacting with the btmesh_host_provisioner application. These commands manage BT Mesh network provisioning, scanning, node listing, information retrieval, removal, key refresh, and factory reset.

```APIDOC
Run Example:
  ./exe/btmesh_host_provisioner.exe -u /dev/ttyS4 --scan
  (On Windows: winpty exe/btmesh_host_provisioner.exe -u COM5)

Usage Modes:
  UI Mode: Start without specific arguments (e.g., ./exe/btmesh_host_provisioner.exe -u COM5). Database is updated during runtime but not preserved across sessions.
  CLI Mode: One command per run. Database is not preserved, but node identifiers remain consistent if nodes are not reset.

CLI Commands:
  --scan
    Description: Scan for unprovisioned beaconing devices.
    Example: ./exe/btmesh_host_provisioner.exe --scan

  --provision <UUID>
    Description: Provision and configure the selected device using its UUID.
    Parameters:
      <UUID>: The unique identifier of the device to provision.
    Example: ./exe/btmesh_host_provisioner.exe --provision 00010203-0405-0607-0809-0a0b0c0d0e0f

  --nodelist
    Description: List all nodes known to the provisioner, present in the device database (DDB).
    Example: ./exe/btmesh_host_provisioner.exe --nodelist

  --nodeinfo <UUID>
    Description: Print Device Configuration Data (DCD) information about the selected device.
    Parameters:
      <UUID>: The unique identifier of the device.
    Example: ./exe/btmesh_host_provisioner.exe --nodeinfo 00010203-0405-0607-0809-0a0b0c0d0e0f

  --remove <UUID>
    Description: Unprovision the selected device from the network.
    Parameters:
      <UUID>: The unique identifier of the device to unprovision.
    Example: ./exe/btmesh_host_provisioner.exe --remove 00010203-0405-0607-0809-0a0b0c0d0e0f

  --key-refresh <timeout>
    Description: Refresh the network key and application keys. Requires a timeout value.
    Parameters:
      <timeout>: The timeout duration for key refresh.
    Example: ./exe/btmesh_host_provisioner.exe --key-refresh 60

  --reset
    Description: Reset the provisioner to its factory state. It is recommended to remove all known devices before resetting.
    Example: ./exe/btmesh_host_provisioner.exe --reset

  --help
    Description: Print a help message about usage and available commands.
    Example: ./exe/btmesh_host_provisioner.exe --help

Connection Options:
  -u <port>
    Description: Connect to an UART serial port. On Windows, use COMx; on POSIX systems, use /dev/ttyX.
    Example: -u /dev/ttyS4

  -t <address>
    Description: Connect via TCP/IP.
    Example: -t 192.168.1.100

Additional Build Parameters (for CLI mode):
  UI=1: Adds UI mode on top of the CLI application.
  RPR=1: Adds remote provisioning support.
  CBP=1: Adds certificate-based provisioning support. If added, UI mode automatically uses CBP. In CLI mode, an extra --cbp parameter is needed for CBP provisioning; otherwise, normal provisioning occurs.
```

--------------------------------

### Install POSIX Harness Simulation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-simulation/README.md

This script installs the necessary components for the Thread Test Harness on a POSIX environment. It requires the OpenThread repository path to be configured correctly in `config.yml` before execution.

```bash
tools/harness-simulation/posix/install.sh
```

--------------------------------

### Start Node 1 (ot-cli-ftd) OpenThread CLI

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/protocol/openthread/sample-apps/ot-cli/README.md

Initializes, configures, and starts an OpenThread Full Thread Device (ot-cli-ftd). This involves generating and committing an active operational dataset, bringing up the IPv6 interface, and starting the Thread protocol. It also verifies the device state and displays assigned IPv6 addresses.

```bash
> dataset init new
Done
> dataset
Active Timestamp: 1
Channel: 13
Channel Mask: 0x07fff800
Ext PAN ID: d63e8e3e495ebbc3
Mesh Local Prefix: fd3d:b50b:f96d:722d::/64
Network Key: dfd34f0f05cad978ec4e32b0413038ff
Network Name: OpenThread-8f28
PAN ID: 0x8f28
PSKc: c23a76e98f1a6483639b1ac1271e2e27
Security Policy: 0, onrc
Done
> dataset commit active
Done
> ifconfig up
Done
> thread start
Done
> state
leader
Done
> ipaddr
fd3d:b50b:f96d:722d:0:ff:fe00:fc00
fd3d:b50b:f96d:722d:0:ff:fe00:c00
fd3d:b50b:f96d:722d:7a73:bff6:9093:9117
fe80:0:0:0:6c41:9001:f3d6:4148
Done
```

--------------------------------

### Build and Clean Application

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/bluetooth/example_host/bt_cs_host/readme.md

Commands to build the host application using make and to clean build artifacts.

```shell
make
make clean
```

--------------------------------

### Release Checklist: Build and Verification

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/wpantund/doc/wpantund-oss-plan.md

Commands for configuring the build environment, compiling the project, and performing final checks on the release artifacts and tags.

```APIDOC
./configure && make distcheck
  Description: Configures the build environment and creates distribution tarballs. This step verifies the build process and generates release artifacts.
  Note: If this command fails, the release process must stop.

git show <VERSION>
  Description: Displays the commit associated with the specified tag and its tag notes. Used to verify tag message formatting.
  Parameters:
    <VERSION>: The release tag version (e.g., v1.0.0).
  Example: git show v1.0.0
```

--------------------------------

### Application Startup

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/rail/documentation/example/rail_soc_simple_trx/readme.md

Shows the application name displayed on startup, indicating the device is ready.

```cli
> Simple TRX
```

--------------------------------

### CMake Build and Install

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/cjson/README.md

Steps to build cJSON using CMake, supporting out-of-tree builds. Includes compilation, installation, and a comprehensive list of CMake options to customize the build process, such as enabling tests, utilities, sanitizers, and shared/static libraries.

```shell
mkdir build
cd build
cmake ..
make
make install
```

```cmake
-DENABLE_CJSON_TEST=On
-DENABLE_CJSON_UTILS=On
-DENABLE_TARGET_EXPORT=On
-DENABLE_CUSTOM_COMPILER_FLAGS=On
-DENABLE_VALGRIND=On
-DENABLE_SANITIZERS=On
-DENABLE_SAFE_STACK
-DBUILD_SHARED_LIBS=On
-DBUILD_SHARED_AND_STATIC_LIBS=On
-DCMAKE_INSTALL_PREFIX=/usr
-DENABLE_LOCALES=On
-DCJSON_OVERRIDE_BUILD_SHARED_LIBS=On
-DENABLE_CJSON_VERSION_SO
```

--------------------------------

### List Available Devices

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/tools/harness-automation/doc/quickstart.rst

Lists the available serial devices that can be used for testing.

```bash
./start.sh -l
```

```windows-cmd
start.bat -l
```

--------------------------------

### Channel Monitor Commands

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README.md

Commands for monitoring the OpenThread channel, including getting current state, starting, and stopping the monitor.

```APIDOC
channel monitor
  Gets current channel monitor state and channel occupancy.
  Requires: OPENTHREAD_CONFIG_CHANNEL_MONITOR_ENABLE.
  Output Example:
    > channel monitor
    channel monitor
    enabled: 1
    interval: 41000
    threshold: -75
    window: 960
    count: 10552
    occupancies:
    ch 11 (0x0cb7)  4.96% busy
    ...
    Done

channel monitor start
  Starts the channel monitor.
  Requires: OPENTHREAD_CONFIG_CHANNEL_MONITOR_ENABLE.
  Example:
    > channel monitor start
    channel monitor start
    Done

channel monitor stop
  Stops the channel monitor.
  Requires: OPENTHREAD_CONFIG_CHANNEL_MONITOR_ENABLE.
  Example:
    > channel monitor stop
    channel monitor stop
    Done
```

--------------------------------

### PSA Crypto API Functions

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/common/example/psa_crypto_kdf/readme.md

Details the core PSA Crypto API functions utilized in the example for managing cryptographic keys and performing key derivation operations. This includes initialization, attribute setting, key import/export, and derivation setup.

```APIDOC
PSA Crypto API Functions:

Key Management:
  psa_crypto_init(): Initializes the PSA Crypto module.
  psa_key_attributes_init(): Initializes key attributes structure.
  psa_set_key_type(attributes, type): Sets the key type.
  psa_set_key_bits(attributes, bits): Sets the key bit size.
  psa_set_key_usage_flags(attributes, flags): Sets key usage flags.
  psa_set_key_algorithm(attributes, alg): Sets the key algorithm.
  psa_set_key_id(attributes, id): Sets the key ID.
  psa_set_key_lifetime(attributes, lifetime): Sets the key lifetime.
  psa_import_key(attributes, data, data_len): Imports a key into the crypto module.
  psa_export_key(key, data, data_len, data_len_actual): Exports a key.
  psa_get_key_attributes(key, attributes): Retrieves key attributes.
  psa_get_key_algorithm(key, alg): Retrieves the key algorithm.
  psa_reset_key_attributes(attributes): Resets key attributes.
  psa_destroy_key(key): Destroys a key.

Key Derivation:
  psa_key_derivation_operation_init(): Initializes a key derivation operation.
  psa_key_derivation_setup(operation, alg): Sets up the key derivation algorithm.
  psa_key_derivation_set_capacity(operation, capacity): Sets the capacity for the derivation.
  psa_key_derivation_input_bytes(operation, parameter, data, data_len): Inputs byte data into the operation.
  psa_key_derivation_input_key(operation, parameter, key): Inputs a key into the operation.
  psa_key_derivation_key_agreement(operation, private_key, public_key): Performs key agreement.
  psa_key_derivation_abort(operation): Aborts a key derivation operation.
  sl_psa_key_derivation_single_shot(attributes, alg, input, input_len, output, output_len): Silicon Labs custom single-shot key derivation.

Cleanup:
  mbedtls_psa_crypto_free(): Frees resources used by PSA Crypto.
```

--------------------------------

### Quick Start: Node 2 TCP Connection Confirmation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_TCP.md

Shows the expected output on Node 2 after establishing a TCP connection.

```bash
TCP: Connection established
```

--------------------------------

### CoAP Service Control

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_COAP.md

Controls the lifecycle of the CoAP service. Commands include starting and stopping the application's CoAP service.

```APIDOC
coap start
  Starts the application coap service.

coap stop
  Stops the application coap service.
Examples:
  > coap start
  > coap stop
```

```bash
> coap start
Done
> coap stop
Done
```

--------------------------------

### Console Output: Initial Configuration

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/rail/documentation/example/rail_soc_burst_duty_cycle/readme.md

Displays the initial bitrate, off-time, and on-time configuration of the Burst Duty Cycle example upon startup.

```text
Burst Duty Cycle
Bitrate is 500000 b/s with 497000 us off time and 3000 us on time
```

--------------------------------

### Include cJSON in C Code

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/cjson/README.md

The standard C include directive required to use the cJSON library in your C/C++ projects after installation.

```c
#include <cjson/cJSON.h>
```

--------------------------------

### Install Dependencies on Debian

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/Simple-web-server/repo/README.md

Installs necessary development libraries for SSL and Boost.Asio on Debian-based systems.

```shell
sudo apt-get install libssl-dev libboost-filesystem-dev libboost-thread-dev
```

--------------------------------

### Wi-SUN CLI: Help Command

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/protocol/wisun/app/wisun_soc_cli/doc/readme.md

Displays available commands and their brief descriptions in the console.

```APIDOC
Wi-SUN CLI Help:

wisun help
  Displays a list of all available commands and their associated help text.
  - Example:
    - wisun help
```

--------------------------------

### TCAT Server Start/Stop

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_TCAT.md

Controls the TCAT server and its associated BLE advertisement. The 'start' command initiates the server and advertisement, while 'stop' terminates them.

```APIDOC
TCAT Server Control Commands:

start
  Starts the TCAT server and BLE advertisement.
  Example:
    tcat start
    Done

stop
  Stops the TCAT server and BLE advertisement.
  Example:
    tcat stop
    Done
```

--------------------------------

### Run Host Application

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/app/bluetooth/example_host/bt_cs_host/readme.md

Example command to run the CS host application, specifying the serial port.

```shell
./exe/bt_cs_host -u /dev/tty.usbmodem0004402717881
```

--------------------------------

### Connect to Peer and Get Resource

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_COAPS.md

Connects to a peer device using its IPv6 address and retrieves data from the 'test-resource'. This is performed on the client node.

```bash
> coaps connect <peer-ip6-address>
Done
coaps connected
> coaps get test-resource
Done
coaps response from fdde:ad00:beef:0:9903:14b:27e0:5744 with payload: 68656c6c6f576f726c6400
```

--------------------------------

### Install otbr-agent Init Script

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/src/openwrt/CMakeLists.txt

Configures the otbr-agent.init.in file to otbr-agent.init and installs it to the system's init.d directory, renaming it to otbr-agent. This sets up the agent as a service.

```CMake
configure_file(otbr-agent.init.in otbr-agent.init)
install(FILES ${CMAKE_CURRENT_BINARY_DIR}/otbr-agent.init
    DESTINATION ${CMAKE_INSTALL_FULL_SYSCONFDIR}/init.d
    RENAME otbr-agent)
```

--------------------------------

### Quick Start: Node 1 TCP Receive Confirmation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/src/cli/README_TCP.md

Shows the expected output on Node 1 after receiving data sent from Node 2.

```bash
Accepted connection from [fe80:0:0:0:8f3:f602:bf9b:52f2]:49152
TCP: Connection established
TCP: Received 5 bytes: hello
```

--------------------------------

### Compiler Flags and Example Builds

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/ot-br-posix/third_party/Simple-web-server/repo/CMakeLists.txt

Sets compiler flags for C++11, warnings, and builds example executables (http_examples, https_examples) if the project is not a sub-project and dependencies are met.

```cmake
if(CMAKE_SOURCE_DIR STREQUAL "${CMAKE_CURRENT_SOURCE_DIR}")
    if(NOT MSVC)
        add_compile_options(-std=c++11 -Wall -Wextra)
        if (CMAKE_CXX_COMPILER_ID MATCHES "Clang")
            add_compile_options(-Wthread-safety)
        endif()
    else()
        add_compile_options(/W1)
    endif()

    find_package(Boost 1.53.0 COMPONENTS system thread filesystem)
    if(Boost_FOUND)
        add_executable(http_examples http_examples.cpp)
        target_link_libraries(http_examples simple-web-server)
        target_link_libraries(http_examples ${Boost_LIBRARIES})
        target_include_directories(http_examples PRIVATE ${Boost_INCLUDE_DIR})
        if(OPENSSL_FOUND)
            add_executable(https_examples https_examples.cpp)
            target_link_libraries(https_examples simple-web-server)
            target_link_libraries(https_examples ${Boost_LIBRARIES})
            target_include_directories(https_examples PRIVATE ${Boost_INCLUDE_DIR})
        endif()
     endif()

    install(FILES asio_compatibility.hpp server_http.hpp client_http.hpp server_https.hpp client_https.hpp crypto.hpp utility.hpp status_code.hpp mutex.hpp DESTINATION include/simple-web-server)
endif()
```

--------------------------------

### Spawn OpenThread CLI Simulation

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/util/third_party/openthread/examples/platforms/simulation/README.md

Command to start the OpenThread CLI simulation process. After building, navigate to the simulation examples directory and execute the ot-cli-ftd binary.

```bash
$ cd <path-to-openthread>/build/simulation/examples/apps/cli
$ ./ot-cli-ftd 1

```

--------------------------------

### Start Node 2 (ot-cli-ftd/ot-cli-mtd) OpenThread CLI

Source: https://github.com/siliconlabs/simplicity_sdk/blob/sisdk-2024.12/protocol/openthread/sample-apps/ot-cli/README.md

Configures a second OpenThread device (ot-cli-ftd or ot-cli-mtd) to join the network established by Node 1. This involves setting the network key, committing the active operational dataset, bringing up the IPv6 interface, and starting the Thread protocol. It verifies the device's role (child or router).

```bash
> dataset networkkey dfd34f0f05cad978ec4e32b0413038ff
Done
> dataset commit active
Done
> ifconfig up
Done
> thread start
Done
> state
child
Done
```