Add own backend interface to the logger failed

RE: Add own backend interface to the logger failed

Edvin — Tue, 03 Sep 2019 09:18:48 GMT

It is probably possible to use the UART for logging and application, but that is not something that our SDK supports. The issue is that you try to initialize the UART twice. I suggest you use the RTT backend for your logging, and use the JLink RTT Viewer to monitor this log, to save you some trouble.

8 means NRF_ERROR_INVALID_STATE, which is returned because the uart is already initialized. I don't know whether you use the same uart instance and the same pins for your custom UART, or whether you are aware that only one uart instance can be used at the time, not both.

If you try to use the same instance, but with two uartHandlers, I suggest you use only one handler, which also calls the second.

But again, if this is only for log monitoring during development, I recommend that you save yourself some trouble and use the RTT backend.

RE: Add own backend interface to the logger failed

awneil — Mon, 02 Sep 2019 14:34:54 GMT

[quote userid="82935" url="~/f/nordic-q-a/51566/add-own-backend-interface-to-the-logger-failed/207437"]I have only a Make project and no SES or Keil project to debug step by step[/quote]

It is, of course, perfectly possible to debug on the command line - if that's your thing.

RE: Add own backend interface to the logger failed

ManuelF — Mon, 02 Sep 2019 14:05:31 GMT

I try to implement a UART backend for the logger, but with custom functions. This because I add some data to indentify these messages as log messages. The UART is additionaly used for sending commands.
I figured out, that there is a problem with my uartInit(). I took the example ble_app_hrs and added my uart communication. As soon as I call my uartInit() the example, I get error code 0x08 on APP_UART_FIFO_INIT() call. But how do I init the uart to get the uartHandler?

// UART
#define UART_TX_BUF_SIZE                  512
#define UART_RX_BUF_SIZE                  1024

typedef uint16_t uarttMessageLength_t;
typedef void (* uartMessageHandler_t) (const uint8_t * data, uarttMessageLength_t length);

/*
 * @brief Sends the specified data to the uart port.
 */
bool uartSendMessage(const void * data, uarttMessageLength_t length)
{
   //send uart data
   return true;
}

/*
 * @brief The uart messages flow.
 */
void onUartMessage(const uint8_t * data, uint16_t length)
{
   NRF_LOG_HEXDUMP_DEBUG(data, length);
}

/*
 * @brief The UART communication callback.
 */
void onUartEvent(app_uart_evt_t * p_event)
{
   switch (p_event->evt_type)
   {
      case APP_UART_DATA:
         break;

      case APP_UART_DATA_READY:
         break;

      case APP_UART_COMMUNICATION_ERROR:
         APP_ERROR_HANDLER(p_event->data.error_communication);
         break;

      case APP_UART_FIFO_ERROR:
         APP_ERROR_HANDLER(p_event->data.error_code);
         break;

      default:
         break;
    }
}

void uartInit(uartMessageHandler_t uartMessageHandler)
{

   const app_uart_comm_params_t comm_params =
   {
      .rx_pin_no    = 5,
      .tx_pin_no    = 6,
      .rts_pin_no   = 31,
      .cts_pin_no   = 7,
      .flow_control = APP_UART_FLOW_CONTROL_DISABLED,
      .use_parity   = false,
      .baud_rate    = UART_BAUDRATE_BAUDRATE_Baud115200
   };

   uint32_t result;
   APP_UART_FIFO_INIT(& comm_params,
                      UART_RX_BUF_SIZE,
                      UART_TX_BUF_SIZE,
                      onUartEvent,
                      APP_IRQ_PRIORITY_LOWEST,
                      result);
   APP_ERROR_CHECK(result);
}



/**@brief Function for application main entry.
 */
int main(void)
{
    bool erase_bonds;

    // Initialize.
    uartInit(& onUartMessage);
    log_init();
    timers_init();
    buttons_leds_init(&erase_bonds);
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    advertising_init();
    services_init();
    sensor_simulator_init();
    conn_params_init();
    peer_manager_init();

    // Start execution.
    NRF_LOG_INFO("Heart Rate Sensor example started.");
    application_timers_start();
    advertising_start(erase_bonds);

    // Enter main loop.
    for (;;)
    {
        idle_state_handle();
    }
}

awneil: Unfortunately I have only a Make project and no SES or Keil project to debug step by step.

RE: Add own backend interface to the logger failed

Edvin — Fri, 30 Aug 2019 08:45:03 GMT

Hello,

Are you trying to implement a UART backend for the logger?

If so, I suggest you take a look at one of the examples that has the option for UART backend in the NRF_LOG module, such as the ble_app_hrs example.

Other than that I don't know what the issue is, I see a lot of empty functions in your snippets. Is the plan to populate them?

RE: Add own backend interface to the logger failed

awneil — Thu, 29 Aug 2019 15:09:16 GMT

[quote userid="82935" url="~/f/nordic-q-a/51566/add-own-backend-interface-to-the-logger-failed"]I seems the software is "stuck" somewhere[/quote]

So have you used the debugger to find where it's stuck?