Re: Handling Notify/Indicate and CCCD Changes

On Sat, Jul 16, 2016 at 12:10:14AM +0200, Kevin Townsend wrote: > I don't think the disconnect is a massive issue at this point and worth > a lot of effort. There are higher priorities as you said, which gets a > +1 from me anyway, and it isn't entirely unreasonable based on the spec > (thanks

Re: Handling Notify/Indicate and CCCD Changes

Hi Chris, Thanks for the quick response. I think CCCD events are quite important from a power management perspective and worth clearly exposing. 2. How is a failed 'indicate' message handled? Indicate generates an ACK, but are there any examples or documentation around how to properly

Re: Handling Notify/Indicate and CCCD Changes

Hi Kevin, On Fri, Jul 15, 2016 at 04:50:14PM +0200, Kevin Townsend wrote: > My apologies if I'm missing something in the documentation, but putting > an example together here we are almost done with a barebones app > implementing Nordic's UART service to reuse the apps we've published for >

Re: BLE link layer

Hi Hamid, Welcome to the Apache Mynewt community! 1. Your will find the source code on github: https://github.com/apache/incubator-mynewt-core/tree/master/net/nimble 2. Yes - it’s a full controller implementation.

BLE link layer

Hello, I would like to replace Nordic nRF51 SoftDevice with your BLE stack to have this possibility to add my own proprietary LLID to link layer. I have two questions and I will appreciate your assistance: 1- Where I can find the source code of BLE controller including link layer of your