NRF CLI Thread Safe?

RE: NRF CLI Thread Safe?

Jakub Rzeszutko — Tue, 12 Mar 2019 21:33:19 GMT

With SDK15.3 this will not matter - both will work fine. I've simplified it.

RE: NRF CLI Thread Safe?

Dave_couling — Tue, 12 Mar 2019 19:52:21 GMT

Issue was using '\n' instead of '\r' in the Definition macro

NRF_CLI_DEF(m_cli_uart,
CLI_UART_PREFIX,
&m_cli_uart_transport.transport,
'\r',
CLI_LOG_QUEUE_SIZE);

RE: NRF CLI Thread Safe?

Jakub Rzeszutko — Wed, 27 Feb 2019 07:53:05 GMT

I did not face this problem so it is hard to comment. Are you able to share some code where I could reproduce it?

RE: NRF CLI Thread Safe?

Dave_couling — Mon, 25 Feb 2019 22:21:01 GMT

Wanted to re-address this issue. I've been finding with extensive testing that the CLI module will randomly assert. If occurs on line 270 of nrfx_uarte.c results from a NULL pointer passed for p_data. This seems to occur randomly, whether the Softdevice/BLE Thread is running or not. The Thread trace shows the following:

RE: NRF CLI Thread Safe?

Jakub Rzeszutko — Thu, 03 Jan 2019 23:36:03 GMT

You are allowed to use a backend for both. Example can be found in peripherals\cli

RE: NRF CLI Thread Safe?

Dave_couling — Thu, 03 Jan 2019 20:44:34 GMT

I thought you weren't allowed to use a backend for both logging and cli. I guess this is where you'd set the #define NRF_CLI_LOG_BACKEND 1 ? To be able to use Logging -> thur CLI -> to whatever backend is configured for CLI (e.g. RTT or UART)?

RE: NRF CLI Thread Safe?

Jakub Rzeszutko — Thu, 03 Jan 2019 12:27:40 GMT

You can create as many CLI backends as possible: BT, UART0/UARTE0, UARTE1 (nrf52840), RTT or USB.

Each backend is independant and you can use them "at the same time". Each CLI backend can be at the same time a Logger backend. What is more you can configure each backend to show different log levels and it can be changed at runtime.

So I think the answer for your question is simply: yes.

RE: NRF CLI Thread Safe?

Dave_couling — Wed, 02 Jan 2019 22:24:41 GMT

1. Understood, I'll wrap this into its own thread with a Semaphore

2. The usage of the term backend is quite confusing. I use RTT backend on my CLI (may change to UART depending on the application). So as I understand, there is a setting which hooked the Logging into the CLI as the backend which then uses whatever backend is configured for the CLI?

RE: NRF CLI Thread Safe?

Jakub Rzeszutko — Tue, 01 Jan 2019 19:03:35 GMT

Basically it is not thread safe. However you can safely use it with RTOS under following conditions:

1. CLI commands will be not executed from from multiple contexts (to avoid executing commands at the same time).

2. nrf_cli_fprintf function will be used only inside command handler. If you wish to print something on the screen from different context you can use Logger module with CLI backend.