Different advertising initialisation

[Pete W]

Hi

I've been experimenting with the ble_app_att_mtu_throughput example and have it running between 2 custom boards using PuTTY, but I'm struggling to understand why the advertising is initialised differently to other ble examples (heart rate sensor, UART etc), which create an instance of ble_advertising_t, and use  ble_advertising_init(..)  and  ble_advertising_conn_cfg_tag_set(..)  in the intialisation. The throughput example uses  ble_advdata_encode(..)  and  sd_ble_gap_adv_set_configure(..). Why is this? I'm using SDK 15.3 with S140 on the NRF52840.

Generally, I'm floundering a bit, and feel like I've missed a 'manual' on how/when to use the functions in the SDK and softdevice. Feel like I'm wading through treacle trying to understand how the examples work. Any pointers would be appreciated.

Cheers

Pete

[Kenneth]

It seems the advertising_init() is different because two different engineers have worked on the two different projects.

One project use the ble_advertising module in the nRF5 SDK to setup advertisement, the ble_advertising_init() will call the softdevice specific api calls. The second project use the softdevice api calls directly, for instance sd_ble_gap_adv_set_configure().

Both can work, though using the ble_advertising module may make it easier for you:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_ble_advertising.html?cp=5_1_3_2_1 

Best regards,
Kenneth

[Pete W]

Thanks for the reply. After spending a few hours digging I managed to figure out that the throughput example is using the softdevice calls directly, so you confirmed what I suspected.