HCI Vendor-Specific Scan Request
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 running Zephyr’s built-in Bluetooth LE controller (requires Zephyr-specific HCI vendor extensions; external HCI controllers are not supported)
A central device & monitor (e.g. nRF Connect) to check the advertisements and send scan requests.
Building and Running
Build and flash the sample as follows, replacing <board> with your target board:
west build -b <board> samples/bluetooth/hci_vs_scan_req
west flash
After flashing, the sample starts advertising. Use a Bluetooth LE central device (e.g. a smartphone with nRF Connect) with active scanning enabled to scan for the device and trigger scan requests. Observe the scan request events reported in the console output.