zephyr/samples/bluetooth/hci_rpmsg
Piotr Pryga a0a8a12642 Bluetooth: hci: Use extended VS fatal error in hci and hci_rpmsg sample
Provide common helper functions to create extended extended Zephyr
Fatal Error functionality in HCI common code.

Use the implementation in hci_rpmsg sample.

The sample didn't provide an information about Controllers assert
or system fatal error to an application code while run with nRF5340
SoC. The goal for hci_rpmsg sample change is to enhance user experience
for conformance testing of the Bluetooth Controller while executed with
nRF5340.

Signed-off-by: Piotr Pryga <piotr.pryga@nordicsemi.no>
2022-08-02 13:53:32 +02:00
..
src Bluetooth: hci: Use extended VS fatal error in hci and hci_rpmsg sample 2022-08-02 13:53:32 +02:00
CMakeLists.txt cmake: increase minimal required version to 3.20.0 2021-08-20 09:47:34 +02:00
debug_overlay.conf samples: hci_rpmsg: Use release configuration by default 2021-07-22 22:42:22 +03:00
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
README.rst doc: use :kconfig:option: domain role 2022-03-02 09:28:37 +01:00
sample.yaml samples: Bluetooth: hci_rpmsg: Fix Broadcast and Sync Receiver prj conf 2022-04-29 08:57:02 +02:00

.. _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.