Difference between System Events and BLE events in S110?

RE: Difference between System Events and BLE events in S110?

John — Fri, 23 Jan 2015 13:51:05 GMT

Hi Brajesh,

For most peripherals such as the UART you will get the interrupts directly and have your own interrupt handlers. However some system activities such as access to the flash memor (NVMC) require the soft device stack to do work to ensure that the stack is not interferred with. In those cases, the stack passes you control via the system events once it does the work it needs to do.

RE: Difference between System Events and BLE events in S110?

Brajesh — Fri, 23 Jan 2015 04:29:41 GMT

Thanks John, it is reasonably clear now. So interrupts generated by SPI, UART etc also goes under System events (Non-BLE portion of SOC) ?

RE: Difference between System Events and BLE events in S110?

John — Thu, 22 Jan 2015 14:38:11 GMT

System events handled in the softdevice_sys_evt_handler_set function are events related to the non-radio portion of the SOC. Things like events generated by the NVMC (Non-Volatile Memory Controller) would fall into this category.

Bluetooth Low Energy events are those related to the Bluetooth communications functions provided by the stack and radio. Things like connect, disconnect, packet received, packet transmitted etc.

They probably could have been implemented in a single event handler, but that would take away from the clarity of a module design. For example if you were doing a design with the ANT protocol rather than BLE, your event handler would be cluttered with BLE events even though you don't use them.