Lines Matching +full:code +full:- +full:0
9 The Acceptor will typically be a resource-constrained device, such as a headset, earbud or hearing
16 When the Bluetooth stack has been initialized (:code:`bt init`), the Acceptor can be registered by
17 calling :code:`cap_acceptor init`, which will register the CAS and CSIS services, as well as
20 .. code-block:: console
23 cap_acceptor --help
24 cap_acceptor - Bluetooth CAP acceptor shell commands
27 [rank <int>] [not-lockable] [sirk <data>]
39 ------------------
42 :code:`bt adv-data` or :code:`bt advertise` must be called again to set the new advertising data.
43 If :code:`CONFIG_BT_CSIP_SET_MEMBER_NOTIFIABLE` is enabled, this will also notify connected
46 .. code-block:: console
52 ------------------------
56 .. code-block:: console
66 The Initiator will typically be a resource-rich device, such as a phone or PC. The Initiator can
69 stream control procedures on sets of devices, either ad-hoc or Coordinated, and thus provides an
75 When the Bluetooth stack has been initialized (:code:`bt init`), the Initiator can discover CAS and
76 the optionally included CSIS instance by calling (:code:`cap_initiator discover`).
79 .. code-block:: console
81 uart:~$ cap_initiator --help
82 cap_initiator - Bluetooth CAP initiator shell commands
116 :code:`bap discover` operation to discover the ASEs and PAC records. The :code:`bap init`
120 --------------
124 .. code-block:: console
132 .. code-block:: console
135 conn 0x81cc260: #0: codec 0x81d5b28 dir 0x01
136 codec 0x06 cid 0x0000 vid 0x0000 count 5
137 data #0: type 0x01 len 2
139 data #1: type 0x02 len 1
140 data #2: type 0x03 len 1
141 data #3: type 0x04 len 4
143 data #4: type 0x05 len 1
144 meta #0: type 0x01 len 2
148 Conn: 0x81cc260, Sink #0: ep 0x81e4248
149 Conn: 0x81cc260, Sink #1: ep 0x81e46a8
150 conn 0x81cc260: #0: codec 0x81d5f00 dir 0x02
151 codec 0x06 cid 0x0000 vid 0x0000 count 5
152 data #0: type 0x01 len 2
154 data #1: type 0x02 len 1
155 data #2: type 0x03 len 1
156 data #3: type 0x04 len 4
158 data #4: type 0x05 len 1
159 meta #0: type 0x01 len 2
163 Conn: 0x81cc260, Source #0: ep 0x81e5c88
164 Conn: 0x81cc260, Source #1: ep 0x81e60e8
165 Discover complete: err 0
168 To use multiple devices, simply connect to more and then use :code:`bt select` the device to execute
172 :code:`cap_initiator unicast_start` command can be used to put one or more streams into the
175 .. code-block:: console
177 uart:~$ cap_initiator unicast_start sinks 1 sources 0 conns all
178 Setting up 1 sinks and 0 sources on each (2) conn
182 To stop all the streams that has been started, the :code:`cap_initiator unicast_stop` command can be
186 .. code-block:: console
192 --------------------
203 .. code-block:: console
207 bt adv-create nconn-nscan ext-adv name
208 bt per-adv-param
211 bt adv-data discov
212 bt per-adv-data
216 The broadcast source is created by the :code:`cap_initiator ac_12`, :code:`cap_initiator ac_13`,
217 and :code:`cap_initiator ac_14` commands, configuring the broadcast source for the defined audio
219 :code:`cap_initiator broadcast_stop` or deleted with :code:`cap_initiator broadcast_delete`.
222 streaming. To update the metadata the :code:`cap_initiator broadcast_update` command can be used.
227 .. code-block:: console
230 CAP Broadcast source updated with new metadata. Update the advertised base via `bt per-adv-data`
231 bt per-adv-data
233 The :code:`bt per-adv-data` command should be used afterwards to update the data is the advertised
234 BASE. The data must be little-endian, so in the above example the metadata :code:`03020400` is
235 setting the metadata entry with :code:`03` as the length, :code:`02` as the type (streaming context)
236 and :code:`0400` as the value :code:`BT_AUDIO_CONTEXT_TYPE_MEDIA`
237 (which has the numeric value of 0x).
242 The Commander will typically be a either co-located with a CAP Initiator or be on a separate
243 resource-rich mobile device, such as a phone or smartwatch. The Commander can
252 When the Bluetooth stack has been initialized (:code:`bt init`), the Commander can discover CAS and
253 the optionally included CSIS instance by calling (:code:`cap_commander discover`).
255 .. code-block:: console
257 cap_commander --help
258 cap_commander - Bluetooth CAP commander shell commands
274 distribute_broadcast_code : Distribute broadcast code <src_id [...]> <broadcast_code>
278 :code:`bap discover` operation to discover the ASEs and PAC records. The :code:`bap init`
282 --------------
287 .. code-block:: console
296 .. code-block:: console
303 VCP volume 15, mute 0
305 VCP volume 15, mute 0
306 VCP flags 0x01
312 The offsets are set by connection index, so connection index 0 gets the first offset,
315 .. code-block:: console
333 VOCS inst 0x200140a4 offset 10
334 Offset set for inst 0x200140a4
339 Offset set for inst 0x200140a4
340 VOCS inst 0x20014188 offset 15
341 Offset set for inst 0x20014188
347 .. code-block:: console
370 uart:~$ cap_commander change_volume_mute 0
371 Setting volume mute to 0 on 2 connections
372 VCP volume 100, mute 0
374 VCP volume 100, mute 0
381 .. code-block:: console
404 uart:~$ cap_commander change_microphone_mute 0
405 Setting microphone mute to 0 on 2 connections
406 MICP microphone 100, mute 0
408 MICP microphone 100, mute 0
414 The gains are set by connection index, so connection index 0 gets the first offset,
417 .. code-block:: console
435 AICS inst 0x200140a4 state gain 10, mute 0, mode 0
436 Gain set for inst 0x200140a4
441 Gain set for inst 0x200140a4
442 AICS inst 0x20014188 state gain 15, mute 0, mode 0
443 Gain set for inst 0x20014188
449 .. code-block:: console
458 uart:~$ cap_commander broadcast_reception_start <device B> 0 4
461 uart:~$ cap_commander broadcast_reception_stop 0
465 Distributing the broadcast code
468 .. code-block:: console
477 uart:~$ cap_commander broadcast_reception_start <device B> 0 4
480 uart:~$ cap_commander distribute_broadcast_code 0 "BroadcastCode"
481 Distribute broadcast code completed