Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

samples: bluetooth: use zephyr:code-sample directive #77760

Merged
merged 2 commits into from
Sep 5, 2024
Merged

samples: bluetooth: use zephyr:code-sample directive #77760

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
28808f3
samples: bluetooth: use zephyr:code-sample directive
kartben Aug 29, 2024
6d1af38
samples: bluetooth: Use "Bluetooth LE" terminology
kartben Sep 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion boards/96boards/carbon/doc/stm32f401xe.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,7 +347,7 @@ in general, see :ref:`build_an_application`.
:board: 96b_carbon/stm32f401xe
:goals: build flash

#. Refer to the instructions in :ref:`peripheral_hr` for how
#. Refer to the instructions in :zephyr:code-sample:`ble_peripheral_hr` for how
to verify functionality.

Congratulations! Your 96Boards Carbon now has Bluetooth
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bl5340_dvk/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -409,9 +409,9 @@ Testing Bluetooth on the BL5340 DVK
Many of the Bluetooth examples will work on the BL5340 DVK.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`

References
**********
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bl652_dvk/doc/bl652_dvk.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,9 +245,9 @@ Testing Bluetooth on the BL652 DVK
Many of the Bluetooth examples will work on the BL652 DVK.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`

Testing the LEDs and buttons in the BL652 DVK
*********************************************
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bl653_dvk/doc/bl653_dvk.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,9 +151,9 @@ Testing Bluetooth on the BL653 DVK
Many of the Bluetooth examples will work on the BL653 DVK.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`


Testing the LEDs and buttons on the BL653 DVK
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bl654_dvk/doc/bl654_dvk.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,9 +162,9 @@ Testing Bluetooth on the BL654 DVK
Many of the Bluetooth examples will work on the BL654 DVK.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`


Testing the LEDs and buttons on the BL654 DVK
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bl654_sensor_board/doc/bl654_sensor_board.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,9 +222,9 @@ Testing Bluetooth on the BL654 Sensor Board
Many of the Bluetooth examples will work on the BL654 Sensor Board.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`


Testing the LED and button on the BL654 Sensor Board
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bl654_usb/doc/bl654_usb.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,9 +160,9 @@ Testing Bluetooth on the BL654 USB
Many of the Bluetooth examples will work on the BL654 USB.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`


Testing the LED on the BL654 USB
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bt510/doc/bt510.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,9 +228,9 @@ Testing Bluetooth on the BT510
Many of the Bluetooth examples will work on the BT510.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`


Testing the LEDs and buttons on the BT510
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/bt610/doc/bt610.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -582,9 +582,9 @@ Testing Bluetooth on the BT610
Many of the Bluetooth examples will work on the BT610.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`


