Thanks for the heads-up, Szymon. How does the bt5 implementation of "multiple advertising instances" relate to the corresponding vendor extension that's currently in master?
-- simon On Tue, Jul 18, 2017 at 12:33 PM, Szymon Janc <[email protected]> wrote: > Hi, > > This is to give community a heads up that we are going to merge bluetooth5 > branch [1] into master very soon. This is rather big feature so don't be > surprised about amount of new code. > > Feature wise this includes: > - Channel Selection Algorithm #2 > - High Duty non-connectable advertising > - LE 2M and LE coded (aka long range) PHYs > - Extended Advertising (both advertiser and scanner, no chaining support) > - multiple advertising instances (controller only) > > Note that this branch also get rid of support for 1M clock and 32K clock is > not required for running nimBLE stack. > > Note that controller is now optimized to work with low power 32768 Hz and > does not work with 1 MHz clock anymore. For details see existing BSP-s > which are already preconfigured for new clock or check updated > documentation. > > -- > pozdrawiam > Szymon K. Janc >
