Hi Will, I did a quick check but did not see support in the bluetooth5 branch.
I'll work on expanding support in 4.2 for now. You're right, I'm not planning to do any connected advertising at all, I just want to see how the chip performs when trying to advertise both eddystone and iBeacon interleaved with each other. If I get stuck, I'll be sure to reach out. Thanks! Gurpreet On Wed, May 10, 2017 at 4:26 PM, will sanfilippo <wi...@runtime.io> wrote: > I would say the bluetooth5 branch is fairly stable but I am not in the > best postiion to comment on it. Furthermore, I am not sure if the > multi-advertising support has been fully added to that branch. If it has > been added I would go ahead and use it as it should be fairly stable. > > If you wanted to expand support for multiple advertisers in 4.2 it sounds > like you are going about it the correct way: use the code from the bletest > app to construct your HCI commands to send to the controller. Presumably > you are not doing any connected advertising so all you need to do is write > wrappers for the bletest code and you should be fine. I realize that I did > not give you detailed information on exactly what to do but it sounds like > you have a decent handle on it. > > If you have questions about the bletest code let us know and we can answer > them. > > > On May 10, 2017, at 4:15 PM, Gurpreet Singh <gurpr...@mistsys.com> > wrote: > > > > Hi Will, > > > > Thanks for the quick response. The controller only support on 4.2 makes > > sense based on what I found in the source code. (I found some test code > > that exercises this, and was trying to build on top of that.) > > > > How stable would you say the bluetooth5 branch is? If I wanted to try > this > > feature out as I build out a quick prototype while exploring the use of > > Nimble/MyNewt, do you think I'd be hampered too much? Alternatively, some > > quick pointers on how to expand this support in the 4.2 codebase to the > > host code will be welcomed as well. > > > > -Gurpreet > > > > > > > > On Wed, May 10, 2017 at 4:05 PM, will sanfilippo <wi...@runtime.io> > wrote: > > > >> Hello Gurpreet: > >> > >> So a few things here: > >> > >> The multi-advertising support that was added was “vendor specific”, > >> meaning that it is (or shall I say was) not in the BLE specification at > the > >> time the code was written. Bluetooth 5 adds support for > multi-advertising > >> and that standard support will be added to Mynewt. Actually, it might > >> already be there; I know it is in process on the bluetooth5 branch but > it > >> may not be fully complete. > >> > >> The Mynewt code that supports 4.2 only supports mutliple advertisers in > >> the controller; it does not support them through the host API. If you > are > >> using the combined host-controller you will have to write some of your > own > >> code to deal with advertising instances other than the default. This is > not > >> terribly difficult to do and we could provide some help/pointers if > needed. > >> > >>> On May 10, 2017, at 3:56 PM, Gurpreet Singh <gurpr...@mistsys.com> > >> wrote: > >>> > >>> Hi, > >>> > >>> I've been playing around with MyNewt and Nimble on the nRF52dk board, > and > >>> noticed the recently added support for multiple advertising instances > >>> (MYNEWT-508). (BLE_MULTI_ADV_SUPPORT) > >>> > >>> I want to use this to set up interleaved Eddystone and iBeacon > >>> advertisements, but it doesnt look like those APIs support this quite > >> yet? > >>> Or perhaps, I'm missing something? > >>> > >>> I'd appreciate any insight, or thoughts. > >>> > >>> Thanks in advance > >>> GPS > >> > >> > >
