Command line tracing in Ubuntu

RE: Command line tracing in Ubuntu

Matts — Thu, 31 Mar 2016 12:57:59 GMT

Now it works. const app_uart_comm_params_t comm_params = { RX_PIN_NUMBER, TX_PIN_NUMBER, RTS_PIN_NUMBER, CTS_PIN_NUMBER, APP_UART_FLOW_CONTROL_ENABLED, false, UART_BAUDRATE_BAUDRATE_Baud115200 };

And the main thing was to change the tx buffer size in the file to 2k. apparently the whole system outputs so much trace that it overflows.

RE: Command line tracing in Ubuntu

Matts — Thu, 31 Mar 2016 12:42:54 GMT

To continue my monolog:

I managed to get some life out of the tracing (altough still not working properly).

By adding few makefile flags: CFLAGS += -DBSP_UART_SUPPORT CFLAGS += -DENABLE_DEBUG_LOG_SUPPORT (originally I just removed the #ifdef from the app_trace.h & c)

Also -replaced uart_app.c with uart_app_fifo.c -added INC_PATHS += -I../config/uart_pca10036 -added INC_PATHS += -I../components/libraries/uart

After this I get trace calls from main loop (this is trace & debugger modified version of ble alert notification example) with 2,5 sec delay: for (;;) { printf("\n looping\n\r"); nrf_delay_ms(2500); power_manage(); }

And in terminal: looping looping looping

However if button is pressed (i added only extra traces there) it all goes bad:

" ��"

Is this some stack overflow in the cb?

RE: Command line tracing in Ubuntu

Matts — Thu, 31 Mar 2016 11:39:10 GMT

Ok, lets reform the question.

What is the easiest way to try the tracing under linux? I noticed, that there's pretty much no printf:s in other examples than the uart.

I managed to get uart traces out (only to terminal, not via any j-link related tool) from putty-example by adding uart config to example:

const app_uart_comm_params_t comm_params =
{
  RX_PIN_NUMBER,
  TX_PIN_NUMBER,
  RTS_PIN_NUMBER,
  CTS_PIN_NUMBER,
  APP_UART_FLOW_CONTROL_ENABLED,
  false,
  UART_BAUDRATE_BAUDRATE_Baud38400
};
 // Initialize.

APP_UART_FIFO_INIT(&comm_params,
                 UART_RX_BUF_SIZE,
                 UART_TX_BUF_SIZE,
                 uart_error_handle,
                 APP_IRQ_PRIORITY_LOW,
                 err_code);

However when I tried this with any soft device example, no trace is outputted properly (some random characters appear to terminal occasionally). The app_trace_init seems to do same thign with higher bus clock, but that's it.

Is there something in the softdevice that re-routes the uart output? Or is this matter of some makefile setting?