mesh node unexpected reset

[stefanogradozzi]

Hello,

I have realized a simple mesh network made up by 6 nodes, one basically with on-off client function and five basically with on-off server function.

In other words, toggle of SW0 on client makes on-off of LED0 on all servers.

All nodes are realized with nrf_52840.

When I try repeatedly to push SW0 (one push every 2 or 3 seconds), LED0s repeatedly go on/off as expected, but every now and again a node unexpectedly resets (not always the same node, first one then another and so on).

I was able to capture the error messages sent through serial communication by one of the nodes in case of reset.

Here they are:

ASSERTION FAIL [(ret == 0) || (ret == 2) || (fp_op_func == ((void *)0))] @ WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/ull_adv.c:1939
[00:08:25.577,514] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x0000001c
[00:08:25.577,545] <err> os: r3/a4:  0x200022c8 r12/ip:  0x00000014 r14/lr:  0x0000ccc3
[00:08:25.577,575] <err> os:  xpsr:  0x6100001b
[00:08:25.577,575] <err> os: Faulting instruction address (r15/pc): 0x0000ccce
[00:08:25.577,636] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:08:25.577,636] <err> os: Fault during interrupt handling
[00:08:25.577,667] <err> os: Current thread: 0x20002950 (unknown)
[00:00:00.000,427] <err> qspi_nor: JEDEC id [00 00 00] expect [c2 28 17]
*** Booting nRF Connect SDK v2.5.1 ***
[00:00:00.000,671] <inf> main: Initializing...

Can you help me to fix this?

Thank you in advance

[Amanda Hsieh]

Hi, 

ASSERTION FAIL [(ret == 0) || (ret == 2) || (fp_op_func == ((void *)0))] @ WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/ull_adv.c:1939

It's from https://github.com/nrfconnect/sdk-zephyr/blob/main/subsys/bluetooth/controller/ll_sw/ull_adv.c#L1939 

Could you try to debug to check it' caused which one?

ret == TICKER_STATUS_SUCCESS) ||
(ret == TICKER_STATUS_BUSY) ||
(fp_op_func == NULL));

[00:00:00.000,427] <err> qspi_nor: JEDEC id [00 00 00] expect [c2 28 17]

You can check the similar cases
qspi_nor error using SPI: JEDEC id [00 00 00] expect [c2 28 17] 

 JEDEC id [00 00 00] expect [c2 28 17] in Matter template sample 

 spi_nor device id 00 00 00 does not match config c2 28 17   

Regards,
Amanda H.

[stefanogradozzi]

Hi,

I managed to check the value of ret and fp_op_func when there is the reset event:

RET = 1

FP_OP_FUNC = 212549

I hope that this is useful to understand why there are unexpected resets in my system

Regards

[Amanda Hsieh]

Are you using the Zephyr controller or the softdevice controller? If it is the Zephyr controller, could you try the softdevice controller?

Are you able to reproduce the issue with the light and light_switch sample?

[stefanogradozzi]

Hi,

Are you using the Zephyr controller or the softdevice controller? If it is the Zephyr controller, could you try the softdevice controller?

I'm using Zephir controller through nrf Connect system.
I don't know how to switch from Zephyr controller to softdevide controller: could you tell me which is the easiest way to do this?

Are you able to reproduce the issue with the light and light_switch sample?

Our mesh network is based upon your light, light switch, dfu, and vendor (chat) example and permit to automate switch on and off every 3 secs without press any button.
I will try to reproduce the issue with the light and light_switch sample only, but this means to press manually the button, and in this way it will be not easy to sistematically reach the reset event.

[stefanogradozzi]

I forgot to tell you that I'm using NCS version 2.5.1