| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 43 relies on an Initiator to give it a list of Target nodes and transfer parameters. The Distributor
46 with the Initiator, and the :ref:`bluetooth_mesh_dfu_cli` is responsible for distributing the
49 Initiator
50 The Initiator role is typically implemented by the same device that implements the Bluetooth Mesh
52 <bluetooth_mesh_models_cfg_cli>` roles. The Initiator needs a full overview of the potential
54 Initiator role is not implemented in the Zephyr Bluetooth Mesh DFU subsystem.
65 the Distributor and Initiator role can be combined by instantiating the
66 :ref:`bluetooth_mesh_dfu_cli` on the Initiator node and calling its API directly.
68 It's also possible to combine the Initiator and Distributor devices into a single device, and
83 phone or gateway (the Initiator). During the Upload stage, the Initiator transfers the firmware
[all …]
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | Kconfig.cap | 34 bool "Common Audio Profile Initiator Role Support"
38 Enabling this will enable the CAP Initiator role.
42 bool "Common Audio Profile Initiator Role Support"
50 Enabling this will enable the CAP Initiator role.
|
| /Zephyr-latest/samples/bluetooth/channel_sounding/connected_cs/initiator/ |
| D | sample.yaml | 2 name: Bluetooth Channel Sounding - Initiator
4 sample.bluetooth.channel_sounding.connected_cs.initiator:
|
| /Zephyr-latest/samples/bluetooth/channel_sounding/cs_test/initiator/ |
| D | sample.yaml | 2 name: Bluetooth Channel Sounding Test - Initiator
4 sample.bluetooth.channel_sounding.cs_test.initiator:
|
| /Zephyr-latest/samples/bluetooth/periodic_adv_conn/ |
| D | README.rst | 2 :name: Periodic Advertising Connection Procedure (Initiator)
10 A simple application demonstrating the initiator side of the BLE
13 How the initiator decides the address of the synced device to connect to
|
| /Zephyr-latest/dts/bindings/ipc/ |
| D | zephyr,ipc-icmsg-me-initiator.yaml | 7 description: Multiendpoint inter core messaging backend in initiator role
9 compatible: "zephyr,ipc-icmsg-me-initiator"
|
| /Zephyr-latest/samples/bluetooth/tmap_bms/src/ |
| D | tmap_bms.h | 9 * @brief Initialize the CAP Initiator role
16 * @brief Setup streams for CAP Initiator
|
| /Zephyr-latest/tests/bluetooth/host/conn/src/ |
| D | main.c | 78 zassert_equal(err, -EINVAL, "Failed starting initiator (err %d)", err); in ZTEST()
81 zassert_equal(err, -EAGAIN, "Failed starting initiator (err %d)", err); in ZTEST()
87 zassert_not_equal(err, -EINVAL, "Failed starting initiator (err %d)", err); in ZTEST()
124 zassert_equal(err, -EINVAL, "Failed starting initiator (err %d)", err); in ZTEST()
127 zassert_equal(err, -EAGAIN, "Failed starting initiator (err %d)", err); in ZTEST()
133 zassert_not_equal(err, -EINVAL, "Failed starting initiator (err %d)", err); in ZTEST()
|
| /Zephyr-latest/samples/bluetooth/cap_initiator/src/ |
| D | main.c | 38 LOG_ERR("Failed to run CAP Initiator as broadcaster: %d", err); in main()
43 * function that runs the application as a CAP Initiator for unicast. This will attempt to in main()
53 LOG_ERR("Failed to run CAP Initiator as unicast: %d", err); in main()
|
| D | cap_initiator.h | 18 * @brief Run the application as a CAP Initiator for unicast
28 * @brief Run the application as a CAP Initiator for broadcast
|
| /Zephyr-latest/samples/bluetooth/cap_initiator/ |
| D | sample.yaml | 2 description: Bluetooth Low Energy Common Audio Profile Initiator sample
3 name: Bluetooth Low Energy Common Audio Profile Initiator sample
|
| D | prj.conf | 8 CONFIG_BT_DEVICE_NAME="CAP Initiator"
|
| D | README.rst | 2 :name: Common Audio Profile (CAP) Initiator
10 Application demonstrating the CAP Initiator functionality.
|
| D | Kconfig | 4 mainmenu "Bluetooth: Common Audio Profile initiator sample"
|
| /Zephyr-latest/tests/bsim/bluetooth/audio_samples/cap/ |
| D | compile.sh | 13 app=tests/bsim/bluetooth/audio_samples/cap/initiator \
25 app=tests/bsim/bluetooth/audio_samples/cap/initiator \
36 app=tests/bsim/bluetooth/audio_samples/cap/initiator \
48 app=tests/bsim/bluetooth/audio_samples/cap/initiator \
|
| /Zephyr-latest/subsys/ipc/ipc_service/backends/ |
| D | Kconfig | 30 bool "ICMSG backend with multi-endpoint support in initiator role"
37 on circular packet buffer. This enables enpoint discovery initiator
|
| D | Kconfig.icmsg_me | 29 initiator and the follower.
|
| /Zephyr-latest/samples/subsys/ipc/ipc_service/multi_endpoint/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 36 compatible = "zephyr,ipc-icmsg-me-initiator";
50 compatible = "zephyr,ipc-icmsg-me-initiator";
|
| /Zephyr-latest/samples/bluetooth/tmap_central/src/ |
| D | tmap_central.h | 56 * @brief Initialize the CAP Initiator role
63 * @brief Setup streams for CAP Initiator
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 308 * **Initiator** - It assigns endpoint addresses and sends binding messages.
313 * If ``address of rx-region < address of tx-region``, then it is initiator.
324 Initiator Binding Procedure
327 The initiator sends a binding message.
348 The endpoint binding procedure from the initiator's point of view is the following:
350 #. The initiator assigns an endpoint address to this endpoint.
351 #. The initiator sends a binding message containing the endpoint name and address.
352 #. The initiator waits for any message from the follower using this endpoint address.
354 #. The initiator is bound to an endpoint, and it can send data messages using this endpoint.
366 #. The follower stores the endpoint address assigned to this endpoint by the initiator.
|
| /Zephyr-latest/subsys/bluetooth/host/classic/ |
| D | rfcomm_internal.h | 171 * Initiator --> Responder 1
172 * Responder --> Initiator 0
174 * Initiator --> Responder 0
175 * Responder --> Initiator 1
|
| /Zephyr-latest/tests/bluetooth/audio/cap_initiator/ |
| D | prj.conf | 13 # Dependencies for CAP initiator unicast
|
| /Zephyr-latest/samples/boards/bbc/microbit/pong/src/ |
| D | pong.h | 8 void pong_conn_ready(bool initiator);
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | cap.rst | 63 CAP Initiator
66 The Initiator will typically be a resource-rich device, such as a phone or PC. The Initiator can
68 information about other CAP Acceptors in the same Coordinated Set. The Initiator can execute
72 Using the CAP Initiator argument
75 When the Bluetooth stack has been initialized (:code:`bt init`), the Initiator can discover CAS and
77 The CAP initiator also supports broadcast audio as a source.
82 cap_initiator - Bluetooth CAP initiator shell commands
194 To start a broadcast as the CAP initiator there are a few steps to be done:
242 The Commander will typically be a either co-located with a CAP Initiator or be on a separate
|
| D | tmap.rst | 6 devices. Thus both the initiator and acceptor (or central and peripheral) should do a discovery of
|
