Hi,
On 4 January 2017 at 18:22, Klaus Hagen <[email protected]> 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
