Why is NRF_LOG_DEFAULT_BACKENDS_INIT causing INVALID_STATE error when calling nrf_cli_init?

[Dusan Daniska]

I tried to use UART both for NRF_LOG and NRF_CLI. Now it's running but I had a problem that calling to nrf_cli_init caused fatal error 8 - INVALID_STATE.

When I commented out the NRF_LOG_DEFAULT_BACKENDS_INIT, the error disappeared and now both LOG and CLI are working.

Why?

[FormerMember]

NRF_CLI_UART_xxx sets the settings for enabling logging in the CLI module. You will also need the following to enable the command line interface and the log module:

 

Enabling the settings NRF_CLI_LOG_BACKEND and NRF_LOG_CLI_CMDS are important to for the CLI module and the LOG module to co-exist.

[Dusan Daniska]

I have also NRF_CLI_LOG_BACKEND enabled, just missed in the list in the previous reply. I'd like to remind that currently I can run both NRF_LOG and NRF_CLI but I had to comment out the NRF_LOG_DEFAULT_BACKENDS_INIT() macro and I am wondering why. And if this can cause some problems in the future.

[Jakub Rzeszutko]

Hi,

nrf_cli_init is initializing UART driver and the same is doing macro NRF_LOG_DEFAULT_BACKENDS_INIT().

If you try to initialize already initialized driver you will have an error code message about invalid state.

When using CLI you don't need to call macro NRF_LOG_DEFAULT_BACKENDS_INIT() and you shall not expect any errors in the future related with this.

[Dusan Daniska]

Thank you for the explanation. I would recommend to update the docs somehow to avoid such misunderstanding by another new developers.