Home
last modified time | relevance | path

Searched refs:mesh (Results 1 – 25 of 102) sorted by relevance

12345

/Zephyr-latest/doc/connectivity/bluetooth/api/
Dmesh.rst8 `Bluetooth Mesh Protocol Specification v1.1 <https://www.bluetooth.com/specifications/specs/mesh-pr…
11 `Bluetooth SIG Website <https://www.bluetooth.com/bluetooth-resources/?tags=mesh>`_.
16 mesh/core.rst
17 mesh/access.rst
18 mesh/models.rst
19 mesh/msg.rst
20 mesh/sar_cfg.rst
21 mesh/provisioning.rst
22 mesh/proxy.rst
23 mesh/heartbeat.rst
[all …]
/Zephyr-latest/tests/bsim/bluetooth/mesh/
Dcompile.sh13 app=tests/bsim/bluetooth/mesh compile
14 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_pst.conf compile
15 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_gatt.conf compile
16 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_gatt_separate.conf compile
17 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_low_lat.conf compile
18 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_psa.conf compile
19 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_workq_sys.conf compile
20 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_multi_adv_sets.conf compile
21 app=tests/bsim/bluetooth/mesh \
23 app=tests/bsim/bluetooth/mesh conf_overlay="overlay_gatt.conf;overlay_psa.conf" compile
[all …]
DREADME.rst10 mesh subsystem, and each folder has a corresponding test_<subfolder>.c under the
24 To only run the mesh tests, set ``SEARCH_PATH`` to point to this folder before
61 BabbleSim platform, but with some mesh specific additions:
75 ``RunTest`` starts one mesh application for each selected harness, before
81 Common target side mesh behavior is collected in mesh_test.c and mesh_test.h.
82 This includes ``PASS``/``FAIL`` macros and some common mesh actions, such as
83 mesh initialization, as well as message sending and receiving.
105 Each mesh test harness should call the ``bt_mesh_test_cfg`` function from its
106 ``test_init_f`` callback to set up the test timeout and mesh metadata. The test
/Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/
DCMakeLists.txt13 src/mesh/ble_mesh.c
14 src/mesh/device_composition.c
15 src/mesh/no_transition_work_handler.c
16 src/mesh/publisher.c
17 src/mesh/state_binding.c
18 src/mesh/transition.c
23 src/mesh
DREADME.rst64 This sample can be found under :zephyr_file:`samples/boards/nordic/mesh/onoff_level_lighting_vnd_ap…
70 :zephyr-app: samples/boards/nordic/mesh/onoff_level_lighting_vnd_app
99 the mesh configuration. As additional nodes (boards) are provisioned, it
114 This application was derived from the sample mesh skeleton at
115 :zephyr_file:`samples/bluetooth/mesh`.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dshell.rst17 the mesh initialization.
29 The Bluetooth Mesh shell subsystem adds a single ``mesh`` command, which holds a set of
30 sub-commands. Every time the device boots up, make sure to call ``mesh init`` before any of the
33 uart:~$ mesh init
40 The mesh node must be provisioned to become part of the network. This is only necessary the first
46 uart:~$ mesh prov local 0 0x0001
48 Since all mesh nodes use the same values for the default network key, this can be done on multiple
51 ``mesh prov pb-adv on`` or ``mesh prov pb-gatt on``. The beacons can be picked up by an external
54 Once the mesh node is part of a network, its transmission parameters can be controlled by the
57 * To set the destination address, call ``mesh target dst <Addr>``.
[all …]
Dpriv_beacon_srv.rst7 mesh specification. It is enabled with
11 Specification version 1.1, and controls the mesh node's Private Beacon state,
16 mesh node from being tracked by devices outside the mesh network, and hides the
27 :c:macro:`BT_MESH_MODEL_PRIV_BEACON_SRV`. Note that if the mesh node stored
Dpriv_beacon_cli.rst7 mesh specification. It is enabled with the
16 mesh node from being tracked by devices outside the mesh network, and hides the
Dcfg.rst11 mesh node instantiates a :ref:`bluetooth_mesh_models_cfg_srv` model that the
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
Dcore.rst15 a mesh network as a leaf node. An LPN interacts with the mesh network through
20 The radio control and polling is managed automatically by the mesh stack, but
36 numbers from elements within the mesh network to perform protection against
41 the amount of traffic in a mesh network, storing recently seen sequence numbers
75 The mesh stack uses the :ref:`Settings Subsystem <settings_api>` for storing the
118 All mesh stack bearers advertise data with the :c:macro:`BT_ID_DEFAULT` local identity.
119 The value is preset in the mesh stack implementation. When Bluetooth® Low Energy (LE)
Ddfu_cli.rst6 The Firmware Update Client is responsible for distributing firmware updates through the mesh
Daccess.rst13 The functionality of a mesh node is represented by models. A model implements
15 thermostat. The mesh models are grouped into *elements*. Each element is
17 model. Conventionally, each element represents a single aspect of the mesh
28 <https://www.bluetooth.com/specifications/mesh-specifications/>`_. All models
33 initialization of the mesh stack or with the
70 multiple nodes throughout the mesh network with a single message.
92 the mesh network than the individual nodes will.
116 The Bluetooth Mesh specification allows the mesh models to extend each other.
122 lists. The mesh stack implements this by merging the subscription lists of the
171 The Composition Data provides information about a mesh device.
[all …]
Drpr_srv.rst7 mesh specification. It is enabled with the
12 provisioning devices into a mesh network.
/Zephyr-latest/tests/bluetooth/mesh/brg/
DCMakeLists.txt11 ${ZEPHYR_BASE}/subsys/bluetooth/mesh/brg_cfg.c)
15 ${ZEPHYR_BASE}/subsys/bluetooth/mesh
/Zephyr-latest/tests/bluetooth/mesh/rpl/
DCMakeLists.txt11 ${ZEPHYR_BASE}/subsys/bluetooth/mesh/rpl.c)
15 ${ZEPHYR_BASE}/subsys/bluetooth/mesh
/Zephyr-latest/tests/bluetooth/mesh/delayable_msg/
DCMakeLists.txt11 ${ZEPHYR_BASE}/subsys/bluetooth/mesh/delayable_msg.c)
15 ${ZEPHYR_BASE}/subsys/bluetooth/mesh
/Zephyr-latest/samples/bluetooth/mesh/
DREADME.rst11 standard mesh models, and supports provisioning over both the
17 controlling the first LED on the board over the mesh.
31 This sample can be found under :zephyr_file:`samples/bluetooth/mesh` in the
40 :zephyr-app: samples/bluetooth/mesh
52 to enable mesh support.
57 The sample can either be provisioned into an existing mesh network with an
DCMakeLists.txt7 project(mesh) project
/Zephyr-latest/samples/boards/nordic/mesh/onoff-app/
DREADME.rst5 Control LEDs on a mesh network using the Bluetooth Mesh OnOff model.
11 Each element has a mesh onoff client and server
17 corresponding LED and does not initiate any mesh activity.
47 This sample can be found under :zephyr_file:`samples/boards/nordic/mesh/onoff-app` in the
53 :zephyr-app: samples/boards/nordic/mesh/onoff-app
78 the mesh configuration. As additional nodes (boards) are provisioned, it
97 This application was derived from the sample mesh skeleton at
98 :zephyr_file:`samples/bluetooth/mesh`.
/Zephyr-latest/doc/connectivity/networking/api/
Dthread.rst12 Thread is a low-power mesh networking technology, designed specifically for home
15 a Thread mesh network to the internet with a Thread Border Router.
19 and all communications within the mesh are encrypted. More information about
29 A Thread Border Router is required to connect mesh network to the internet.
/Zephyr-latest/tests/bluetooth/mesh/basic/
DCMakeLists.txt5 project(mesh) project
/Zephyr-latest/subsys/bluetooth/
DCMakeLists.txt10 add_subdirectory_ifdef(CONFIG_BT_MESH mesh)
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dod_priv_proxy.c51 SHELL_SUBCMD_ADD((mesh, models), od_priv_proxy, &od_priv_proxy_cmds,
/Zephyr-latest/tests/bsim/bluetooth/
Dcompile.sh22 ${ZEPHYR_BASE}/tests/bsim/bluetooth/mesh/compile.sh
/Zephyr-latest/boards/atmarktechno/degu_evk/doc/
Dindex.rst4 and can connect to an OpenThread mesh network. The Kit has a

12345