Softdevice and interrupt lost

RE: Softdevice and interrupt lost

David Edwin — Tue, 28 Nov 2017 09:20:18 GMT

You can share your code in the one-on-one support portal so we can look at it in a confidential manner. www.nordicsemi.com/.../Contact-Support-Team

RE: Softdevice and interrupt lost

leoc7 — Tue, 28 Nov 2017 08:53:08 GMT

Ok, many thanks for your support!

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 15:00:56 GMT

ok, this typically means the interrupt routing is working ok with the softdevice enabled (since it is advertising), need to look at other issues in the code that is preventing the interrupt from running. Can you set up a gpio toggle in the interrupt code on the logic analyzer and also the hardware pin that is interrupting the mcu, i.e. and post some results. Make sure that the volatile has not been optimized out in your build, try changes in the optimization level or look at the generated code to verify that volatile is still present.

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 13:24:24 GMT

David, I confirm the situation you described

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 11:59:15 GMT

I'm NOT getting the interrupt when there is BLE connection, but I'm getting the interrupt during advertising.

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 11:56:34 GMT

let me summarize: You are getting the interrupt routine executed when the SD is advertising. You are getting the interrupt routine executed when the SD is enabled but here is no active role. You are not getting the interrupt when there is a BTLE connection. Is this an accurate understanding of the issue ? Edited: There is no interrupt on BTLE connection

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 11:52:43 GMT

These are wrapper calls with some checks.

Chapter 6: System on Chip (SoC) library

NVIC Wrapper functions for the CMSIS NVIC functions provided by ARM®. Important: To ensure reliable usage of the SoftDevice you must use the wrapper functions when the SoftDevice is enabled.

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 10:56:33 GMT

Thank you. But what does it mean "Make sure you are using the Softdevice provided wrappers for the NVIC". Could you explain better please?

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 10:54:06 GMT

Ok, then you need look if the Interrupt is being routed correctly via the softdevice as all the interrupts need to be routed via the MBR/Softdevice. Make sure you are using the Softdevice provided wrappers for the NVIC. Please do read the Softdevice specification so you understand how the softdevice fits in the architecture.

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 10:30:38 GMT

Also, I investigated with debugger and interrupt works when there is no BLE connection.

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 10:29:25 GMT

Yes, it's volatile

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 10:22:36 GMT

It should never be discarded but it may be delayed. Is the "flag_can_msg" already volatile ?

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 10:18:42 GMT

Thanks, I try to change Priority to 2. But nothing changes. Using Timeslot APi can be a valid solution?

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 09:13:26 GMT

I would suggest that you look at chapter 16 of the Softdevice specfication s132 SoftDevice v4.0. your interrupt should always be handled by the application and will never be discarded, however it can be delayed by the higher priority interrupt.

I would typically make flags as "volatile" in the interrupt context.

RE: Softdevice and interrupt lost

leoc7 — Mon, 27 Nov 2017 08:55:00 GMT

Sorry for the missing information! I updated the answer with requested info.

RE: Softdevice and interrupt lost

David Edwin — Mon, 27 Nov 2017 08:40:24 GMT

Can you add some profiling information on the SPI interrupt on how much time are you using in the interrupt. Can you also provide some information on the connection interval used and advertising interval used. The softdevice interrupt priority levels are documented in the "SoftDevice Specification S132 SoftDevice v4.0"