Event handler interaction

[Jordan Archer]

Is there a document describing the interaction and any asynchronous issues with the different types of event handlers? As I read it there are softdevice events, BLE events, timer events and button events. Are the handlers for all of these and any I've missed, schedule step on each other, or which once do I need to be concerned about critical sections?

[Susheel Nuguru]

With nordic chips if you are using BLE stack application can get

• Interrupts from configured peripherals (Timers, watchdog, RTC, buttons uses GPIO interrupts)
• BLE events
• system events like flash operations (pstorage if your application uses it)
• radio notification events (if your application enables it)
• Timeslot events (if your application enables it)

[Jordan Archer]

I'm still not clear how each of these interact with the other. Are they scheduled independently or synchronously to each other? Can on type of event interrupt another? This helps define what items I need to wrap in critical sections.

[Jordan Archer]

As a side note, radio notifications are not events like the others. They are interrupts. And as I've discovered you can miss a radio notification if two come close together. It gets sent as one interrupt to the application. This problem occurs with heavy flash writes going on at the same time there is BLE activity.

[Susheel Nuguru]

Events are also SWI interrupts which are routed to application by softdevice handler module. In specification, they have given some explanation of how these interrupts inh each other. Do you mean that is not clear enough? If you already read the specs for softdevice then I will explain better tomorrow as I am not so good in typing on my phone :)

[Jordan Archer]

Thanks Aryan. More explanation would be helpful. Also, pointers to which section of the specification covers these SWI interactions.