Testing the LEDs and buttons on the BT610
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/mg100/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,9 +213,9 @@ Testing Bluetooth on the MG100
Many of the Bluetooth examples will work on the MG100.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`

Testing the LEDs and buttons in the MG100
====================================================
Expand Down
6 changes: 3 additions & 3 deletions boards/ezurio/pinnacle_100_dvk/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,9 +187,9 @@ Testing Bluetooth on the Pinnacle 100 DVK
Many of the Bluetooth examples will work on the Pinnacle 100 DVK.
Try them out:

* :ref:`ble_peripheral`
* :ref:`bluetooth-eddystone-sample`
* :ref:`bluetooth-ibeacon-sample`
* :zephyr:code-sample:`ble_peripheral`
* :zephyr:code-sample:`bluetooth_eddystone`
* :zephyr:code-sample:`bluetooth_ibeacon`

Testing the LEDs and buttons in the Pinnacle 100 DVK
====================================================
Expand Down
2 changes: 1 addition & 1 deletion boards/silabs/dev_kits/sltb010a/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ blobs from the SiLabs HAL repository.
west blobs fetch hal_silabs

Then build the Zephyr kernel and a Bluetooth sample with the following
command. The :ref:`bluetooth-observer-sample` sample application is used in
command. The :zephyr:code-sample:`bluetooth_observer` sample application is used in
this example.

BRD4184A:
Expand Down
2 changes: 1 addition & 1 deletion boards/silabs/dev_kits/xg24_dk2601b/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ blobs from the SiLabs HAL repository.
west blobs fetch hal_silabs

Then build the Zephyr kernel and a Bluetooth sample with the following
command. The :ref:`bluetooth-observer-sample` sample application is used in
command. The :zephyr:code-sample:`bluetooth_observer` sample application is used in
this example.

.. zephyr-app-commands::
Expand Down
2 changes: 1 addition & 1 deletion boards/sparkfun/thing_plus_matter_mgm240p/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ blobs from the SiLabs HAL repository.
west blobs fetch silabs

Then build the Zephyr kernel and a Bluetooth sample with the following
command. The :ref:`bluetooth-observer-sample` sample application is used in
command. The :zephyr:code-sample:`bluetooth_observer` sample application is used in
this example.

.. zephyr-app-commands::
Expand Down
4 changes: 2 additions & 2 deletions boards/st/stm32wb5mmg/doc/stm32wb5mmg.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,7 @@ Flashing `hci_uart` application to STM32WB5MMG
Connect the B-U585I-IOT02A to your host computer using the USB port. Put
the SW4 (MCU SWD) in OFF mode and SW5 (SWD BLE) in ON mode. Then build
and flash an application. Here is an example for the
:ref:`hci_uart <bluetooth-hci-uart-sample>` application.
:zephyr:code-sample:`bluetooth_hci_uart` application.

Run a serial host program to connect with your B-U585I-IOT02A board:

Expand Down Expand Up @@ -287,7 +287,7 @@ Debugging
=========

You can debug an application in the usual way. Here is an example for the
:ref:`hci_uart <bluetooth-hci-uart-sample>` application.
:zephyr:code-sample:`bluetooth_hci_uart` application.

.. zephyr-app-commands::
:zephyr-app: samples/bluetooth/observer
Expand Down
4 changes: 2 additions & 2 deletions boards/vngiotlab/nrf51_vbluno51/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,8 +138,8 @@ Testing the VBLUno51 with Zephyr: buttons, LEDs, UART, BLE
* :ref:`hello_world`
* :zephyr:code-sample:`blinky`
* :zephyr:code-sample:`button`
* :ref:`bluetooth-beacon-sample`
* :ref:`peripheral_hr`
* :zephyr:code-sample:`bluetooth_beacon`
* :zephyr:code-sample:`ble_peripheral_hr`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is one prefixed with bluetooth_ and the other with ble_? Don't think the beacon sample runs on a classic stack.
I would prefer bluetooth_classic_xx for classic samples, and the rest is assumed to be LE.
What do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a few more with the same inconsistency. Also some that is prefixed with _, and even one that is bluetooth_bt :D

Are we planning on using explicit tags, or should we attempt to shorten them at bit? e.g.

bluetooth_beacon => bt_beacon
bluetooth_direction_finding_central => bt_df_central

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer long names for the documentation references. Shortening the filenames/path should be ok. Although i hope people have shell completion

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The simplest route might be to just use the same IDs as the folder names?
Related: is it time to introduce some subfolders underneath samples/bluetooth? It's starting to get really packed in there :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The simplest route might be to just use the same IDs as the folder names? Related: is it time to introduce some subfolders underneath samples/bluetooth? It's starting to get really packed in there :)

#64443 :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The simplest route might be to just use the same IDs as the folder names? Related: is it time to introduce some subfolders underneath samples/bluetooth? It's starting to get really packed in there :)

Sure, so we can have bluetooth prefix for all BT samples, and then, when we do the above move, we can have them like bluetooth_audio_xxx, bluetooth_mesh_xxx


References
**********
Expand Down
4 changes: 2 additions & 2 deletions boards/vngiotlab/nrf52_vbluno52/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,5 +103,5 @@ components on the VBLUno52 board:
* :ref:`hello_world`
* :zephyr:code-sample:`blinky`
* :zephyr:code-sample:`button`
* :ref:`bluetooth-beacon-sample`
* :ref:`peripheral_hr`
* :zephyr:code-sample:`bluetooth_beacon`
* :zephyr:code-sample:`ble_peripheral_hr`
2 changes: 1 addition & 1 deletion doc/build/dts/api/api.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,7 +382,7 @@ device.
- Purpose
* - zephyr,bt-c2h-uart
- Selects the UART used for host communication in the
:ref:`bluetooth-hci-uart-sample`
:zephyr:code-sample:`bluetooth_hci_uart`
* - zephyr,bt-mon-uart
- Sets UART device used for the Bluetooth monitor logging
* - zephyr,bt-hci
Expand Down
10 changes: 5 additions & 5 deletions doc/connectivity/bluetooth/bluetooth-arch.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,9 +97,9 @@ BLE-enabled builds that can be produced from the Zephyr project codebase:
the Link Layer and a special application. This application is different
depending on the physical transport chosen for HCI:

* :ref:`hci_uart <bluetooth-hci-uart-sample>`
* :ref:`hci_usb <bluetooth-hci-usb-sample>`
* :ref:`hci_spi <bluetooth-hci-spi-sample>`
* :zephyr:code-sample:`bluetooth_hci_uart`
* :zephyr:code-sample:`bluetooth_hci_usb`
* :zephyr:code-sample:`bluetooth_hci_spi`

This application acts as a bridge between the UART, SPI or USB peripherals and
the Controller subsystem, listening for HCI commands, sending application data
Expand Down Expand Up @@ -160,8 +160,8 @@ must be built with different configurations, yielding two separate images that
must be programmed into each of the chips respectively. The Host build image
contains the application, the BLE Host and the selected HCI driver (UART or
SPI), while the Controller build runs either the
:ref:`hci_uart <bluetooth-hci-uart-sample>`, or the
:ref:`hci_spi <bluetooth-hci-spi-sample>` app to provide an interface to
:zephyr:code-sample:`bluetooth_hci_uart`, or the
:zephyr:code-sample:`bluetooth_hci_spi` app to provide an interface to
the BLE Controller.

This configuration is not limited to using a Zephyr OS Host, as the right side
Expand Down
2 changes: 1 addition & 1 deletion doc/connectivity/bluetooth/bluetooth-dev.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ devices in either of :ref:`these boards's documentation <nrf52bsim_build_and_run

