Hello,
I've been using the nRF52832 with a Segger JLink Pro which works fine during execution. However during the system initialisation, this is just before getting to the application main loop the RTT logs wont entirely display. The internal buffer seems to get to a point where it gets full and initial so only a few lines of the initialisation logs are actually displayed.
This is not really a big problem because during the main application execution logs work just fine.
I've tried using the NRF_LOG_FLUSH() (given that logs are deferred) macro in between initialisation function calls but this doesn't seem to have any effect. On the other hand, if I place a small delay (20ms) in between these function calls, the logs appear just fine.
I've been playing around with the NRF_LOG buffer size parameters in sdk_config.h with no success.
Is this a known issue? Is there a workaround this? I can't seem to find a more elegant solution apart from placing those ugly delays.
My current sdk_config.h configuration for the logger is the following:
// <e> NRF_LOG_ENABLED - nrf_log - Logger //========================================================== #ifndef NRF_LOG_ENABLED #define NRF_LOG_ENABLED 1 #endif // <h> Log message pool - Configuration of log message pool //========================================================== // <o> NRF_LOG_MSGPOOL_ELEMENT_SIZE - Size of a single element in the pool of memory objects. // <i> If a small value is set, then performance of logs processing // <i> is degraded because data is fragmented. Bigger value impacts // <i> RAM memory utilization. The size is set to fit a message with // <i> a timestamp and up to 2 arguments in a single memory object. #ifndef NRF_LOG_MSGPOOL_ELEMENT_SIZE #define NRF_LOG_MSGPOOL_ELEMENT_SIZE 20 #endif // <o> NRF_LOG_MSGPOOL_ELEMENT_COUNT - Number of elements in the pool of memory objects // <i> If a small value is set, then it may lead to a deadlock // <i> in certain cases if backend has high latency and holds // <i> multiple messages for long time. Bigger value impacts // <i> RAM memory usage. #ifndef NRF_LOG_MSGPOOL_ELEMENT_COUNT #define NRF_LOG_MSGPOOL_ELEMENT_COUNT 8 #endif // </h> //========================================================== // <q> NRF_LOG_ALLOW_OVERFLOW - Configures behavior when circular buffer is full. // <i> If set then oldest logs are overwritten. Otherwise a // <i> marker is injected informing about overflow. #ifndef NRF_LOG_ALLOW_OVERFLOW #define NRF_LOG_ALLOW_OVERFLOW 1 #endif // <o> NRF_LOG_BUFSIZE - Size of the buffer for storing logs (in bytes). // <i> Must be power of 2 and multiple of 4. // <i> If NRF_LOG_DEFERRED = 0 then buffer size can be reduced to minimum. // <128=> 128 // <256=> 256 // <512=> 512 // <1024=> 1024 // <2048=> 2048 // <4096=> 4096 // <8192=> 8192 // <16384=> 16384 #ifndef NRF_LOG_BUFSIZE #define NRF_LOG_BUFSIZE 1024 #endif // <q> NRF_LOG_CLI_CMDS - Enable CLI commands for the module. #ifndef NRF_LOG_CLI_CMDS #define NRF_LOG_CLI_CMDS 0 #endif // <o> NRF_LOG_DEFAULT_LEVEL - Default Severity level // <0=> Off // <1=> Error // <2=> Warning // <3=> Info // <4=> Debug #ifndef NRF_LOG_DEFAULT_LEVEL #define NRF_LOG_DEFAULT_LEVEL 4 #endif // <q> NRF_LOG_DEFERRED - Enable deffered logger. // <i> Log data is buffered and can be processed in idle. #ifndef NRF_LOG_DEFERRED #define NRF_LOG_DEFERRED 1 #endif // <q> NRF_LOG_FILTERS_ENABLED - Enable dynamic filtering of logs. #ifndef NRF_LOG_FILTERS_ENABLED #define NRF_LOG_FILTERS_ENABLED 0 #endif // <o> NRF_LOG_STR_PUSH_BUFFER_SIZE - Size of the buffer dedicated for strings stored using @ref NRF_LOG_PUSH. // <16=> 16 // <32=> 32 // <64=> 64 // <128=> 128 // <256=> 256 // <512=> 512 // <1024=> 1024 #ifndef NRF_LOG_STR_PUSH_BUFFER_SIZE #define NRF_LOG_STR_PUSH_BUFFER_SIZE 128 #endif
Thanks so much in advance and best regards.
Andoni
