May I ask, what's the change of nrf_log in sdk 15.3?

[nine-fox]

Hi,

I am migrating sdk 15.2 to 15.3. Everything works fine, except the nrf logging. Currently, I am using RTT configuration, with default backend enabled. The code is simple:

// Initialize SDK Logger.

APP_ERROR_CHECK(NRF_LOG_INIT(app_timer_cnt_get));

NRF_LOG_DEFAULT_BACKENDS_INIT();

Things odd is that: the log is dumped in a quite slow speed. It acts like, the logging buffer stored in rnf52840 chip. Without event triggered, they are not dumped into RTT viewer. That is to say, the log is dumped in a very deferred way. The latest logs are always not shown in RTT viewer.

BTW, other code is the same, with usbd enabled and also BLE. The functional thing works fine.

The same code works well under sdk 15.2, with the logging is dumped immediately. 

environment:

j-link 6.40

win7

sdk15.3

Since I can not find a way to debug it, would you please give me some suggestions on this? A list of the nrf_log changes in sdk 15.3 would be fine. I attached my sdk_config.h

Thanks

sdk_config.h

[Ted @ T3R]

I experienced this problem as well when moving from SDK 15.0 to SDK 15.3 on the nRF52840 dongle.

Although I did not have enough time to determine the exact cause, I have managed to get around it by downloading the most recent version of Segger's tools and drivers from their homepage (6.48b).

[nine-fox]

Hey Ted,

thanks for your comments.

That sounds reasonable. I will have a try. Currently, I am using 6.40. Will have a try on latest version

Vincent

[nine-fox]

Hi Ted,

The problem is resolved after I updated to 6.50b

Still, not sure why.....I can only guess it is a segger issue.

Thanks very much for your tip!