ea04fd95f9
Enforcing the peer's behavior is not strictly necessary. All the host should do is make sure it is resilient to a spec-violating peer. Moreover, a growing number of platforms were disabling the check, as the spec allows "batching" HCI num complete packets events, stalling ATT RX. Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no> Co-authored-by: Aleksander Wasaznik <aleksander.wasaznik@nordicsemi.no> |
||
---|---|---|
.. | ||
boards | ||
src | ||
CMakeLists.txt | ||
Kconfig | ||
prj.conf | ||
README.rst | ||
sample.yaml |
.. _peripheral_ht: Bluetooth: Peripheral HT ######################## Overview ******** Similar to the :ref:`Peripheral <ble_peripheral>` sample, except that this application specifically exposes the HT (Health Thermometer) GATT Service. On Nordic nRF devices, this sample uses the built-in TEMP peripheral to return die temperature values. On other boards, it will generate dummy temperature values. Requirements ************ * BlueZ running on the host, or * A board with BLE support Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/peripheral_ht` in the Zephyr tree. See :ref:`bluetooth samples section <bluetooth-samples>` for details.