Is calling Softdevice function from main context safe?

RE: Is calling Softdevice function from main context safe?

Petter Myhre — Fri, 07 Nov 2014 10:20:43 GMT

You would just need to consider that SVC calls and application interrupts will be scheduled and handled in turn. :)

RE: Is calling Softdevice function from main context safe?

michael — Fri, 07 Nov 2014 09:59:41 GMT

Thanks Petter! What I'm reading from your reply is that it might be a better idea to use the scheduler for both, the application and the softdevice. I ended up in the constellation I'm currently using because I started from a S120 example that did not use the scheduler for the SD and I did not yet dare to change it. In case I'm using the scheduler for my application anyways, are there any reasons or considerations why I would not use the scheduler also for the softdevice?

RE: Is calling Softdevice function from main context safe?

Petter Myhre — Fri, 07 Nov 2014 08:38:36 GMT

dm_device_delete_all() is a function that belongs to the Device Manager, which is a software module, it is not part of the SoftDevice.

sd_ble_gap_scan_stop() is an SVC call and has interrupt priority 2 (0 is the highest, 3 is the lowest)

There are two application interrupt priorities available, 1 and 3.

The general answer is yes, it is safe, but it depends on your application, you could get unwanted behavior if you don't keep in mind how the interrupts and the events are handled.

One difference will be that:

If you use scheduling on both the application and the SoftDevice, SVC calls and application interrupts will be scheduled and handled in turn.

If you use scheduling only on the application, the SoftDevice will be able to interrupt the scheduled application events, even the ones with priority 1.