BLE stack event and SYS event difference?

[Milad]

Hello there, I have been trying to look at the documentation and the forum but haven't been able to understand the difference between BLE stack event and SYS event. Could someone please explain this or posts links that would clarify the question.

Thank you

[RK]

one returns events related to bluetooth, one returns events related to everything which isn't bluetooth but is still executed by the softdevice. If you look at the documentation for sd_evt_get it tells you what events are returned, there's only a few, and sd_ble_evt_get returns all the rest, as sd_ble_evt_t structures (although that's not clear from the function documentation particularly).

[Milad]

Thank you for your response. Are these two hardware related interrupts?

[RK]

No they are functions. Although the softdevice raises SWI2 to indicate it has events waiting.

If you read the softdevice eventhandler code you can see in 20 lines how this works.

[Milad]

SO I have tried to look the sd_evt_get function. This is the furthest i got and in the search that I did was not able to trace the function down. Where can I find the SoC library ?

developer.nordicsemi.com/.../a01316.html

**uint32_t sd_evt_get	(	uint32_t * 	p_evt_id	)	
Gets any pending events generated by the SoC API.

The application should keep calling this function to get events, until NRF_ERROR_NOT_FOUND is returned.

Parameters
[out]	p_evt_id	Set to one of the values in NRF_SOC_EVTS, if any events are pending.
Return values
NRF_SUCCESS	An event was pending. The event id is written in the p_evt_id parameter.
NRF_ERROR_NOT_FOUND	No pending events.**

[RK]

You can't trace it any further - it calls into the softdevice at that point. What are you trying to do here?

I suggested looking at the softdevice eventhandler code, softdevice_handler.c which shows you how those two functions, sd_evt_get() and sd_ble_evt_get() are used.