RE: MPSL ASSERT: 106, 501

Susheel Nuguru — Wed, 07 Feb 2024 06:27:47 GMT

Hi cbooth_lpa,

The assert shows that one of your timeslots sessions have overstayed in the timeslot and did not end it in time. This could happen if you have a high priority context/interrupt_handler that masks the MPSL timer interrupt handling.

The other reason could be that your application is using timeslot API itself in which case the application is responsible to close the timeslot before it expires. In this usecase, it might be that the application does not manage to close the timeslot in time.

RE: MPSL ASSERT: 106, 501

Susheel Nuguru — Tue, 06 Feb 2024 12:04:00 GMT

I need to ask the MPSL team to give the context of when this can happen. I have enough information from you to ask the team. I will write back here once I get the response from the team.