With the :ref:`nrf52_bsim <nrf52_bsim>`, typically you do :ref:`Combined builds
<bluetooth-build-types>`, but it is also possible to build the controller with one of the
:ref:`HCI UART <bluetooth-hci-uart-sample>` samples in one simulated device, and the host with
:zephyr:code-sample:`bluetooth_hci_uart` samples in one simulated device, and the host with
the H4 driver instead of the integrated controller in another simulated device.

With the :ref:`nrf5340bsim <nrf5340bsim>`, you can build with either, both controller and host
Expand Down
2 changes: 1 addition & 1 deletion doc/connectivity/bluetooth/bluetooth-shell.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -394,7 +394,7 @@ The server can now notify the client with the command :code:`gatt notify`.
Another option available through the GATT command is initiating the MTU exchange. To do it, use the
:code:`gatt exchange-mtu` command. To update the shell maximum MTU, you need to update Kconfig
symbols in the configuration file of the shell. For more details, see
:ref:`bluetooth_mtu_update_sample`.
:zephyr:code-sample:`bluetooth_mtu_update`.

L2CAP
*****
Expand Down
7 changes: 4 additions & 3 deletions doc/connectivity/bluetooth/bluetooth-tools.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,9 +166,9 @@ Using a Zephyr-based BLE Controller
Depending on which hardware you have available, you can choose between two
transports when building a single-mode, Zephyr-based BLE Controller:

* UART: Use the :ref:`hci_uart <bluetooth-hci-uart-sample>` sample and follow
* UART: Use the :zephyr:code-sample:`bluetooth_hci_uart` sample and follow
the instructions in :ref:`bluetooth-hci-uart-qemu-posix`.
* USB: Use the :ref:`hci_usb <bluetooth-hci-usb-sample>` sample and then
* USB: Use the :zephyr:code-sample:`bluetooth_hci_usb` sample and then
treat it as a Host System Bluetooth Controller (see previous section)

.. _bluetooth-hci-tracing:
Expand Down Expand Up @@ -301,7 +301,8 @@ After following these steps the Zephyr application will be available to the Andr
over the virtual Bluetooth controller that was bridged with Bumble. You can verify that the
Zephyr application can communicate over Bluetooth by opening the Bluetooth settings in your
AVD and scanning for your Zephyr application device. To test this you can build the Bluetooth
peripheral samples such as :ref:`Peripheral HR <peripheral_hr>` or :ref:`Peripheral DIS <peripheral_dis>`
peripheral samples such as :zephyr:code-sample:`ble_peripheral_hr` or
:zephyr:code-sample:`ble_peripheral_dis`.

.. _bluetooth_ctlr_bluez:

Expand Down
8 changes: 4 additions & 4 deletions doc/connectivity/usb/device/usb_device.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ the next interface, preventing other composite functions from working.
Because of this problem, HCI USB should not be used in a composite configuration.
This problem is fixed in the implementation for new USB support.

See :ref:`bluetooth-hci-usb-sample` sample for reference.
See :zephyr:code-sample:`bluetooth_hci_usb` sample for reference.

.. _usb_device_cdc_acm:

Expand Down Expand Up @@ -168,7 +168,7 @@ List of few Zephyr specific chosen properties which can be used to select
CDC ACM UART as backend for a subsystem or application:

