Dynamic allocate BLE observers

RE: Dynamic allocate BLE observers

nine-fox — Mon, 19 Feb 2018 11:17:36 GMT

Hi Håkon,

Thanks a lot for your reply!

Your suggestions look great to me and I will have a try :-)

Vincent

RE: Dynamic allocate BLE observers

Håkon Alseth — Mon, 19 Feb 2018 09:00:34 GMT

Hi Vincent,

Sorry for misunderstanding, and thanks for clarifying your use-case!

I am functions from SDK v14, application ble_app_hids_keyboard as an example here;

you can mimic the "older" use-case by declaring the m_hids variable as you did in SDK 12, and then call "ble_hids_on_ble_evt(p_ble_evt, NULL)" from main.c::ble_evt_handler() with an if-condition for dynamic handling. Note that you'll also need to comment out (or, wrap an if-condition around if dynamic handling of HIDS) hids_init() in main.c::services_init().

If DEVICE B never needs the hid-service, then I would just use #ifdef to remove it from the project when compiling for this specific device.

Best regards,

Håkon

RE: Dynamic allocate BLE observers

nine-fox — Sat, 17 Feb 2018 05:33:41 GMT

Hi Håkon,

Thanks a lot for your detailed reply! Following your guide, I can define these observers successfully. However, it is *STATIC*.

For example, my firmware needs to start with HID and NUS service for DEVICE A, so I add the following lines in my code:

BLE_HIDS_DEF(m_hids);

BLE_NUS_DEF(m_nus);

However, when this firmware starts for DEVICE B, it only needs NUS service ONLY. As a result, m_hids is not used, and the hid listener is added anyway.

How can I add NUS service and listen for NUS events only for DEVICE B? (while DEVICE A works well)

Thanks,

Vincent

RE: Dynamic allocate BLE observers

Håkon Alseth — Wed, 14 Feb 2018 09:24:30 GMT

Hi,

Most of this is done in linker sections. This is what BLE_HIDS_DEF expands to:

#define BLE_HIDS_DEF(_name)                                                                         \
static ble_hids_t _name;                                                                            \
NRF_SDH_BLE_OBSERVER(_name ## _obs,                                                                 \
                     BLE_HIDS_BLE_OBSERVER_PRIO,                                                    \
                     ble_hids_on_ble_evt, &_name)

And NRF_SDH_BLE_OBSERVER(...) expands to defining a linker section (though several steps), which shall be declared in your linker script as the .sdh_ble_observer section:

*snip*
  .sdh_ble_observers :
  {
    PROVIDE(__start_sdh_ble_observers = .);
    KEEP(*(SORT(.sdh_ble_observers*)))
    PROVIDE(__stop_sdh_ble_observers = .);
  } > FLASH
*snip*

This tells the linker where the section is located both with a __start and a __stop symbol (think of it like a pointer), so that it is able to statically allocate 'n' amount of observers based on how many BLE_ANY_SERVICE_DEF(...) that you have in your application.

The library nrf_sdh will then iterate over all the BLE_*_DEF() objects so you do not have to go into your main.c::on_ble_evt() function to add another function call.

In order to migrate your current project to SDK 14.x, you need to conform to the BLE_*_DEF() API for your BLE observers, and updated your linker script. The linker script can be taken from almost any ble_app_* example, as they all include the sections needed. Remember that you might need to adjust the RAM start address.

Let me know if you run into trouble.

Cheers,

Håkon