mpsl_init: MPSL ASSERT: 112, 2245

[ronbo999]

Hi. I'm using NCS v1.9.1 with nRF5340 and I'm trying to merge the direct_test_mode sample app with the hci_rpmsg sample app. Basically, I have one net core image that has both sample apps. When the net core app boots up, it runs the hci_rpmsg app or the direct_test_mode app.

When the net core is running direct_test_mode app, I'm getting the following asserts when I try to run a transmit test.

nrf_dppi[00:00:30.074,218] <err> mpsl_init: MPSL ASSERT: 112, 2245
[00:00:30.074,249] <err> os: ***** HARD FAULT *****
[00:00:30.074,249] <err> os:   Fault escalation (see below)
[00:00:30.074,249] <err> os: ARCH_EXCEPT with reason 3

[00:00:30.074,279] <err> os: r0/a1:  0x00000003  r1/a2:  0x21001938  r2/a3:  0x21001938
[00:00:30.074,279] <err> os: r3/a4:  0x21002520 r12/ip:  0x00000000 r14/lr:  0x010246df
[00:00:30.074,279] <err> os:  xpsr:  0x61000018
[00:00:30.074,279] <err> os: Faulting instruction address (r15/pc): 0x0101fe62
[00:00:30.074,310] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:30.074,310] <err> os: Fault during interrupt handling

[00:00:30.074,310] <err> os: Current thread: 0x21001938 (Shure rpmsg)
ÿ*** Booting Zephyr OS build v2.7.99-ncs1-1  ***

Since I don't have access to the MPSL library, can you shed some light about the possible cause of this assertion? What does the code 2245 mean?

[Susheel Nuguru]

Not sure if you are supposed to run DTM and rpmsg together. The DTM needs direct access to hardware and is very time critical so is the hci_rpmsg stack using MPSL. I do not think that MPSL like DTM using other restricted peripherals directly. 

[ronbo999]

Hi Susheel,

Just to clarify. DTM and rpmsg are not running at the same time. When the net core boots up, it's either running DTM or rpmsg but not both at the same time.

[Susheel Nuguru]

I do not have access to the assert table in the Softdevice Controller so asking the dev team to shed some light on this. Will come back to you when i have some info.

[Susheel Nuguru]

Hi,

We do not see any asserts in the MPSL in the given line number with that version of the MPSL lib that is tagged with ncsv1.9.1

If you are sure that you are using that ncs version, the only thing i can think of is a stack corruption in RAM that can cause the hardfault info invalid.

[Susheel Nuguru]

Can you please add the contents of 

sdk-nrfxlib/mpsl/lib/cortex-m4/soft-float/manifest.yaml

And which platform are you working with (Linux, Windows and other toolchain information)