zephyr

History

Johan Hedberg 9b19a90daa samples: bluetooth: Add build asserts for VS-using samples The README files of these samples already indicate that they use the Zephyr-specific HCI vendor extensions, but this may still not be clear enough to some users, as evidenced in #81779. Add build asserts to make sure the samples only build when Zephyr VS extensions have been enabled. Signed-off-by: Johan Hedberg <johan.hedberg@silabs.com>		2024-11-27 10:30:32 +01:00
..
src	samples: bluetooth: Add build asserts for VS-using samples	2024-11-27 10:30:32 +01:00
CMakeLists.txt
prj.conf
README.rst	doc: samples: Adopt code-sample-category across tree	2024-09-23 12:00:00 +02:00
sample.yaml

README.rst

.. zephyr:code-sample:: bluetooth_hci_vs_scan_req
   :name: HCI Vendor-Specific Scan Request
   :relevant-api: bluetooth

   Use vendor-specific HCI commands to enable Scan Request events when using legacy advertising.

Overview
********

This simple application is a usage example to manage HCI VS commands to obtain
scan request events even using legacy advertisements, while may result in lower
RAM usage than using extended advertising.
This is quite important in applications in which the broadcaster role is added
to the central role, where the RAM saving can be bigger.
This sample implements only the broadcaster role; the peripheral role with
connection can also be added, depending on configuration choices.

Requirements
************

* A board with Bluetooth LE support
* A central device & monitor (e.g. nRF Connect) to check the advertiments and
  send scan requests.

Building and Running
********************

This sample can be found under :zephyr_file:`samples/bluetooth/hci_vs_scan_req`
in the Zephyr tree.

See :zephyr:code-sample-category:`bluetooth` samples for details.