Skip to content

doc: fix NCP sample UART pinout configuration #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edmont merged 1 commit into from
Sep 3, 2025
Merged

doc: fix NCP sample UART pinout configuration #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 23 additions & 7 deletions samples/ncp/README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,13 +77,13 @@ The communication channel uses Zephyr's `UART API`_.
ncs,zigbee-uart = &uart20;
};

By default, Zephyr's logger uses ``uart20`` and the NCP sample communicates through the UART serialization using ``uart21``.
The DTS overlay file configures ``uart21`` to be connected to the on-board J-Link instead of ``uart20``.
As the result, Zephyr's logger ``uart20`` is available only through GPIO pins (**P1.08** and **P1.09**).
By default, Zephyr's logger uses ``uart20``, and the NCP sample communicates through the UART serialization using ``uart21``.
The DTS overlay file configures ``uart21`` to connect to the on-board J-Link instead of ``uart20``.
As a result, Zephyr's logger on ``uart20`` is available only through GPIO pins (**P1.08** and **P1.09**).

The ``uart20`` pins are configured by devicetree overlay files for each supported development kit in the :file:`boards` directory.

.. group-tab:: nRF52840 and nRF5340 DKs
.. group-tab:: nRF5340 DK

The serial device is selected in devicetree like this:

Expand All @@ -93,9 +93,25 @@ The communication channel uses Zephyr's `UART API`_.
ncs,zigbee-uart = &uart0;
};

By default, Zephyr's logger uses ``uart0`` and the NCP sample communicates through the UART serialization using ``uart1``.
The DTS overlay file configures ``uart1`` to be connected to the on-board J-Link instead of ``uart0``.
As the result, Zephyr's logger ``uart0`` is available only through GPIO pins (**P1.00** and **P1.01**).
By default, Zephyr's logger uses ``uart0``, and the NCP sample communicates through the UART serialization using ``uart1``.
The DTS overlay file configures ``uart1`` to connect to the on-board J-Link instead of ``uart0``.
As a result, Zephyr's logger on ``uart0`` is available only through GPIO pins (**P1.04** and **P1.05**).

The ``uart0`` pins are configured by devicetree overlay files for each supported development kit in the :file:`boards` directory.

.. group-tab:: nRF52840 DK

The serial device is selected in the following devicetree:

.. code-block:: devicetree

chosen {
ncs,zigbee-uart = &uart0;
};

By default, Zephyr's logger uses ``uart0``, and the NCP sample communicates through the UART serialization using ``uart1``.
The DTS overlay file configures ``uart1`` to connect to the on-board J-Link instead of ``uart0``.
As a result, Zephyr's logger on ``uart0`` is available only through GPIO pins (**P1.01** and **P1.02**).

The ``uart0`` pins are configured by devicetree overlay files for each supported development kit in the :file:`boards` directory.

Expand Down