Softdevice assert: 86108:0

[inv4]

Hi, Im using a BMD-300 board with the external crystal installed, I can run zigbee examples fine, even using the external crystal, but when running the Mesh examples I can discover the light switch example, I can provision it and it connects to it ok, I can send messages through the node to other nodes (all of this using nrf Mesh app) but if I manually disconnect the node, then I can connect to it again, if I reset the node it halts with this error from the log.

<t:    1374377>, app_error_weak.c,   96, Softdevice assert: 86108:0>

This only happens if the node is provisioned.

Ive tested this on the eval board also from Rigado and it works fine, I can reconnect.

I also have a custom board with a MDBT50Q-1M and the external crystal installed and it does the same error as the BMD-340.

Both modules are based on the nrf52840, both board can run zigbee examples.

the version of the softdevice is: s140_nrf52_7.0.1

SDK. 16.0.0

Mesh 4.0.0

[Hung Bui]

Hi,

Could you explain what exactly you meant by "manually disconnect the node" and "connect to it again" ?
The assert from the softdevice prompts that it could related to the timeslot event being used longer than it should. It could be something to do with timing. 
Which external crystal do you use ? Is it for the HFCLK or the LFCLK ? Could you send the schematic of the board ? 

Which example did you use to test ? 

[inv4]

Im using the dimmable server example from experimental but I have tried the switch server example.

By manually disconnecting the node I mean that once I provisioned the node it stays connected to that node and to the network, it can repeat messages and everything works great, but if I press disconnect on the mesh app and then I scan for provisioned nodes it shows up, but the node keeps halting like 20 seconds or so from start.

The module has already in place the HFCLK from the factory and I added the LFCKL which is a 32.768KHZ whid a +20ppm

-20ppm

[Hung Bui]

Could you confirm that the same firmware (light switch example) can run on the DK and Rigado with no problem ? 
Please make sure you have erased the chip (erase full chip) before testing with your board. 

Please try testing with the LFCLK set to RC (Set NRF_SDH_CLOCK_LF_SRC in sdk_config.h to 0 and NRF_SDH_CLOCK_LF_RC_CTIV = 16) 

If the issue persist please send us the schematic, and the full log when the issue occurs (you can increase the log level to DEBUG) 

[inv4]

It works! although I dont know if its normal that sometimes it takes several tries to connect succesfully, the first two or so tries it just goes back to the discovery of avaliable nodes without a succesfull connection and no error or log on the node that Im trying to connect via the mesh app.

[inv4]

Ive solved it changing the accuracy.