Why did the softdevice handler's API change?

RE: Why did the softdevice handler's API change?

Håkon Alseth — Mon, 07 May 2018 07:18:19 GMT

Hi,

That is correct. If you want to change the order, wrt. which handler is called first, then you should change the define that you mention.

Best regards,

Håkon

RE: Why did the softdevice handler's API change?

masataka hasegawa — Mon, 07 May 2018 03:36:02 GMT

Hi,

Thank you for your reply.
I understood it.

At old interface,
if I want to change the handler priority, I changed the order of the hanler calling.

At new interface,
if I want to change the handler priority, shuld I set BLE_XXXX_OBSERVER_PRIO?

Best regards,

Hasegawa

RE: Why did the softdevice handler's API change?

Håkon Alseth — Fri, 20 Apr 2018 13:39:03 GMT

Hi,

The previous implementation of the softdevice_handler was centered around the main.c application, and the on_ble_evt handler.

All the hooks into ble-services, bond handling, flash handling, and other SoftDevice related events needed to go through the main.c implementations.

One of the issues that we at technical support saw very often is that a developer had added a new library, but forgot to add the library-handler function call to the main.c::on_ble_evt() (or sys_evt_handler), thus the application did not work properly.

With the nrf_sdh_* libraries, you can now add a new BLE service to your example, and the handler for the BLE service recently added will be loaded into a .section for the linker to dynamically place.

nrf_sdh_* will look at this .section, and loop over it for all the registered "subscribers".

This removes manual labor for the developer, and optimizes the application as each function call is not routed from the main file anymore.

This thread might also be of interest:

https://devzone.nordicsemi.com/f/nordic-q-a/30470/dynamic-allocate-ble-observers/

Best regards,

Håkon