Why NRF_LOG_INFO is going crazy ?

[Lola]

I think I found the source of many of my recent problem. The print in Segger is going crazy. I found out that if I increment a simple variable and print it when I hit debug and run ( then play button), they system will skip or stop in the middle :

I removed everything and I did this on the main.c :

  for (int k=0;k<50;k++)
   NRF_LOG_INFO("BIM BAM %d\r\n",k );

This will only print from 0 up to 23 or 27 , not to 50 .

I think there is something fundamentally wrong with my printing which skips values and going crazy.

I'v also tried to use the nrf_log_push , on things like this :

   for (int k=0;k<50;k++)
   NRF_LOG_INFO("Read %s\r\n",nrf_log_push(data[k]) );

which would skip levels, and instead of data that goes from 1 -50 , it will go like :

1 2 3 5 6 8 10 11 12 15 etc .

In simple words it is going crazy for some reason.

[Jørgen Kvalvaag]

NRF_LOG is non-blocking so, as @Turbo J mentioned, by default it will skip if there is no space in buffer.

You can configure thisbehaviour in sdk_config.h. Look under nRF_Segger_RTT -> segger_rtt -> SEGGER_RTT_CONFIG_DEFAULT_MODE, you can change it to BLOCK_IF_FIFO_FULL.

This way you should be able to print whatever you want without inserting delays.

[Krzysztof Chruscinski]

You can also try to increase logger buffer size (NRF_LOG_DEFERRED_BUFSIZE in sdk_config.h). This is the buffer which holds log entries before they are processed and send to the host (NRF_LOG_PROCESS, NRF_LOG_FLUSH). But as Jorgen mentioned it can be that RTT is losing the data because it is not able to process.

[Lola]

Thank you ! I wonder why am I the only one at least at Google, to having this kind of problems :)