#LORA#BLE#LORAWAN

[ULJ]

I want to implement dual-mode operation of LORAWAN and BLE, but when using the SoftDevice, the interrupt on the LORAWAN DIO1 pin does not trigger. I suspect it is being blocked by the SoftDevice, and I want to know how to solve this.

The interrupt here will not be triggered

This is the function I use to set up DIO1

[Øyvind]

Hello, please provide your questions in English so that other people in this forum can see and follow this thread. 

I see that you are mentioning Lora, please note that there is no official support for Lora or Lorawan from Nordic Semiconductor. 

Kind regards,
Øyvind

[ULJ]

I hava already cahnged it to English.
Although there is no support for LoRa, that is not the key issue. The key issue is that the external interrupt I set on the DIO1 pin did not trigger. I want to know if this could be due to the SoftDevice, and how to resolve this problem. (When I don't use the SoftDevice, this interrupt can be triggered)

[Øyvind]

Thank you for converting to English, and for clarifying your issue. What version of the SoftDevice are you using, and what SDK version? I will need forward this ticket to a colleague with more knowledge on the SoftDevice side. 

Kind regards,
Øyvind

[ULJ]

The SDK is nRF5_SDK_17.1.0_ddde560_zl
The SD is s140_nrf52_7.2.0_softdevice

[Edvin]

Hello,

Please refer to the SDK 17.1.0\examples\peripheral\pin_change_int example.

The issue in your implementation is that you are using interrupt priority 0, which is reserved by the SoftDevice S140:

https://docs.nordicsemi.com/bundle/sds_s140/page/SDS/s1xx/processor_avail_interrupt_latency/exception_mgmt_sd.html

When you are using the S140 SoftDevice, you can choose between Interrupt level 2 and 3 for high priority tasks (don't spend too much time in these interrupts), or level 5, 6 or 7 for lower priority interrupts.

Best regards,

Edvin