BLE-UART Non connectable Advertising

RE: BLE-UART Non connectable Advertising

Kenneth — Thu, 02 Jul 2020 09:36:25 GMT

It's no problem to use the 'sd_*' function directly no. There should be some examples that use 'sd_*' in the nRF5 SDK:

ble_app_beacon
ble_app_blinky
ble_app_multiperipheral
..

Best regards,
Kenneth

RE: BLE-UART Non connectable Advertising

Justin — Wed, 01 Jul 2020 14:14:27 GMT

Thanks Kenneth.

Is it safe to use 'sd_*' function directly than to use 'ble_advertising_*' and 'advertising_init()' ?

RE: BLE-UART Non connectable Advertising

Kenneth — Wed, 01 Jul 2020 07:51:52 GMT

The api that start with 'sd_*' are the function calls to the BLE softdevice stack, while the 'ble_advertising_*' and 'advertising_init()' are just wrappers around these calls. The wrappers are typically SDK modules or libraries that make it slightly easier to setup and transition between advertising.

Best regards,
Kenneth

RE: BLE-UART Non connectable Advertising

Justin — Tue, 30 Jun 2020 14:07:49 GMT

Hi Kenneth,

I see that ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST); function does lot of other things for e.g. to check if flash access is in progress, whitelist fetch etc.

Is uisng sd_ble_gap_adv_start() same as ble_advertising_start?

I am confused between sd_ble_gap_adv_set_configure() and advertising_init().

When to use what?

Can you please provide me more details on the same?

RE: BLE-UART Non connectable Advertising

Kenneth — Wed, 13 May 2020 10:54:57 GMT

If you want to modify the advertisement packets you may just call:

sd_ble_gap_adv_stop()
sd_ble_gap_adv_set_configure()
sd_ble_gap_adv_start()

Though if you want to use the advertisement module you may find this answer useful:
https://devzone.nordicsemi.com/f/nordic-q-a/32824/dynamically-updating-advertising-data-in-sdk-15/128970#128970