fc6b100bc8
To give control over GPIO pins for Direction Finding Extension of Radio peripheral when build for nRF53 network core, the application core has to assign those pins to network core. There is a mechanism that uses a device tree overlay to get information about GPIO pins to be assigned to network core. The commit adds overlays with appropriate configuration to assign GPIO pins in all DF related samples. Signed-off-by: Piotr Pryga <piotr.pryga@nordicsemi.no>
76 lines
3.0 KiB
ReStructuredText
76 lines
3.0 KiB
ReStructuredText
.. _bluetooth_direction_finding_peripheral:
|
|
|
|
Bluetooth: Direction Finding Peripheral
|
|
#######################################
|
|
|
|
Overview
|
|
********
|
|
|
|
A simple application demonstrating the BLE Direction Finding CTE transmission in
|
|
connected mode by response to a request received from connected peer device.
|
|
|
|
Requirements
|
|
************
|
|
|
|
* Nordic nRF SoC based board with Direction Finding support (example boards:
|
|
:ref:`nrf52833dk_nrf52833`, :ref:`nrf52833dk_nrf52820`, :ref:`nrf5340dk_nrf5340`)
|
|
* Antenna matrix for AoA (optional)
|
|
|
|
Check your SoC's product specification for Direction Finding support if you are
|
|
unsure.
|
|
|
|
Building and Running
|
|
********************
|
|
|
|
By default the application supports Angle of Arrival and Angle of Departure mode.
|
|
|
|
To use Angle of Arrival mode only, build this application as follows,
|
|
changing ``nrf52833dk_nrf52833`` as needed for your board:
|
|
|
|
.. zephyr-app-commands::
|
|
:zephyr-app: samples/bluetooth/direction_finding_peripheral
|
|
:host-os: unix
|
|
:board: nrf52833dk_nrf52833
|
|
:gen-args: -DOVERLAY_CONFIG=overlay-aoa.conf
|
|
:goals: build flash
|
|
:compact:
|
|
|
|
To run the application on nRF5340DK, a Bluetooth controller application must
|
|
also run on the network core. The :ref:`bluetooth-hci-rpmsg-sample` sample
|
|
application may be used. To build this sample with direction finding support
|
|
enabled:
|
|
|
|
* Copy
|
|
:zephyr_file:`samples/bluetooth/direction_finding_peripheral/boards/nrf52833dk_nrf52833.overlay`
|
|
to a new file,
|
|
:file:`samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.overlay`.
|
|
* Make sure the same GPIO pins are assigned to Direction Finding Extension in file
|
|
:zephyr_file:`samples/bluetooth/direction_finding_peripheral/boards/nrf5340dk_nrf5340_cpuapp.overlay`.
|
|
as those in the created file :file:`samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.overlay`.
|
|
* Copy
|
|
:zephyr_file:`samples/bluetooth/direction_finding_peripheral/boards/nrf52833dk_nrf52833.conf`
|
|
to a new file,
|
|
:file:`samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.conf`.
|
|
|
|
Antenna matrix configuration
|
|
****************************
|
|
|
|
To use this sample with Angle of Departure enabled on Nordic SoCs, additional
|
|
configuration must be provided via :ref:`devicetree <dt-guide>` to enable
|
|
control of the antenna array.
|
|
|
|
An example devicetree overlay is in
|
|
:zephyr_file:`samples/bluetooth/direction_finding_peripheral/boards/nrf52833dk_nrf52833.overlay`.
|
|
You can customize this overlay when building for the same board, or create your
|
|
own board-specific overlay in the same directory for a different board. See
|
|
:dtcompatible:`nordic,nrf-radio` for documentation on the properties used in
|
|
this overlay. See :ref:`set-devicetree-overlays` for information on setting up
|
|
and using overlays.
|
|
|
|
Note that antenna matrix configuration for the nRF5340 SoC is part of the
|
|
network core application. When :ref:`bluetooth-hci-rpmsg-sample` is used as the
|
|
network core application, the antenna matrix configuration should be stored in
|
|
the file
|
|
:file:`samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.overlay`
|
|
instead.
|