Searched refs:Configuration (Results 1 – 25 of 323) sorted by relevance
12345678910>>...13
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | sar_cfg_cli.rst | 3 SAR Configuration Client
6 The SAR Configuration Client model is a foundation model defined by the Bluetooth Mesh
10 The SAR Configuration Client model is introduced in the Bluetooth Mesh Protocol Specification
14 The model can send messages to query or change the states supported by the SAR Configuration Server
15 (SAR Transmitter and SAR Receiver) using SAR Configuration messages.
18 Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_transmitter_get` and
23 Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_receiver_get` and
29 An element can send any SAR Configuration Client message at any time to query or change the states
30 supported by the SAR Configuration Server model of a peer node. The SAR Configuration Client model
31 only accepts messages encrypted with the device key of the node supporting the SAR Configuration
[all …]
|
| D | srpl_cli.rst | 3 Solicitation PDU RPL Configuration Client
6 The Solicitation PDU RPL Configuration Client model is a foundation model defined by the Bluetooth
10 The Solicitation PDU RPL Configuration Client model was introduced in the Bluetooth Mesh Protocol
15 The Solicitation PDU RPL Configuration Client model communicates with a Solicitation PDU RPL
16 Configuration Server model using the application keys configured by the Configuration Client.
18 If present, the Solicitation PDU RPL Configuration Client model must only be instantiated on the
24 The Solicitation PDU RPL Configuration Client model behavior can be configured with the transmission
27 Configuration Client waits for a response message to arrive in milliseconds. This value can be
|
| D | cfg_cli.rst | 3 Configuration Client
6 The Configuration Client model is a foundation model defined by the Bluetooth Mesh
11 The Configuration Client model communicates with a
13 node. The Configuration Client model may communicate with servers on other
14 nodes or self-configure through the local Configuration Server model.
16 All configuration functions in the Configuration Client API have ``net_idx``
20 The Configuration Client model is optional, and it must only be instantiated on the
|
| D | brg_cfg_srv.rst | 3 Bridge Configuration Server
6 The Bridge Configuration Server model is a foundation model defined by the Bluetooth Mesh
11 The Bridge Configuration Server model was introduced in the Bluetooth Mesh Protocol Specification
14 The Bridge Configuration Server model relies on a :ref:`bluetooth_mesh_models_brg_cfg_cli` to
15 configure it. The Bridge Configuration Server model only accepts messages encrypted with the node’s
18 If present, the Bridge Configuration Server model must be instantiated on the primary element.
20 The Bridge Configuration Server model provides access to the following three states:
|
| D | brg_cfg_cli.rst | 3 Bridge Configuration Client
6 The Bridge Configuration Client is a foundation model defined by the Bluetooth Mesh
10 The Bridge Configuration Client model provides functionality for configuring the
13 the target Bridge Configuration Server is used for access layer security.
15 If present, the Bridge Configuration Client model must only be instantiated on the primary
|
| D | sar_cfg_srv.rst | 3 SAR Configuration Server
6 The SAR Configuration Server model is a foundation model defined by the Bluetooth Mesh
10 The SAR Configuration Server model is introduced in the Bluetooth Mesh Protocol Specification
15 The SAR Configuration Server model defines two states, SAR Transmitter state and SAR Receiver state.
20 The SAR Configuration Server model does not have an API of its own, but relies on a
21 :ref:`bluetooth_mesh_sar_cfg_cli` to control it. The SAR Configuration Server model only accepts
24 If present, the SAR Configuration Server model must only be instantiated on the primary element.
|
| D | cfg_srv.rst | 3 Configuration Server
6 The Configuration Server model is a foundation model defined by the Bluetooth Mesh
7 specification. The Configuration Server model controls most parameters of the
11 The Configuration Server model is mandatory on all Bluetooth Mesh nodes, and
|
| D | srpl_srv.rst | 3 Solicitation PDU RPL Configuration Server
6 The Solicitation PDU RPL Configuration Server model is a foundation model defined by the Bluetooth
9 The Solicitation PDU RPL Configuration Server model was introduced in the Bluetooth Mesh Protocol
15 The Solicitation PDU RPL Configuration Server does not have an API of its own, and relies on a
17 application key as configured by the Configuration Client.
19 If present, the Solicitation PDU RPL Configuration Server model must only be instantiated on the
25 For the Solicitation PDU RPL Configuration Server model, the
|
| D | cfg.rst | 3 Runtime Configuration
7 configuration directly, without going through the Configuration models.
12 Configuration Client can communicate with to change the node configuration. In some
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
|
| D | brg_cfg.rst | 20 The Bridge Configuration Server model is mandatory for supporting the Subnet Bridge feature.
21 The Bridge Configuration Client model is optional and allows nodes to configure the Subnet Bridge on
27 Configuration Server and Client models.
28 A node implementing the Bridge Configuration Client model can act as a *Configuration Manager* for
61 by the Bridge Configuration Server model.
70 The Bridge Configuration Client (or Configuration Manager) can enable or disable the Subnet Bridge
71 feature on a node by sending a **Subnet Bridge Set** message to the Bridge Configuration
77 The Bridge Configuration Client can add or remove an entry from the Bridging Table by sending a
78 **Bridging Table Add** or **Bridging Table Remove** message to the Bridge Configuration
91 The Bridge Configuration Client can retrieve this information by sending a **Subnet Bridge Get**
[all …]
|
| /Zephyr-latest/boards/nxp/ls1046ardb/ |
| D | ls1046ardb_ls1046a_smp_defconfig | 3 # Platform Configuration
9 # Zephyr Kernel Configuration
21 # Zephyr Kernel Configuration
|
| D | ls1046ardb_ls1046a_defconfig | 4 # Platform Configuration
10 # Zephyr Kernel Configuration
|
| D | ls1046ardb_ls1046a_smp_4cores_defconfig | 3 # Platform Configuration
9 # Zephyr Kernel Configuration
|
| /Zephyr-latest/tests/drivers/gpio/gpio_basic_api/boards/ |
| D | intel_adl_crb.overlay | 9 * Under Intel Advanced Menu > PCH-IO Configuration
12 * ISH Configuration > GP_6 > Unchecked [ ]
13 * ISH Configuration > GP_7 > Unchecked [ ]
|
| /Zephyr-latest/samples/bluetooth/eddystone/ |
| D | README.rst | 5 Export an Eddystone Configuration Service as a Bluetooth LE GATT service.
9 Application demonstrating `Eddystone Configuration Service`_
11 The Eddystone Configuration Service runs as a GATT service on the beacon while
31 .. _Eddystone Configuration Service: https://github.com/google/eddystone/tree/master/configuration-…
|
| /Zephyr-latest/boards/raspberrypi/rpi_4b/ |
| D | rpi_4b_defconfig | 3 # Platform Configuration
7 # Zephyr Kernel Configuration
|
| /Zephyr-latest/boards/ti/sk_am62/ |
| D | sk_am62_am6234_m4_defconfig | 8 # Platform Configuration
11 # Zephyr Kernel Configuration
|
| /Zephyr-latest/boards/phytec/phyboard_lyra/ |
| D | phyboard_lyra_am6234_a53_defconfig | 14 # Platform Configuration
16 # Zephyr Kernel Configuration
|
| D | phyboard_lyra_am6234_m4_defconfig | 8 # Platform Configuration
11 # Zephyr Kernel Configuration
|
| /Zephyr-latest/boards/phytec/phyboard_electra/ |
| D | phyboard_electra_am6442_m4_defconfig | 8 # Platform Configuration
11 # Zephyr Kernel Configuration
|
| /Zephyr-latest/boards/brcm/bcm958402m2/ |
| D | bcm958402m2_bcm58402_a72_defconfig | 3 # Platform Configuration
7 # Zephyr Kernel Configuration
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 3 Configuration System (Kconfig)
7 for specific application and platform needs. Configuration is handled through
11 Configuration options (often called *symbols*) are defined in :file:`Kconfig`
|
| /Zephyr-latest/soc/ti/simplelink/cc23x0/ |
| D | Kconfig | 23 menu "Bootloader Configuration"
49 endmenu # "Bootloader Configuration"
|
| /Zephyr-latest/boards/others/stm32_min_dev/ |
| D | Kconfig.stm32_min_dev | 1 # STM32 Minimum Development Board Configuration
|
| /Zephyr-latest/samples/net/cloud/tagoio_http_post/ |
| D | Kconfig | 4 mainmenu "TagoIO IoT Cloud Platform (HTTP Post) Client Configuration"
6 menu "TagoIO IoT Cloud Configuration"
|
12345678910>>...13
