Skip to content

Commit 6b28fe6

Browse files
Damian-Nordicrlubos
authored andcommitted
samples: protocols_serialization: use different GPIO pins of UART
One of the previously selected pins for uart21 peripheral was also used to drive LED 1 on nRF54L15 DK, which might have interferred with the UART hardware flow control. Due to lack of available pins on GPIO port 1, use the pins dedicated to Button 1 & 2 but make sure that the buttons are removed from the devicetree to prevent from using them accidentally. Also, fix pull-up configuration for UART pins. Signed-off-by: Damian Krolik <[email protected]>
1 parent 33524e9 commit 6b28fe6

File tree

13 files changed

+87
-88
lines changed

13 files changed

+87
-88
lines changed

CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -274,7 +274,7 @@
274274

275275
/doc/**/*.svg @nrfconnect/ncs-doc-leads
276276
/doc/**/*.png @nrfconnect/ncs-doc-leads
277-
277+
/doc/**/*.webp @nrfconnect/ncs-doc-leads
278278

279279
# Drivers
280280
/drivers/bluetooth/ @nrfconnect/ncs-co-drivers @nrfconnect/ncs-dragoon
-175 KB
Binary file not shown.
61.5 KB
Loading

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -350,7 +350,8 @@ PMIC samples
350350
Protocol serialization samples
351351
------------------------------
352352

353-
|no_changes_yet_note|
353+
* Updated GPIO pins on nRF54L15 DK used for communication between the client and server over UART.
354+
One of the previously selected pins was also used to drive an LED, which may have disrupted the UART communication.
354355

355356
SDFW samples
356357
------------

samples/nrf_rpc/protocols_serialization/client/README.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,10 @@ Testing
6565

6666
To test the client sample, follow the instructions in the :ref:`protocols_serialization_server_sample_testing` section of the protocol serialization server sample test procedure.
6767

68+
.. note::
69+
When using the nRF54L15 DK, do not press **Button 1** or **Button 2**.
70+
The GPIO pins connected to these buttons are used by the UART peripheral for communication with the server device.
71+
6872
Dependencies
6973
************
7074

samples/nrf_rpc/protocols_serialization/client/boards/nrf52840dk_nrf52840.overlay

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,14 @@
1717

1818
&uart1_default {
1919
group1 {
20-
psels = <NRF_PSEL(UART_RX, 1, 1)>,
21-
<NRF_PSEL(UART_RTS, 1, 3)>;
22-
bias-pull-up;
23-
};
24-
group2 {
2520
psels = <NRF_PSEL(UART_TX, 1, 2)>,
21+
<NRF_PSEL(UART_RTS, 1, 3)>,
2622
<NRF_PSEL(UART_CTS, 1, 4)>;
2723
};
24+
group2 {
25+
psels = <NRF_PSEL(UART_RX, 1, 1)>;
26+
bias-pull-up;
27+
};
2828
};
2929

3030
&uart1_sleep {

samples/nrf_rpc/protocols_serialization/client/boards/nrf54l15dk_nrf54l15_cpuapp.overlay

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,28 +7,38 @@
77
chosen {
88
nordic,rpc-uart = &uart21;
99
};
10+
11+
/* delete all buttons except button0 to free GPIO pins assigned to uart21 below */
12+
buttons {
13+
/delete-node/ button1;
14+
/delete-node/ button2;
15+
/delete-node/ button3;
16+
};
1017
};
1118

1219
&pinctrl {
1320
uart21_default: uart21_default {
1421
group1 {
15-
psels = <NRF_PSEL(UART_TX, 1, 11)>,
16-
<NRF_PSEL(UART_RX, 1, 10)>,
17-
<NRF_PSEL(UART_RTS, 1, 12)>,
18-
<NRF_PSEL(UART_CTS, 1, 13)>;
22+
psels = <NRF_PSEL(UART_TX, 1, 8)>,
23+
<NRF_PSEL(UART_RTS, 1, 11)>,
24+
<NRF_PSEL(UART_CTS, 1, 12)>;
25+
};
26+
group2 {
27+
28+
psels = <NRF_PSEL(UART_RX, 1, 9)>;
29+
bias-pull-up;
1930
};
2031
};
2132

2233
uart21_sleep: uart21_sleep {
2334
group1 {
24-
psels = <NRF_PSEL(UART_TX, 1, 11)>,
25-
<NRF_PSEL(UART_RX, 1, 10)>,
26-
<NRF_PSEL(UART_RTS, 1, 12)>,
27-
<NRF_PSEL(UART_CTS, 1, 13)>;
35+
psels = <NRF_PSEL(UART_TX, 1, 8)>,
36+
<NRF_PSEL(UART_RX, 1, 9)>,
37+
<NRF_PSEL(UART_RTS, 1, 11)>,
38+
<NRF_PSEL(UART_CTS, 1, 12)>;
2839
low-power-enable;
2940
};
3041
};
31-
3242
};
3343

