How to enable Bluetooth 5 long range advertisements

[Peter Lerup]

Hi,

I'm experimenting with the nrf52840 preview board.

I have tried the example "ble_app_att_mtu_throughput" using the coded option to check the extended range and it works fairly well. I heard that there is a bug in the sd which cripples the actual range though...

My question is regarding extended range advertising. It looks like the BLE_GAP_PHY_CODED option is something that is set up via negotiation during the actual connection.

What is the proper way to set up advertising so that BLE 5 devices can get the extended range during advertisement phase.

Thanks /Peter Lerup

[Ulrich Myhre]

The Advertising Sets feature is only a part of the Advertising Extensions. That part is not completed yet, but we wanted early feedback on our API.

[Mohammad Afaneh]

Ulrich,

Looks like there are missing files that need to be updated in the SDK to get the ble_app_att_mtu_throughput_example_connecting_on_long_range example to compile. One example is the ble_advertising.c. It has references to BLE_GAP_ADV_MAX_SIZE which doesn't exist anymore, and I can't file an updated file from the example to overwrite the one in the SDK.

Any ideas where I can get the necessary updated files?

[Ulrich Myhre]

It seems like you forgot the step where you copy the header files from the release bundle and replace them with the s140 ones inside the SDK folder. When skipping that, I got similar errors. Either that, or you are using an incompatible SDK version. Please follow the instructions in the readme.md file inside the example to the letter. For me it built just fine, going from a fresh compile using Keil.

[Mohammad Afaneh]

Ulrich,

I went through the steps and just read them again (to make sure). I'm using the SDK version 13.0.0, and I replaced the files within the SDK with the headers included in the s140 5.0.0-3.alpha release.

However, the file I'm referring to within the SDK is in the path components/ble/ble_advertising which is not included with the s140 release's header files (which get placed in components/softdevice/s140).

I even checked out the 13.1.0 SDK release and that one also includes the references to the macro BLE_GAP_ADV_MAX_SIZE which doesn't exist in the new version of s140.

[Mohammad Afaneh]

Ulrich,

One thing I didn't mention is that I'm trying to include the new s140 headers into an existing project of mine, and so this existing project might be including files that have not been updated yet (such as the ble_advertising.c file). This may be causing the issue I'm running into. I will try running the example app separately first, and then figure out how to incorporate the changes and migrate my existing app to the new s140 release.