SWI2_IRQHandler trouble?

RE: SWI2_IRQHandler trouble?

run_ar — Mon, 05 Feb 2018 14:50:10 GMT

Ok, please make sure you do not call softdevice functions from within the timer2 interrupt. Instead you should create an event that you can handle in main context later on.

RE: SWI2_IRQHandler trouble?

Mitch996 — Fri, 02 Feb 2018 03:07:51 GMT

Hello, thank you for your reply. The only softdevice estricted peripherals I can think of is the radio and timer. I'm using timer 2, not even 3, and I'm definitely not using the radio at all, I've also used TWI and SPI and that's it.

I'm still checking whether my app is making interrupt calls from within the SWI interrupt, most likely the timer2. Will get back later. I hope that is what you meant by your 1st reply.

In the mean time, please make more suggestions, thank you.

RE: SWI2_IRQHandler trouble?

run_ar — Wed, 31 Jan 2018 14:09:40 GMT

Could you be using any HW peripherals that is blocked by or restricted by the SD? Please check the softdevice specification, chapter 11 SoC resource requirements. For restricted peripherals e.g. the RNG you need to use the SD api to use this.

RE: SWI2_IRQHandler trouble?

Mitch996 — Wed, 31 Jan 2018 10:14:32 GMT

Hi the SDK is 10.0.0, I don't know how to check that yet but I think I'll figure it out, you can give me a tip or 2 if you want to. I'll get back later. On the other hand, what is the chance of a data collision? By that I mean something on the stack overridden something it shouldn't?

RE: SWI2_IRQHandler trouble?

run_ar — Wed, 31 Jan 2018 10:07:02 GMT

Which SDK version are you using? Could you check that you are not calling any SD functions from isr? i.e. If you are running in ISR and calling a new ISR with the same priority or higher, the CPU core will trigger a fault.
There is a couple of good threads here and here.