mesh node unexpected reset

RE: mesh node unexpected reset

Amanda Hsieh — Fri, 08 Mar 2024 13:49:33 GMT

Hi,

It's good to hear that.

I will be out of the office next week and will not reply immediately. If the the issue is urgent, please create a new support.

-Amanda H.

RE: mesh node unexpected reset

stefanogradozzi — Fri, 08 Mar 2024 13:41:30 GMT

Hi,

I made a lot of experiments in these latest days and It seems that removing CONFIG_BT_LL_SW_SPLIT=y resolves the unexpected reset issue.

Next days I'll go on with additional tests and I hope that the good result will be confirmed

Regards

RE: mesh node unexpected reset

stefanogradozzi — Wed, 06 Mar 2024 14:31:52 GMT

ok, I will try to remove it and I'll let you know the result as soon as possible

RE: mesh node unexpected reset

Amanda Hsieh — Wed, 06 Mar 2024 14:26:19 GMT

Could you try to remove it to use the softdevice controller?

RE: mesh node unexpected reset

stefanogradozzi — Wed, 06 Mar 2024 13:58:46 GMT

Yes, in prj.conf I have option CONFIG_BT_LL_SW_SPLIT=y

RE: mesh node unexpected reset

Amanda Hsieh — Wed, 06 Mar 2024 13:49:54 GMT

Are you using the Zephyr controller with option CONFIG_BT_LL_SW_SPLIT=y? In NCS, the default setting is to use the softdevice controller.

RE: mesh node unexpected reset

stefanogradozzi — Wed, 06 Mar 2024 10:11:03 GMT

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

RE: mesh node unexpected reset

stefanogradozzi — Wed, 06 Mar 2024 08:26:31 GMT

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.

RE: mesh node unexpected reset

Amanda Hsieh — Tue, 05 Mar 2024 19:52:27 GMT

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?

RE: mesh node unexpected reset

stefanogradozzi — Tue, 05 Mar 2024 14:33:44 GMT

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

RE: mesh node unexpected reset

Amanda Hsieh — Fri, 01 Mar 2024 13:59:43 GMT

Hi,

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

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));

[quote user=""][00:00:00.000,427] <err> qspi_nor: JEDEC id [00 00 00] expect [c2 28 17][/quote]

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.