SD_EVT_IRQHandler in Timeslot obsever

[FA]

I'm using the Github project github.com/.../nRF51-multi-role-conn-observer-advertiser in order to SCAN in a specific channel rather than all 3 channels. In this example, softdevice_handler.c which is needed for normal advertising is not used. As long as you add this file, you will get a conflict for SWI2_IRQHandler.

It is used in both main.c of the Timeslot scanner as SD_EVT_IRQHandler (defined in nrf_soc.h #define SD_EVT_IRQHandler (SWI2_IRQHandler)) and in softdeivce.handler.c. I want to solve this conflict and be able to use the rest of my program just like before adding this Timeslot scan to it.

Generally,

1- what are the sources of these 2 interrupts? any good documentation on these interrupts?

2- If I want to use time slot only for scanning, and use normal advertising with S110, are these interrupts related? i.e., they should be handled in the same IRQHandler? or we can service them separately?

[Hung Bui]

Hi FA,

1. They all come from the same source, the softdevice event notification that use the SWI2 to notify the application. Please have a look in the Softdevice product specification, look for "Application signals - software interrupts"

2. I don't think normal advertising have anything to do with softdevice event, except for the advertising timeout event.

My suggestion for you is to do some more study on a normal example to understand how the softdevice event handle works. Then you can have a look at the timeslot documentation in the softdevice specification (download from our website). A tutorial on how the timeslot works can be found in the tutorial section here.

[FA]

Thanks for the documentations. The softdevice_handler.c is used in the advertising part of my program, which is essentially based on one of the SDK examples, so that file has to be included. Also, I need to have the Observer example added to the program, which is using SWI2_IRQHandler. So, these two handlers have to be merged. As I'm doing scanning and advertising sequentially and not at the same time, does it make sense to add a switch case in the SWI2_IRQHandler and do whatever the examples are doing based on whether the timeslot scanning or normal advertising is being used (just as a very quick setup to get rid of the error)?

[FA]

An answer to my above issue is posted in comments of this post: devzone.nordicsemi.com/.../