Hi,
I am running the stock UDP example on a nRF9160-DK (PCA10090, 0.8.5, 2019.7, Modem FW 1.3.6) and the modem crashes immediately.
*** Booting nRF Connect SDK v3.5.99-ncs1-1 *** UDP sample has started E: Modem has crashed, reason 0x10, PC: 0x1142c4 E: Modem library initialization failed, err -5 I: Trace thread ready E: Failed to set trace level, err: -1 I: Trace level override: 2 E: Failed to start tracing, err -8 E: Modem library init error: -5, lte_lc not initialized Failed to initialize modem library, error: -5 I: No more trace data
I have also tried the CoAP example and I am getting a similar result.
*** Booting nRF Connect SDK v3.5.99-ncs1-1 *** [00:00:00.341,705] <inf> coap_client_sample: The CoAP client sample started [00:00:00.341,705] <inf> coap_client_sample: Bringing network interface up and connecting to the network [00:00:00.539,306] <err> nrf_modem_lib_netif: Modem error: 0x10, PC: 0x1142c4 ASSERTION FAIL [!arch_is_in_isr()] @ WEST_TOPDIR/zephyr/kernel/mutex.c:110 mutexes cannot be used inside ISRs [00:00:00.539,428] <err> os: r0/a1: 0x00000004 r1/a2: 0x0000006e r2/a3: 0x00000003 [00:00:00.539,459] <err> os: r3/a4: 0x2000cb90 r12/ip: 0x00000014 r14/lr: 0x0001bc73 [00:00:00.539,459] <err> os: xpsr: 0x4100003a [00:00:00.539,459] <err> os: Faulting instruction address (r15/pc): 0x000200cc [00:00:00.539,520] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0 [00:00:00.539,520] <err> os: Fault during interrupt handling [00:00:00.539,550] <err> os: Current thread: 0x2000d380 (unknown) [00:00:00.608,917] <err> fatal_error: Resetting system
I did manage to rebuild the UDP example to allow for a modem trace.
trace-2024-07-15T15-56-22.067Z.mtrace
Any ideas or is this DK just broken?