You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit itroduces documentation for the
nRF21540 EK shield.
Signed-off-by: Kamil Gawor <[email protected]>
Signed-off-by: Mia Koen <[email protected]>
Copy file name to clipboardExpand all lines: doc/nrf/ug_radio_fem.rst
+88-3Lines changed: 88 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,6 @@ These methods are only available to protocol drivers that are using FEM features
24
24
They are also valid for cases where an application uses just one protocol, but benefits from features provided by MPSL.
25
25
To avoid conflicts, check the protocol documentation to see if it uses FEM support provided by MPSL.
26
26
27
-
Work is underway to make the protocols shipped with |NCS| use FEM.
28
-
At the moment, :ref:`ug_thread` and :ref:`ug_zigbee` support the :ref:`nRF21540 DK <nrf21540dk_nrf52840>` and the nRF21540 EK for nRF52 Series devices, but there is no multiprotocol support or support for nRF5340 yet.
29
-
30
27
|NCS| provides a friendly wrapper that configures FEM based on devicetree (DTS) and Kconfig information.
31
28
To enable FEM support, you must enable FEM and MPSL, and add an ``nrf_radio_fem`` node in the devicetree file.
32
29
The node can also be provided by the devicetree file of the target devkit or by an overlay file.
@@ -191,3 +188,91 @@ Then there is no need to define a GPIO to control the PDN signal. The line ``pdn
191
188
192
189
Generally, if pin ``X`` is not used, the ``X-gpios = < .. >;`` property can be removed.
193
190
This applies to all properties with a ``-gpios`` suffix, for both nRF21540 and SKY66112-11.
191
+
192
+
.. _ug_radio_fem_boards:
193
+
194
+
Supported boards
195
+
****************
196
+
197
+
Two nRF21540 boards are available, showcasing the possibilities of the nRF21540 FEM:
198
+
199
+
* :ref:`nRF21540 DK <nrf21540dk_nrf52840>`
200
+
* nRF21540 EK, described in sections below
201
+
202
+
While the front-end module feature is supported on the nRF52 Series, it is yet not supported on the nRF53 Series.
203
+
Work is underway to make the protocols shipped with |NCS| use FEM.
204
+
At the moment, :ref:`ug_thread` and :ref:`ug_zigbee` support both the nRF21540 DK and the nRF21540 EK for the nRF52 Series devices.
205
+
206
+
.. _ug_radio_fem_nrf21540_ek:
207
+
208
+
nRF21540 EK
209
+
===========
210
+
211
+
The nRF21540 EK (Evaluation Kit) is an RF front-end module (FEM) for Bluetooth Low Energy, Bluetooth mesh, 2.4 GHz proprietary, Thread, and Zigbee range extension.
212
+
When combined with an nRF52 or nRF53 Series SoC, the nRF21540 RF FEM’s +21 dBm TX output power and 13 dB RX gain ensure a superior link budget for up to 16x range extension.
213
+
214
+
Overview
215
+
--------
216
+
217
+
The nRF21540 complementary device has a 50 Ω SMA transceiver interface and 2x 50 Ω SMA antenna interfaces.
218
+
This enables connecting an SoC or a signal generator to the input.
219
+
It also enables connecting the outputs to measurement tools or to antennas directly.
220
+
The FEM can be configured through the pins available on the Arduino headers.
221
+
222
+
The nRF21540's gain control, antenna switching, and modes are controlled via GPIO or SPI, or a combination of both.
223
+
GPIO and SPI are accessible through the Arduino Uno Rev3 compatible headers.
224
+
The shield also features two additional SMA connectors hooked to the dual antenna ports from the RF FEM, to monitor the performance of the RF FEM using any equipment desired.
225
+
The FEM SMA input can be connected to the nRF52 or nRF53 Series SoC RF output with a coaxial RF cable with SMA\SWF connectors.
0 commit comments