Advertise two connectable peripherals from one board

[Moh]

I am using nrF5340DK board. I want to advertise two connectable peripherals from one board. Using the sample application of Multi-advert, I able to advertise one peripheral as connectable and other as non-connectable. When I run this code, I can see both advertise on the client side (nrf connect app). When I modify the code to advertise both as non-connectable, I can see both non-connectable peripherals advertise on the client side (nrf connect app). But when I modify the code to advertise both as connectable, I can see only first connectable peripherals advertised on the client side (nrf connect app) and other one got failed to advertise. 

Kindly can you please advise the required configurations I need in firmware to achieve this.

Kind Regards,

Moh

[Einar Thorsrud]

Hi Moh,

Are you refering to Bluetooth: Multiple advertising sets? If so, you should be able to make it do two connectable advertisers with small modifications, by changing the flags of the non-connectable advertiser to be connectable, and adding somethign like CONFIG_BT_MAX_CONN=4 in your prj.conf.

Note that it will not look sensible in for instance iOS, as it will see it as the same device. So to verify that you actually got two connectable advertisiers, you can use a sniffer. (This brings up the point that multiple connectable advertisers are perhaps not that usefull in practice, ans not commonly supported or used).

[Moh]

Hi Einar,

I have made the changes as per your suggestions but still no luck. Please find the code attached as well as the screen shot below.

Kind Regards,

Moh

multiple_adv_sets.zip

[Einar Thorsrud]

Hi,

You are right. On the nRF53 you also need to add CONFIG_BT_CTLR_SDC_PERIPHERAL_COUNT=2 (or a higher number) in the network core configuration (so hci_rpmsg or hci_ipc depending on which SDK version you are using).

[Moh]

Hi Einar,

When I try to set CONFIG_BT_CTLR_SDC_PERIPHERAL_COUNT=2, I am getting build errors. Do you know what other dependecies I need to set? Thanks 

Moh

[Einar Thorsrud]

Hi Moh,

I did a very quick test here that works on my end. Note that these are minimal changes to the sample so it is very dirty, but you get two connectable advertisers: 7180.multiple_adv_sets.zip.

I am curious in which practical application this makes sense?

Einar

[Moh]

Hi Einar,

I have managed to build but still I am seeing following error

*** Booting Zephyr OS build v3.2.99-ncs2 ***
Starting Bluetooth multiple advertising sets example
Bluetooth initialized
Created adv: 0x20000d18
Non-connectable advertising started
Created adv: 0x20000d68
E: Failed to start advertiser
Failed to create a connectable advertising set (err -111)

Moh

[Einar Thorsrud]

Hi Moh.

I should have been more specific. I tested the project I uploaded on nRF Connect SDK 2.6.0 (the latest release) and build for nrf5340dk_nrf5340_cpuapp. Does it work for you with that combinarion?