Timeslot API

[xixili]

I use SDK 15.3, nrf52840.

https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/setting-up-the-timeslot-api

Normal use most of the time, after transmitting for a period of time, NRF_RADIO_CALLBACK_SIGNAL_TYPE_RADIO cannot be received.

NRF_RADIO_CALLBACK_SIGNAL_TYPE_START, NRF_RADIO_CALLBACK_SIGNAL_TYPE_TIMER0 can be received，What is the problem？

[Einar Thorsrud]

Hi,

I do not fully understand the context of this question. Can you please elaborate / explain in more detail what you do and what the issue is?

[xixili]

Set up a timeslot, use ble and radio at the same time, after a long period of use, conflicts will occur, and the protocol stack will be reset abnormally. I found that it was caused by no radio interruption, how should I solve it?

Refer to devzone.nordicsemi.com/.../setting-up-the-timeslot-api

[Einar Thorsrud]

Hi,

I see. So you are waiting for a radio interrupt that does not happen. Is this still within a timeslot? Have you debugged to verify that you have some radio activity that should have caused a radio interrupt? Please elaborate / provide much more details so that I can better understand what could be going on.

[xixili]

Radio interruption will appear at the beginning, but it will be lost after a period of time. Sometimes it is a day, sometimes a few days, and it may appear in a few hours soon. Why is there no radio interruption

[Einar Thorsrud]

I understand. But there is not enough to go on for me to consider what could cause this. Have you done any debugging? What have you found out? Please elaborate.

[xixili]

Call sd_radio_request(&m_timeslot_request) once every 3 seconds; after sending thousands of times, an error may appear SOFTDEVICE: ASSERTION FAILED

ASSERTION FAILED

[Einar Thorsrud]

That makes sense. Can you cheche which assert you get, meaning which program counter value? You can typically see that from the app_error_fault_handler when you get a NRF_FAULT_ID_SD_ASSERT (it is called with pc as a parameter).

In most cases with SoftDevice asserts when using timeslot it is related to the application either not cleaning up properly or using resources outside of the timeslot for some reason.