3444
&uart21 {

samples/nrf_rpc/protocols_serialization/server/Kconfig

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,7 @@ endif
3838

3939
config NRF_PS_SERVER_FATAL_ERROR_TRIGGER
4040
bool "Fatal error trigger"
41+
select DK_LIBRARY
4142
help
4243
Enables triggering a fatal error by pressing Button 1 on the development
4344
kit. This trigger allows for testing the feature of logging over RPC that

samples/nrf_rpc/protocols_serialization/server/README.rst

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -52,15 +52,19 @@ User interface
5252
**************
5353

5454
.. tabs::
55+
5556
.. group-tab:: nRF52840 DK
5657

57-
Button 4:
58+
Button 1:
59+
5860
* When the ``log_rpc`` snippet is enabled: triggers a fatal error.
59-
This is used for testing the crash log feature.
61+
This is used for testing the crash log feature.
6062
* Otherwise: not available.
6163

6264
.. group-tab:: nRF54L15 DK
63-
Button 3:
65+
66+
Button 0:
67+
6468
* When the ``log_rpc`` snippet is enabled: triggers a fatal error.
6569
This is used for testing the crash log feature.
6670
* Otherwise: not available.
@@ -81,6 +85,10 @@ Testing
8185

8286
After building the Protocols serialization server sample and programming it to your development kit, connect it to a second device running the :ref:`Protocol serialization client <nrf_rpc_protocols_serialization_client>` sample to test either the Bluetooth LE, OpenThread or NFC functionality.
8387

88+
.. note::
89+
When using the nRF54L15 DK, do not press **Button 1** or **Button 2**.
90+
The GPIO pins connected to these buttons are used by the UART peripheral for communication with the client device.
91+
8492
.. _protocols_serialization_server_app_connection:
8593

8694
Connecting the client and server samples
@@ -137,17 +145,17 @@ In the protocols serialization samples, one peripheral is used for shell and log
137145
* - Server
138146
- Client
139147
- Function on server
140-
* - **P1.10**
141-
- **P1.11**
142-
- RX
143-
* - **P1.11**
144-
- **P1.10**
148+
* - **P1.8**
149+
- **P1.9**
145150
- TX
146-
* - **P1.12**
147-
- **P1.13**
148-
- RTS (hardware flow control)
149-
* - **P1.13**
151+
* - **P1.9**
152+
- **P1.8**
153+
- TX
154+
* - **P1.11**
150155
- **P1.12**
156+
- RTS (hardware flow control)
157+
* - **P1.12**
158+
- **P1.11**
151159
- CTS (hardware flow control)
152160
* - **GND**
153161
- **GND**
@@ -156,7 +164,7 @@ In the protocols serialization samples, one peripheral is used for shell and log
156164
To enable the communication between the client and the server devices, connect the pins on the two nRF54L15 DKs using jumper wires.
157165
The following illustration demonstrates the pin connections:
158166

159-
.. figure:: /images/ps_nrf54l_connections.png
167+
.. figure:: /images/ps_nrf54l_connections.webp
160168
:alt: nRF54L15 DK server and client pin connections
161169

162170
Testing Bluetooth LE API serialization

samples/nrf_rpc/protocols_serialization/server/boards/nrf52840dk_nrf52840.overlay

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,14 @@
1717

1818
&uart1_default {
1919
group1 {
20-
psels = <NRF_PSEL(UART_RX, 1, 1)>,
21-
<NRF_PSEL(UART_RTS, 1, 3)>;
22-
bias-pull-up;
23-
};
24-
group2 {
2520
psels = <NRF_PSEL(UART_TX, 1, 2)>,
21+
<NRF_PSEL(UART_RTS, 1, 3)>,
2622
<NRF_PSEL(UART_CTS, 1, 4)>;
2723
};
24+
group2 {
25+
psels = <NRF_PSEL(UART_RX, 1, 1)>;
26+
bias-pull-up;
27+
};
2828
};
2929

3030
&uart1_sleep {

0 commit comments

Comments
 (0)