Not supported yet. And, there has been no deadline set or plan in progress towards its completion, yet.
Best said, it will be supported when there is a strong requirement and resources assigned (or there is a community contribution) or as a dependency to other features that may be planned into the roadmap.
That said, there is very experimental initial work of having non-connectable non-scannable advertising implementation that can be tested in the shell application using advx and scanx commands. This may be broken, as I have not tested it for a long time. At present, the implementation may only be there as an inspiration to pick it up and continue the implementation towards a full feature support. Efforts may range upto 6 man months (finger in the air).
-Vinayak
toggle quoted message
Show quoted text
-----Original Message-----
From: Giuliano Franchetto <giuliano.franchetto@...>
Sent: 04 June 2019 16:22
To: Chettimada, Vinayak Kariappa
<vinayak.kariappa.chettimada@...>; a.feil@...;
users@...
Subject: RE: [Zephyr-users] #ble #nrf52840 Setting LE Coded PHY
Hi Vinayak,
When you say " Long range is not supported in advertising", does it mean " Long
range **will never be** supported in advertising" or " Long range is not
supported in advertising **yet**" ?
If this is the later, is there a milestone for this functionnality?
Regards
-----Message d'origine-----
De : users@... <users@...> De la part de
via Lists.Zephyrproject.Org Envoyé : mardi 4 juin 2019 15:30 À :
a.feil@...; users@... Cc :
users@... Objet : Re: [Zephyr-users] #ble #nrf52840 Setting
LE Coded PHY
Well, I can compile and run the zephyr samples (e. g. peripheral_hr
and central_hr). They are using longe range. I am now wondering how I can
set which phy (S=8 or S=2) should be used (for advertising and connection).
Long range is not supported in advertising (Extended Advertising feature is not
supported), hence long range connection too cannot be established. After
legacy connection is established Bluetooth Host performs a PHY update
procedure to achieve a preferred 2M PHY connection (by default, behaviour if
peer supports 2M). This code is internal in hci_core.c, you may change the
preferred PHY to S8 or S2 instead for experimentation (only). Feel free to revert
back if you face issues.
- Vinayak
