CONNECT with extended advertising

[Tilak]

Dear Nordic DevZone,

Greetings!
I have been trying to get working with the example ble_app_buttonless_dfu
I tried configuring for extended advertising with help from this link in SDK 15.3.0 on nRF52832 DK
devzone.nordicsemi.com/.../181595

I am using two different ways to observe the nRF52832. They are: a) "nRF Connect v3.3.0 desktop" on my windows computer, open Bluetooth Low Energy and b) Samsung S10e smart phone (having Bluetooth v5.0) with "nRF Connect APP".

My aim is to quickly get the properties of nRF52832 that it is extended advertising and CONNECT so that DFU service can be triggered from the Application (and get the bootloader to perform the DFU).

I noticed the following issues, please help:

1. In addition to the above link, in this function: advertising_config_get(), I also needed to set
   p_config->ble_adv_extended_enabled = true;
   only then I am able see the correct properties on my smart phone that it is extended advertising. See attached pictures taken from my phone.
   1. Is this the correct way to configure nRF52832?
   2. Meanwhile, the "nRF Connect v3.30 on my desktop" does not show my nRF52832 at all. Is this already fixed in the upcoming release?
2. Now I press CONNECT from the smart phone "nRF Connect APP" but the connection never goes through. Am I missing some special settings to get CONNECT working with extended advertising on nRF52832?

Please help.

Thanks,
Tilak

Below picture when the ble_adv_extended_enabled = true

Below picture when the flag ble_adv_extended_enabled = false

 

[bjorn-spockeli]

Hi Tilak, 

I sincerly apologize for the late reply. This question was mislabeled by in our internal tech support system so that it disappeared for my case list. 

Tilak said:

Looking closely, with help from my colleague, at the Advertising types defined in Bluetooth Core Specification v5.0, Vol 6, Part B, Section 4.4.2.7 Connectable Undirected Event Type in particular. On page 2625, "An initiator may send a connect request using the AUX_CONNECT_REQ PDU on the same secondary advertising channel as the AUX_ADV_IND PDU to request the Link Layer to enter the Connection State......If the advertiser receives an AUX_CONNECT_REQ PDU that contains its device address from an initiator allowed by the advertising filter policy it shall reply with an AUX_CONNECT_RSP PDU on the same secondary advertising channel index."

nRF52832 -> ADV_EXT_IND PDU
Phone -> AUX_CONNECT_REQ
nRF52832 -> AUX_CONNECT_RSP

Do you have the  possible  to capture an on-air trace with a Bluetooth Protocol sniffer? I will do the same here on my end as soon as I get hold of a smartphone that supports Extended Advertising. My Samsung Galaxy S9 does not. 

 The ICS details in the nRF52 with S132 v6.1.1 End Product QDID, just lists Extended Advertising as supported

https://launchstudio.bluetooth.com/ICSDetails/125047

Will ask internally for any test result on this specific scenario. The ble_app_rscs example in the nRF5 SDK uses extended advertising and it has an accompaning central example, i.e.  ble_app_rscs_c.  Not sure if this issues a AUX_CONNECT_REQ to the peripheral. Will check and update the ticket. 

nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_rscs

nRF5_SDK_15.3.0_59ac345\examples\ble_central\ble_app_rscs_c

Best regards

Bjørn