DECT NR+ shell sample crashes on nRF9161 dev board and on custom board

[Joep Boumans]

Hey Nordic support,

We want to perform EMC tests on the DECT NR+ for our product and need a continuous wave or tx tone sample for testing. I found the DECT NR+ shell sample and wanted to use this with our custom nRF9161 board. However, it fails due to no being able to read the temperature sensor in the modem?The 

(dect_phy_ctrl_msgq_thread_handler): init failed (temperature 999, temp_limit 0): 24581 (ERR_INVALID_PARAMETER (temperature: not measured))
DESH version:       v3.2.1-d8887f6f32df
DESH build id:      custom
DESH build variant: dev
[00:00:00.576,873] <err> os: r0/a1:  0x00000004  r1/a2:  0x000003dd  r2/a3:  0x2002234a
[00:00:00.576,904] <err> os: r3/a4:  0x00000004 r12/ip:  0x00000000 r14/lr:  0x0001d9c5
[00:00:00.576,904] <err> os:  xpsr:  0x0100003a
[00:00:00.576,934] <err> os: s[ 0]:  0x2000c968  s[ 1]:  0x2000c3b4  s[ 2]:  0x2000c3ac  s[ 3]:  0x00000002
[00:00:00.576,965] <err> os: s[ 4]:  0x20015454  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x000393c3
[00:00:00.576,965] <err> os: s[ 8]:  0x0000000e  s[ 9]:  0x00000000  s[10]:  0x0094924c  s[11]:  0x00000000
[00:00:00.576,995] <err> os: s[12]:  0x00000000  s[13]:  0x2000c988  s[14]:  0x00000000  s[15]:  0x00000000
[00:00:00.576,995] <err> os: fpscr:  0x00000000
[00:00:00.577,026] <err> os: r4/v1:  0x00000000  r5/v2:  0x2000c994  r6/v3:  0x2000c988
[00:00:00.577,026] <err> os: r7/v4:  0x2000f248  r8/v5:  0x0005116e  r9/v6:  0x00051192
[00:00:00.577,087] <err> os: r10/v7: 0x000511b6  r11/v8: 0x00000000    psp:  0x20022568
[00:00:00.577,117] <err> os: EXC_RETURN: 0x0
[00:00:00.577,117] <err> os: Faulting instruction address (r15/pc): 0x00042096
[00:00:00.577,148] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:00.577,178] <err> os: Fault during interrupt handling

[00:00:00.577,209] <err> os: Current thread: 0x20013900 (idle)
[00:00:00.752,532] <err> os: Halting system
desh:~$ 

The sample is from the v3.2.1  SDK + toolchain and is using the DECT NR+ v1.0.1 for nRF91x1 provide by Wirepas. I tried running it on multiple of our boards, but these all had the same problem of the faulty temperature sensor.

Since this didn't work I tried to run the sample on a nRF9161 dev board but this also did not work:

desh:~$ 
Modem capabilities:
  DECT NR+ version: 1
  DECT NR+ variant count: 1
    rx_spatial_streams[0]:     3
    rx_tx_diversity[0]:        1
    mcs_max[0]:                1
    harq_soft_buf_size[0]:     4
    harq_process_count_max[0]: 0
    harq_feedback_delay[0]:    99
    mu[0]:                     0
ASSERTION FAIL [capability->variant[i].mu == 1] @ CMAKE_SOURCE_DIR/src/dect/dect_phy_ctrl.c:989
[00:00:00.748,199] <err> os: r0/a1:  0x00000004  r1/a2:  0x000003dd  r2/a3:  0x00000001
[00:00:00.748,229] <err> os: r3/a4:  0x00000004 r12/ip:  0x00000000 r14/lr:  0x0000d655
[00:00:00.748,229] <err> os:  xpsr:  0x0100003a
[00:00:00.748,260] <err> os: s[ 0]:  0x2000c968  s[ 1]:  0x2000c3b4  s[ 2]:  0x2000c3ac  s[ 3]:  0x00000002
[00:00:00.748,291] <err> os: s[ 4]:  0x200151d2  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x0002632f
[00:00:00.748,291] <err> os: s[ 8]:  0x0000000e  s[ 9]:  0x00000000  s[10]:  0x00955493  s[11]:  0x00000000
[00:00:00.748,321] <err> os: s[12]:  0x00000000  s[13]:  0x2000c988  s[14]:  0x00000000  s[15]:  0x00000000
[00:00:00.748,321] <err> os: fpscr:  0x00000000
[00:00:00.748,352] <err> os: r4/v1:  0x00000000  r5/v2:  0x2000c994  r6/v3:  0x2000c988
[00:00:00.748,352] <err> os: r7/v4:  0x2000f0b0  r8/v5:  0x0003c427  r9/v6:  0x0003c44b
[00:00:00.748,413] <err> os: r10/v7: 0x0003c46f  r11/v8: 0x00000000    psp:  0x200222b8
[00:00:00.748,443] <err> os: EXC_RETURN: 0x0
[00:00:00.748,443] <err> os: Faulting instruction address (r15/pc): 0x0002edb6
[00:00:00.748,474] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:00.748,504] <err> os: Fault during interrupt handling

[00:00:00.748,535] <err> os: Current thread: 0x20013768 (idle)
[00:00:00.923,828] <err> os: Halting system

Any ideas on what I'm missing or what could be wrong?

Kind regards,
Joep

[Elfving]

Hi,

The sample is from the v3.2.1  SDK + toolchain and is using the DECT NR+ v1.0.1 for nRF91x1 provide by Wirepas

I am not exactly sure, but if this code was provided directly from Wirapas, you should rather contact them about this.

Regards,

Elfving

[ThaboMonoto]

Hi, 

I am getting the same error, using firmware from Nordic Semiconductor. I am using DECT shell sample. Like OP, I'd like to know, what might I be doing wrong? I have no peripherals attached, it's just a clean run of the sample code.

[Elfving]

I see. Are you also using NCS version v3.2.1 ?

EDIT: Please see the comment from Lauri

[Lauri Piikivi]

Hi,

SDK 3.2.1 supports FW version 1.1, for 1.0.1 the SDK version needed is 2.7.0

There have been initialisation changes and rework on the callbacks in the modem firmware, that the 3.2.1 SDK assumes 

[ThaboMonoto]

Yes, I am using v3.2.1