RE: Exit CLI and start Logging

Vidar Berg — Thu, 10 Dec 2020 14:00:53 GMT

Thanks for uploading a project demonstrating the issue, and sorry for the delayed response.

It took me a while to narrow down the problem. Turns out the UARTE keeps triggering the NRF_DRV_UART_EVT_ERROR event even though the logger backend is initializing UARTE in TX only mode. This is a problem because it causes the "m_xfer_done" in nrf_log_backend_uart.c:uart_evt_handler() to always be set to 'true', which again causes the blocking serial_tx() function to become non-blocking.

I do not know why the ERROR events are raised. It is strange considering the receiver is not enabled. The nrf_cli_uninit() function is also disabling UARTE as a part its uninit routine. I was however able to work around the problem by power-cycling the peripheral it before it was re-enabled by the logger backend again. Could you please try the same?

    ret = nrf_cli_stop(&m_cli_uart);
    APP_ERROR_CHECK(ret);

    ret = nrf_cli_uninit(&m_cli_uart);
    APP_ERROR_CHECK(ret);
    
    *(volatile uint32_t *)(NRF_UART0_BASE + 0xFFC) = 0; // Workaround: power-cycle peripheral to make sure it is fully reset. 
    *(volatile uint32_t *)(NRF_UART0_BASE + 0xFFC) = 1;
    nrf_delay_ms(500);
#endif
    NRF_LOG_INIT(NULL);
    NRF_LOG_DEFAULT_BACKENDS_INIT();  //need to init log backend after un-initting CLI
    NRF_LOG_INFO("CLI exit complete.");
    NRF_LOG_FLUSH();

Best regards,

Vidar

RE: Exit CLI and start Logging

cbrown_cdi — Wed, 09 Dec 2020 18:22:48 GMT

In the example project, send the command "exit" to exit manufacturing mode and continue onto the main program where the logging module is used.