Interrupts with Timer Instance Issue

RE: Interrupts with Timer Instance Issue

saugatlogic — Thu, 12 Oct 2023 20:40:25 GMT

I did a workaround with TIMER interrupt. I cleared all my RADIO registers after the END interrupt and create a sufficient delay in the system before opening a new session. In addition I also had missed to cleared and stop the timer right after getting the interrupt. After doing all that now it is working fine. Thank you so much for your support.

RE: Interrupts with Timer Instance Issue

Jørgen Holmefjord — Thu, 12 Oct 2023 09:34:29 GMT

Forgot to mention that you need to select your SDK version on the top of the page to see relevant issues, if not, the link will go to the latest version and resolved issues from older SDK version will not show.

This issue seems to match with your description:

Are you using MPSL_TIMESLOT_REQ_TYPE_EARLIEST in your requests?

RE: Interrupts with Timer Instance Issue

saugatlogic — Wed, 11 Oct 2023 19:00:00 GMT

I am on v2.2.0. I couldn't find any known issues from the documentation. Some older devzone post with MPSL_ASSERT error recommended to clear the NRF_RADIO registers after some delay to make sure it, so that it would be able to perform the pending task before clearing it. So, I currently have also used COMPARE3 (delayed by 500 us) interrupt to clear radio registers. But, it seems to have similar issue event with the suggested workaround.

RE: Interrupts with Timer Instance Issue

Jørgen Holmefjord — Wed, 11 Oct 2023 17:36:58 GMT

Which version of nRF Connect SDK are you using? There are some known issues related to MPSL, can you check if any of these are valid for your setup?

RE: Interrupts with Timer Instance Issue

saugatlogic — Wed, 11 Oct 2023 17:26:51 GMT

Thank you that was a lot helpful and it worked. I am now getting the actual interrupts signal which can be compared to switch cases inside the handler function. However I am currently also trying to open a new MPSL session each time I get an interrupt form COMPARE1 of TIMER1. It works fine when I use a delayed loop and so does when it receives the first two interrupts but crashes on the third interrupt.

RE: Interrupts with Timer Instance Issue

Jørgen Holmefjord — Wed, 11 Oct 2023 13:39:27 GMT

Hi,

You need to connect the TIMER1 IRQ to the nrfx_timer IRQ handler if the driver should receive and process the interrupts. Currently it looks like you have connected the IRQ to the application callback (mpsl_timer_handler). This callback should only be passed to nrfx_timer_init() and will be called whenever the nrfx_timer driver needs to pass an event from the interrupt handler to your application.

You can find an example of how to use the nrfx driver APIs in the nrfx board sample in Zephyr.

Best regards,
Jørgen