mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 03:35:19 +00:00
689bd232f8
In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| 96b_nitrogen.overlay | ||
| generic.conf | ||
| Makefile | ||
| microbit.conf | ||
| nrf5.conf | ||
| nrf51_blenano.overlay | ||
| nrf51_pca10028.overlay | ||
| nrf52_blenano2.overlay | ||
| nrf52_pca10040.overlay | ||
| nrf52840_pca10056.overlay | ||
| README.rst | ||
| testcase.ini | ||
.. _bluetooth-hci-uart-sample: Bluetooth: HCI UART #################### Overview ********* Expose Zephyr Bluetooth Controller support over UART to another device/CPU using the H:4 HCI transport protocol (requires HW flow control from the UART) Requirements ************ * BlueZ running on the host, or * A board with BLE support Building and Running ******************** This sample can be found under :file:`samples/bluetooth/hci_uart` in the Zephyr tree. See :ref:`bluetooth setup section <bluetooth_setup>` for details.