Lines Matching +full:code +full:- +full:1
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
61 1d 9a 2f 41 01 73 3e 01 |../A.s>.
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
85 unicast_start : Unicast Start [csip] [sinks <cnt> (default 1)] [sources
86 <cnt> (default 1)] [conns (<cnt> | all) (default 1)]
91 ac_1 : Unicast audio configuration 1
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
139 data #1: type 0x02 len 1
140 data #2: type 0x03 len 1
142 00000000: 1e 00 f0 |... |
143 data #4: type 0x05 len 1
146 dir 1 loc 1
149 Conn: 0x81cc260, Sink #1: ep 0x81e46a8
154 data #1: type 0x02 len 1
155 data #2: type 0x03 len 1
157 00000000: 1e 00 f0 |... |
158 data #4: type 0x05 len 1
161 dir 2 loc 1
164 Conn: 0x81cc260, Source #1: ep 0x81e60e8
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
179 Starting 1 streams
182 To stop all the streams that has been started, the :code:`cap_initiator unicast_stop` command can be
186 .. code-block:: console
192 --------------------
196 1. Create and configure an extended advertising set with periodic advertising
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`
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
299 VCP discover done with 1 VOCS and 1 AICS
313 and index 1 gets the second offset, etc.:
315 .. code-block:: console
322 VCP discover done with 1 VOCS and 1 AICS
329 VCP discover done with 1 VOCS and 1 AICS
332 Setting volume offset on 1 connections
347 .. code-block:: console
354 VCP discover done with 1 VOCS and 1 AICS
361 VCP discover done with 1 VOCS and 1 AICS
363 uart:~$ cap_commander change_volume_mute 1
364 Setting volume mute to 1 on 2 connections
365 VCP volume 100, mute 1
367 VCP volume 100, mute 1
381 .. code-block:: console
388 MICP discover done with 1 VOCS and 1 AICS
395 MICP discover done with 1 VOCS and 1 AICS
397 uart:~$ cap_commander change_microphone_mute 1
398 Setting microphone mute to 1 on 2 connections
399 MICP microphone 100, mute 1
401 MICP microphone 100, mute 1
415 and index 1 gets the second offset, etc.:
417 .. code-block:: console
424 MICP discover done with 1 AICS
431 MICP discover done with 1 AICS
434 Setting microphone gain on 1 connections
449 .. code-block:: console
457 BASS discover done with 1 recv states
459 Starting broadcast reception on 1 connection(s)
462 Stopping broadcast reception on 1 connection(s)
465 Distributing the broadcast code
468 .. code-block:: console
476 BASS discover done with 1 recv states
478 Starting broadcast reception on 1 connection(s)
481 Distribute broadcast code completed