Hello,
I have migrated my codebase from v1.3.0 to v1.4.0 of the nRF SDK and have a strange issue now where the serial port is spitting out sleep debugging information in large volumes. It's actually incredibly difficult to read the real important debug information now.
Is there a config option to stop this? I tried turning off logging with CONFIG_LOG=n but that seems to have little affect. I don't see anything in the sample programs that would point me in the right direction for what I have enabled in my prj.conf that would cause this much log spam.
[00:00:00.254,821] <inf> mcuboot: Starting bootloader
[00:00:00.261,016] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, co1
[00:00:00.271,209] <inf> mcuboot: Boot source: none
[00:00:00.276,794] <inf> mcuboot: Swap type: none
[00:00:00.343,536] <inf> mcuboot: Bootloader chainload address offset: 0x10000
[00:00:00.351,409] <inf> mcuboot: Jumping to the first image slot
*** Booting Zephyr OS build v2.4.0-ncs1 ***
gSeeSenseCtrl Init
UART by-pass: nRF9160 PCA10090
Application Started
-----------------------------------------------------
Set-up UART
Beginning Hardware Init
Setting up WDT
**************************************************
*** INIT Choices ***
**************************************************
VBATT : true
ACC : false
NVS : true
FOTA : true
PSM : true
UART : true
LED : true
BUZZER: false
WDT : true
SN : true
MODEM : true
SCTRL : true
PRODSC: false
**************************************************
Initializing bsdlib
Initialized bsdlib
Reading Device Serial Number
Opening AT Command Socket
[00:00:00.201,751] <dbg> os.z_impl_k_mutex_lock: 0x200243d0 took mutex 0x2002484
[00:00:00.201,812] <dbg> os.z_impl_k_mutex_unlock: mutex 0x20024858 lock_count:1
--- 2 messages dropped ---
[00:00:00.206,024] ocket ID: 1
Sending AT command: AT+CGSN=0
m<dbg> os.z_impl_k_mutex_unlock: new owner of mutex 0x20021148: 0x00000000 (pri)
--- 5 messages dropped ---
[00:00:00.266,143]Modem response: xxxxxx
OK
Socket status: 22:11, No more processes
Serial Number: xxxxxx
<dbg> os.z_impl_k_mutex_unlock: new owner of mutex 0x20021148: 0x00000000 (prOt
io: -1000)
--- 7 messages dropped ---
[00:00:00.273,620] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
--- 4 messages dropped ---
[00:00:00.282,440] <dbg> os.z_Socket ID: 1
Sending AT command: AT+CFUN=41
tick_sleep: thread 0x200243d0 for 33 ticks
--- 5 messages dropped ---
[00:00:00.286,834Modem response: OK
Socket status: 5:11, No more processes
] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
--- 3 messages dropped ---
[00:00:00.290,100] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.301,757] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.302,886] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.303,955] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.305,053] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.306,152] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.307,250] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.308,349] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.326,110] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.329,620] <dbg> os.z_impl_k_mutex_lock: 0x200243d0 took mutex 0x2002114
[00:00:00.329,650] <dbg> os.z_impl_k_mutex_unlock: mutex 0x20021148 lock_count:1
[00:00:00.329,681] <dbg> os.z_impl_k_mutex_unlock: new owner of mutex 0x2002114)
[00:00:00.329,711] <dbg> os.k_sched_unlock: scheduler unlocked (0x200243d0:0)
[00:00:00.336,120] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.337,219] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.338,317] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.339,416] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.340,515] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.341,613] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.342,712] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.343,811] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.344,909] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.346,008] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.347,106] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.348,205] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.360,229] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.361,328] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.362,426] <dbg> os.z_tick_sleep: thread 0x200243d0 for 33 ticks
[00:00:00.369,140] <dbg> os.z_tick_sleep: thread 0x200243d0 for 65536 ticks
Sending AT command: AT%XSIM?
Many thanks,
MJD093
