BLE legacy advertising with SDK V16 on nRF52820?

RE: BLE legacy advertising with SDK V16 on nRF52820?

dannyhacker1 — Fri, 31 Jan 2020 17:05:24 GMT

Update: I couldn't figure out how to get it to work with ble_app_uart. I instead started with Bluetooth low energy Advertising, a beginner's tutorial and added UART code and it works for me.

RE: BLE legacy advertising with SDK V16 on nRF52820?

dannyhacker1 — Thu, 30 Jan 2020 17:51:48 GMT

Sorry for not adding the details: Yes I changed the init.advdata.flags to be BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE as well as setting init.config.ble_adv_fast_timeout to be 0 [as documented in one of postings here -- forgot which post]. This makes it not time out.

I reverted the main.c to original source of SDK16 and I can see OK on Samsung. On Nexus, the mac address shows up but not the device name. [NRF Connect app shows the UART Icon so it can see the Nordic UART Service] . So I can now tell that both my code and original BLE-UART code shows up on NRF Connect on Nexus 9 but only the mac address not the device name. Why would this be the case?

As for Legacy mode: how is it suppose to be set/unset? The parameter no longer exists in the header files so it would be nice if the doc gets updated to reflect this change, no?

RE: BLE legacy advertising with SDK V16 on nRF52820?

Vidar Berg — Thu, 30 Jan 2020 07:53:53 GMT

Hi,

Most of our examples use "legacy" advertising by default, including the ble_app_uart example. It's really advertising without the advertising extension feature from Bluetooth 5 as Håvard explains in this thread: https://devzone.nordicsemi.com/f/nordic-q-a/34139/sdk-references-ble_adv_legacy_enabled-but-does-not-seem-to-exist.

I think it must be something else causing this. But it's strange that it gets seen by the Samsung phone when it's not seen on the Nexus.

[quote user=""]The only changes I made are the Device Name (changed from "Nordic_UART" to "Nordic_2UART") and changed the advertising timeout to be zero.[/quote]

Just to confirm, both the Nexus table and Samsung phone was tested after you made these changes? Because the BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE flag in advertising_init() must be replaced with BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE to support advertising without timeout.