Timeslot allocation in multiprotocol application. clock configuration

[lyris]

Hello,

I have experienced some softdevice hardfault in my multiprotocol application. I use https://github.com/NordicSemiconductor/nRF-IEEE-802.15.4-radio-driver/wiki with the raal softdevice arbiter.

The problem is most likely due to an inaccurate configuration of the clock. I have done a workaround to fix the problem by changing the default nrf_raal_softdevice_cfg_t config of the nrf_802154 library.

By default, NRF_RAAL_TIMESLOT_DEFAULT_SAFE_MARGIN_US is set to 3. Changing it to 20 makes the application working better, but there is obviously a problem somewhere.

[Edvin]

Hello,

What hardfault do you observe? Does it come with some pointers to the softdevice?

Is this in one of the examples from the SDK, or did you implement your own multiprotocol example using the driver?

Also, what HW are you running this on? Is it the nRF52840 DK, or a 3rd party module? The reason I ask is that this seems to be dependent on the XTALS. 

I have not experienced any hardfault issues with the multiprotocol examples in the SDK when using the DKs, and NRF_RAAL_TIMESLOT_DEFAULT_SAFE_MARGIN_US set to 3, which is the default in the examples.

Best regards,

Edvin

[lyris]

Hello,

the softdevice assertion faild at 0x00025b94. I have my own multiprotocol implementation which uses nrf_802154 csma. The hardware is a nRF52840 DK.