BLE certification of the Nimble stack

[Klaus Hagen <kl...@gmail.com>]

Hi,

Is or will released Nimble stack versions be Bluetooth SIG qualified in the
future? Or are companies integrating the Nimble stack supposed to get their
own qualification done?

Br,
Klaus

Re: BLE certification of the Nimble stack

[Szymon Janc <sz...@codecoup.pl>]

Hi,

On 4 January 2017 at 18:22, Klaus Hagen <kl...@gmail.com> wrote:
> Hi,
>
> Is or will released Nimble stack versions be Bluetooth SIG qualified in the
> future? Or are companies integrating the Nimble stack supposed to get their
> own qualification done?

You always have to qualify your product before going with it to market.

Yet, there are few thing we could do to make this as simple as
possible for companies using Mynewt.
1) provide TPG and tests results/instructions for PTS
   This is already in tree with instructions for GAP, GATT, SM and
L2CAP. Currently this provides instructions
   only for test cases implemented by PTS. For those not implemented
you still need to provide proofs possibly
   with device-device tests. This is something we could consider with
special application as remote device but
   for now we are focusing on PTS only.   (check net/nimble/host/pts/)

   Same could also be done for controller code and for GATT applications.

2) provide controller and host certification for specific code version
(tag?). In case of controller code this would be
    tided to a specific HW. This would allow application makers to
refer to QDID of host and/or controller and only
    qualify GATT applications.
3) same as 2 + provide  high level API for GATT profiles (or sample
applications with specific profiles) and
   also qualify profile. This should allow to refer to those QDID and
not require full qualification process.
   (this is something that could be coupled with SDK if Mynewt get one..)

All this of course costs money and time. There is also question on how
2) and 3) should be handled WRT
host+controller build running on same core, source code being
available (thus leaving possible for changes) etc.

Never the less this is something worth considering in long run.

-- 
pozdrawiam
Szymon K. Janc

Re: BLE certification of the Nimble stack

[Tim Hutt <td...@gmail.com>]

I don't think the 20 byte limit was due to a decision by Nordic. It is part
of the BLE spec and be increased using the packet length extension which
the nRF52 supports.

On 4 January 2017 at 17:30, Kevin Townsend <ke...@adafruit.com> wrote:

> This is something I've been curious about myself as well. Nimble is still
> a work in progress, but I've wondered if there were any plans once the
> final 1.0 release is done and initial development is considered closed.
>
> The SD from Nordic has some significant trade-offs in terms of losing real
> time control of the system, and being limited by the design decisions made
> by Nordic (20 bytes per packet), but it does make it much easier to sell
> products since part of the certification process is handled by Nordic.
> Particularly for low volume, low cost products the thousands of
> dollars/Euros saved here can have a big impact on total per device cost,
> and every bit matters in a startup.
>
> What would the financial burden be of getting a 1.0 Nimble through
> certification along with some certified code for a handful of common
> services/characteristics defined by the SIG? You will still always need to
> register your product with the SIG (which costs money), as well as getting
> FCC certification (which will also cost money), but if the stack itself is
> certified that's one less step to take and one less cheque to write for
> Mynewt users.
>
> K.
>
>
>
> On 04/01/17 18:22, Klaus Hagen wrote:
>
>> Hi,
>>
>> Is or will released Nimble stack versions be Bluetooth SIG qualified in
>> the
>> future? Or are companies integrating the Nimble stack supposed to get
>> their
>> own qualification done?
>>
>> Br,
>> Klaus
>>
>>
>

Re: BLE certification of the Nimble stack

[Kevin Townsend <ke...@adafruit.com>]

This is something I've been curious about myself as well. Nimble is 
still a work in progress, but I've wondered if there were any plans once 
the final 1.0 release is done and initial development is considered closed.

The SD from Nordic has some significant trade-offs in terms of losing 
real time control of the system, and being limited by the design 
decisions made by Nordic (20 bytes per packet), but it does make it much 
easier to sell products since part of the certification process is 
handled by Nordic. Particularly for low volume, low cost products the 
thousands of dollars/Euros saved here can have a big impact on total per 
device cost, and every bit matters in a startup.

What would the financial burden be of getting a 1.0 Nimble through 
certification along with some certified code for a handful of common 
services/characteristics defined by the SIG? You will still always need 
to register your product with the SIG (which costs money), as well as 
getting FCC certification (which will also cost money), but if the stack 
itself is certified that's one less step to take and one less cheque to 
write for Mynewt users.

K.


On 04/01/17 18:22, Klaus Hagen wrote:
> Hi,
>
> Is or will released Nimble stack versions be Bluetooth SIG qualified in the
> future? Or are companies integrating the Nimble stack supposed to get their
> own qualification done?
>
> Br,
> Klaus
>