What context does the SoftDevice run in?

[DBT]

Interrupt or main() context, or something else?

We're using S140 SoftDevice, nRF52840 and Segger Embedded Studio 3.30

We're also usinq Quantum Leaps (https://www.state-machine.com/) as our OS 

How the SoftDevice works is still somewhat mysterious to me.  We see strange behavior and we're not sure if its because of some interaction with Quantum Leaps or something else.

Is there a good document somewhere explaining how the SoftDevice works with the application program?

Not the APIs - I can find them.  But how the APIs are working "behind the curtain".

[Håkon Alseth]

Hi,

S140 is still in alpha-state, and the full softdevice specification is not yet available.

For the interrupt model, you can look at the S132 SDS: http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/processor_avail_interrupt_latency/exception_mgmt_sd.html?cp=2_3_1_0_15_1

I recommend checking the usage patters here for typical timing details on the different roles: Bluetooth low energy processor usage patterns

Cheers,

Håkon