eddac27c4e
These samples were enabled for an nRF board, even though there is no upstream support for the feature. Additionally the sample.yaml files were forcefully disabling any in-tree HCI drivers, making it impossible to use e.g. qemu with an external HCI controller. Simply remove the nRF board from the list, as well as the odd Kconfig HCI driver options. Signed-off-by: Johan Hedberg <johan.hedberg@gmail.com> |
||
---|---|---|
.. | ||
src | ||
CMakeLists.txt | ||
prj.conf | ||
README.rst | ||
sample.yaml |
.. _bluetooth-periodic-advertising-rsp-sample: Bluetooth: Periodic Advertising with Responses (PAwR) Advertiser ################################################################ Overview ******** A simple application demonstrating the BLE Periodic Advertising with Responses Advertiser functionality. This sample will scan for the corresponding sync sample and send the required synchronization info to it. The advertising data is a counter that increases for each subevent. Multiple devices can synchronize and respond to one advertiser. Which subevent to listen to and in which response slot to respond is application specific. In this sample it is decided by the PAwR advertiser. Upon connection it will write to a GATT characteristic the assigned subevent and response slot. Requirements ************ * A board with BLE support * A controller that supports the Periodic Advertising with Responses (PAwR) - Advertiser feature Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/periodic_adv_rsp` in the Zephyr tree. Use the sample found under :zephyr_file:`samples/bluetooth/periodic_sync_rsp` in the Zephyr tree that will synchronize and respond to this sample. See :ref:`bluetooth samples section <bluetooth-samples>` for details.