Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

Simonr — Wed, 18 Nov 2020 08:15:33 GMT

I'm sorry, I thought this was done in the config file but it seems I was mistaken when I went to make sure. Please add the following snippet as part of your UART initiatilization code before you enable the UART in order to disable flow control.

struct uart_config cfg;
uart_config_get(uart, &cfg);
cfg.flow_ctrl = UART_CFG_FLOW_CTRL_NONE;
uart_configure(uart,&cfg);

Best regards,

Simon

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

GPereira — Tue, 17 Nov 2020 08:59:57 GMT

Hello, thank you.

Which Kconfig option can I use for that?

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

Simonr — Tue, 17 Nov 2020 08:18:30 GMT

Edvin is on leave for the time being, so I have been tasked with looking after this case in his place. It seems like the correct way of disabling flow control is to do so in your prj.conf file.

Best regards,

Simon

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

GPereira — Fri, 13 Nov 2020 14:43:21 GMT

No it does not work with any sample. Only works on nRF52840 DK but on my device I am not able to use hardware flow control. Any solution? I only need that connection for debugging purposes.

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

Edvin — Wed, 16 Sep 2020 11:55:48 GMT

Ok, I guess you tried this in another example, and it worked? I suspect that it is a bit different in the Openthread examples, because the UART is more heavily weaved into the openthread module. I will have to look more into this.

First: Can you confirm that this works without any issues in a non-thread examples in NCS (nRF Connect SDK)? E.g a hello-world or blinky example, where you don't use flow control on the custom board? Just to check whether this is opnethread related at all.

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

GPereira — Tue, 15 Sep 2020 14:25:07 GMT

&uart0 {
 compatible = "nordic,nrf-uart";
 status = "okay";
 current-speed = <115200>;
 tx-pin = <6>;
 rx-pin = <8>;
};

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

Edvin — Tue, 15 Sep 2020 14:21:48 GMT

How exactly did you change this in your device tree?

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

GPereira — Mon, 14 Sep 2020 14:25:42 GMT

I am describing the UART interface on NCS using device tree. I am declaring my UART pins and I would expect to access zephyr console from that interface. We can put openthread to the side for now since openthread CLI will be on top of that using the ot command.

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

Edvin — Mon, 14 Sep 2020 14:23:21 GMT

Actually, I don't think that openthread is dependent on the LFXTAL. If you want to change something on the UART, you need to rebuild the openthread stack. Please check how to rebuild it, and modify the UART before you build it. Make sure to use the same github tag as the SDK is using. It is mentioned in 4.1.0\external\openthread\project\readme.txt.

Best regards,

Edvin

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

GPereira — Mon, 14 Sep 2020 14:10:55 GMT

How can I define such thing?

RE: Connect UART to J-Link to access OpenThread CLI with nRF Connect SDK

Edvin — Mon, 14 Sep 2020 14:09:09 GMT

[quote user=""]We already tried the blinky example so we have ensured ourr power supply is OK[/quote]

I am not sure exactly how this works in NCS (nRF Connect SDK), but it is a common issue in the nRF5 SDK. Does your custom board have an external LFXTAL? If not, is the application aware of this?

BR,
Edvin