Skip to content

Commit a1c59ff

Browse files
wiba-nordicnordicjm
authored andcommitted
doc: Update devictree link in include file
The `sample_fem_support.txt` include file links to Zephyr documentation for information on configuring devicetree. This updates the link to point to the Configuring devicetree page in the nRF Connect SDK documentation instead. Also makes other small improvements to the file. Signed-off-by: Wille Backman <[email protected]>
1 parent 0b48922 commit a1c59ff

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

doc/nrf/includes/sample_fem_support.txt

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
You can add support for the nRF21540 front-end module to this sample by using one of the following options, depending on your hardware:
22

33
* Build the sample for one board that contains the nRF21540 FEM, such as :ref:`nrf21540dk/nrf52840 <zephyr:nrf21540dk_nrf52840>`.
4-
* Manually create a devicetree overlay file that describes how FEM is connected to the nRF5 SoC in your device.
5-
See :ref:`zephyr:set-devicetree-overlays` for different ways of adding the overlay file.
6-
* Provide nRF21540 FEM capabilities by using a :ref:`shield <zephyr:shields>`, for example the :ref:`ug_radio_fem_nrf21540ek` shield that is available in the |NCS|.
7-
In this case, build the project for a board connected to the shield you are using with an appropriate variable included in the build command, for example ``SHIELD=nrf21540ek``.
4+
* Manually create a devicetree overlay file that describes how the nRF21540 FEM is connected to the SoC.
5+
See :ref:`configuring_devicetree` for different ways of adding the overlay file.
6+
* Provide nRF21540 FEM capabilities by using a :ref:`shield <zephyr:shields>`, for example the :ref:`nRF21540 EK <ug_radio_fem_nrf21540ek>` shield that is available in the |NCS|.
7+
In this case, build the project for a board connected to the shield you are using with an appropriate variable included in the build command, for example ``-DSHIELD=nrf21540ek``.
88
This variable instructs the build system to append the appropriate devicetree overlay file.
99

1010
.. tabs::
1111

1212
.. group-tab:: nRF Connect for VS Code
1313

14-
To build the sample in the nRF Connect for VS Code IDE for an nRF52840 DK with the nRF21540 EK attached, add the shield variable in the build configuration's :guilabel:`Extra CMake arguments` and rebuild the build configuration.
14+
To build the sample in the |nRFVSC| for an nRF52840 DK with the nRF21540 EK attached, add the shield variable in the build configuration's :guilabel:`Extra CMake arguments` and rebuild the build configuration.
1515
For example: ``-DSHIELD=nrf21540ek``.
1616

17-
See `nRF Connect for VS Code extension pack <How to work with build configurations_>`_ documentation for more information.
17+
See `How to work with build configurations`_ in the |nRFVSC| documentation for more information.
1818

1919
.. group-tab:: Command line
2020

@@ -24,7 +24,7 @@ You can add support for the nRF21540 front-end module to this sample by using on
2424

2525
west build -b nrf52840dk/nrf52840 -- -DSHIELD=nrf21540ek
2626

27-
See :ref:`Programming nRF21540 EK <ug_radio_fem_nrf21540ek_programming>` for information about how to program when you are using a board with a network core, for example nRF5340 DK.
27+
See :ref:`Programming nRF21540 EK <ug_radio_fem_nrf21540ek_programming>` for information about how to program when you are using a board with a network core, for example the nRF5340 DK.
2828

2929
Each of these options adds the description of the nRF21540 FEM to the devicetree.
3030
See :ref:`ug_radio_fem` for more information about FEM in the |NCS|.

0 commit comments

Comments
 (0)