mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-08 15:31:55 +00:00
5e486b98b1
The build infrastructure should not be adding the drivers subdirectory to the include path. Fix the legacy uses that depended on that addition. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _bluetooth-hci-rpmsg-sample: Bluetooth: HCI RPMsg #################### Overview ******** This sample exposes :ref:`bluetooth_controller` support to another device or CPU using RPMsg transport which is a part of `OpenAMP <https://github.com/OpenAMP/open-amp/>`__. Requirements ************ * A board with :ref:`ipm_interface` driver and Bluetooth LE support Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/hci_rpmsg` in the Zephyr tree. To use this application, you need a board with a Bluetooth controller and IPM drivers. You can then build this application and flash it onto your board in the usual way. See :ref:`boards` for board-specific building and programming information. To test this sample, you need a separate device/CPU that acts as Bluetooth HCI RPMsg peer. This sample is compatible with the HCI RPMsg driver provided by Zephyr's Bluetooth :ref:`bt_hci_drivers` core. See the :option:`CONFIG_BT_RPMSG` configuration option for more information. You might need to adjust the Kconfig configuration of this sample to make it compatible with the peer application. For example, :option:`CONFIG_BT_MAX_CONN` must be equal to the maximum number of connections supported by the peer application. Refer to :ref:`bluetooth-samples` for general information about Bluetooth samples.