zephyr

History

Kamil Piszczek d87552a128 drivers: bluetooth: hci: rpmsg: use chosen to abstract ipc instance Added chosen syntax in Device Tree to abstract the IPC device that is used with the IPC service module in the Bluetooth HCI RPMsg driver. Ported affected boards to declare this alias. Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>		2022-05-06 14:15:27 +02:00
..
src	drivers: bluetooth: hci: rpmsg: use chosen to abstract ipc instance	2022-05-06 14:15:27 +02:00
CMakeLists.txt	…
README.rst	doc: use :kconfig:option: domain role	2022-03-02 09:28:37 +01:00
debug_overlay.conf	…
nrf5340_cpunet_iso_broadcast.conf	samples: Bluetooth: hci_rpmsg: Fix Broadcast and Sync Receiver prj conf	2022-04-29 08:57:02 +02:00
nrf5340_cpunet_iso_receive.conf	samples: Bluetooth: hci_rpmsg: Fix Broadcast and Sync Receiver prj conf	2022-04-29 08:57:02 +02:00
prj.conf	samples: Bluetooth: hci_rpmsg: Fix Broadcast and Sync Receiver prj conf	2022-04-29 08:57:02 +02:00
sample.yaml	samples: Bluetooth: hci_rpmsg: Fix Broadcast and Sync Receiver prj conf	2022-04-29 08:57:02 +02:00

README.rst

.. _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_api` 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
:kconfig: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, :kconfig: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.