NCS\Zephyr. lll.c 352 Assert

[ipshiv]

Good day!

Time after time I catch next assert

00> ASSERTION FAIL @ WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c:352
00> E: r0/a1:  0x00000003  r1/a2:  0x20009cf0  r2/a3:  0x00000001
00> E: r3/a4:  0x20009d46 r12/ip:  0xa0000000 r14/lr:  0x0002ecbb
00> E:  xpsr:  0x61000011
00> E: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000
00> E: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000
00> E: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000
00> E: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000
00> E: fpscr:  0x00030f1e
00> E: Faulting instruction address (r15/pc): 0x0002ecc6
00> E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> E: Fault during interrupt handling

Assert occurs most often when I use 3+ mesh sensors in one server with periodic publication configured.

Is there any recommendations how to avoid this kind of problem?

nRF Connect SDK - v1.7.1 Zephyr - v2.6.99

[Mttrinh]

Hi,

Could you give me more details about the issue? What example are you running and have you made any modifications to it?

Which board are yoiu using? 

Assert occurs most often when I use 3+ mesh sensors in one server with periodic publication configured.

Do you mean 3+ sensor models in one server node? Can you describe the steps you have taken to get this assert?