* ``zephyr,bt-c2h-uart`` used in Bluetooth,
for example see :ref:`bluetooth-hci-uart-sample`
for example see :zephyr:code-sample:`bluetooth_hci_uart`
* ``zephyr,ot-uart`` used in OpenThread,
for example see :zephyr:code-sample:`coprocessor`
* ``zephyr,shell-uart`` used by shell for serial backend,
Expand Down Expand Up @@ -595,9 +595,9 @@ The following Product IDs are currently used:
+----------------------------------------------------+--------+
| :zephyr:code-sample:`webusb` | 0x000A |
+----------------------------------------------------+--------+
| :ref:`bluetooth-hci-usb-sample` | 0x000B |
| :zephyr:code-sample:`bluetooth_hci_usb` | 0x000B |
+----------------------------------------------------+--------+
| :ref:`bluetooth-hci-usb-h4-sample` | 0x000C |
| :zephyr:code-sample:`bluetooth_hci_usb_h4` | 0x000C |
+----------------------------------------------------+--------+
| Reserved (previously: wpan-usb) | 0x000D |
+----------------------------------------------------+--------+
Expand Down
2 changes: 1 addition & 1 deletion doc/connectivity/usb/device_next/usb_device.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ To build a sample that supports both the old and new USB device stack, set the
configuration ``-DCONF_FILE=usbd_next_prj.conf`` either directly or via
``west``.

* :ref:`bluetooth-hci-usb-sample`
* :zephyr:code-sample:`bluetooth_hci_usb`

* :zephyr:code-sample:`usb-cdc-acm`

Expand Down
4 changes: 2 additions & 2 deletions samples/bluetooth/bap_broadcast_assistant/README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
.. zephyr:code-sample:: bluetooth_bap_broadcast_assistant
:name: Bluetooth: Broadcast Audio Assistant
:name: Broadcast Audio Assistant
:relevant-api: bt_bap

Use LE Audio Broadcast Assistant functionality
Use LE Audio Broadcast Assistant functionality.

Overview
********
Expand Down
6 changes: 3 additions & 3 deletions samples/bluetooth/bap_broadcast_sink/README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
.. zephyr:code-sample:: bluetooth_bap_broadcast_sink
:name: Bluetooth: Broadcast Audio Sink
:name: Broadcast Audio Sink
:relevant-api: bluetooth

Bluetooth: Broadcast Audio Sink
Use LE Audio Broadcast Sink functionality.
Comment on lines +2 to +5
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'll follow up with a name update PR later - I think several of our LE audio samples could benefit from better names and descriptions, but let's not muddy this PR too much with that :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this would be awesome. It's true that a lot of the names and descriptions are very "content-free" right now and not all that helpful. Hopefully the follow-up PR will be much easier to implement once the directives will already be there :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#78094 :)


Overview
********
Expand Down Expand Up @@ -53,7 +53,7 @@ If you prefer to only build the application core image, you can do so by doing i
:goals: build

In that case you can pair this application core image with the
:ref:`hci_ipc sample <bluetooth-hci-ipc-sample>`
:zephyr:code-sample:`bluetooth_hci_ipc` sample
:zephyr_file:`samples/bluetooth/hci_ipc/nrf5340_cpunet_iso-bt_ll_sw_split.conf` configuration.

Building for a simulated nrf5340bsim
Expand Down
6 changes: 3 additions & 3 deletions samples/bluetooth/bap_broadcast_source/README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
.. zephyr:code-sample:: bluetooth_bap_broadcast_source
:name: Bluetooth: Broadcast Audio Source
:name: Broadcast Audio Source
:relevant-api: bluetooth

Bluetooth: Broadcast Audio Source
Use LE Audio Broadcast Source functionality.

Overview
********
Expand Down Expand Up @@ -52,7 +52,7 @@ If you prefer to only build the application core image, you can do so by doing i
:goals: build

In that case you can pair this application core image with the
:ref:`hci_ipc sample <bluetooth-hci-ipc-sample>`
:zephyr:code-sample:`bluetooth_hci_ipc` sample
:zephyr_file:`samples/bluetooth/hci_ipc/nrf5340_cpunet_iso-bt_ll_sw_split.conf` configuration.

Building for a simulated nrf5340bsim
Expand Down
9 changes: 5 additions & 4 deletions samples/bluetooth/bap_unicast_client/README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
.. _bluetooth_bap_unicast_client:
.. zephyr:code-sample:: bluetooth_bap_unicast_client
:name: Unicast Audio Client
:relevant-api: bt_bap bt_audio

Bluetooth: Unicast Audio Client
###############################
Use LE Audio Unicast Client functionality.

Overview
********
Expand Down Expand Up @@ -56,7 +57,7 @@ If you prefer to only build the application core image, you can do so by doing i
:goals: build

In that case you can pair this application core image with the
:ref:`hci_ipc sample <bluetooth-hci-ipc-sample>`
:zephyr:code-sample:`bluetooth_hci_ipc` sample
:zephyr_file:`samples/bluetooth/hci_ipc/nrf5340_cpunet_iso-bt_ll_sw_split.conf` configuration.

Building for a simulated nrf52_bsim
Expand Down
Loading
Loading