This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Assistance in the Bluetooth SIG Qualification Process

Dear Nordic Team,

The founders Lukas Pilat and Robert Kopka have met your representatives at the Light & Building conference yesterday. They recommended us to get in touch with Nordic via a private ticket to get assistance through the Bluetooth SIG Qualification process.

So far we have registered with die Bluetooth SIG, defined a project with our best knowledge, bought the PTS dongle and got familiar with the PTS Software. Currently we try to pass all test steps.

It would be great if you could give us some tips and tricks in general about the whole qualification process and how to efficiently qualify a product. Further a technical contact for detailed questions concerning the single test steps in PTS would help us a lot.

Sincerly,

  Thomas

Parents
  • Hey,

    We are developing a custom hardware, which is very different to the layout of the nRF52 Development Kit PCA10040 (I assume you regard to this layout when you say "reference layout")

    Since we therefore need to go with "Required Testing", here some questions:

    1. Should we include another prequalified design (QDID)? As explained in the introduction, do we use the nrf52832 with the S132 v3.0.0. If "Yes",  which design (QDID) shall we include
    2. If we inlcude a QDID: Shall we modify it to represent what the capabilities of our firmwware are  or leave it as it is?
    3. Eitherway the consistency check will force us to include functionalities we have not implemented as our product does not need to support it, like non-discoverable e.g. Is it ok if we write a special firmware just to cover these tests but which will not be part of the final product-firmware?

    Thanks in advance,

       Thomas

Reply
  • Hey,

    We are developing a custom hardware, which is very different to the layout of the nRF52 Development Kit PCA10040 (I assume you regard to this layout when you say "reference layout")

    Since we therefore need to go with "Required Testing", here some questions:

    1. Should we include another prequalified design (QDID)? As explained in the introduction, do we use the nrf52832 with the S132 v3.0.0. If "Yes",  which design (QDID) shall we include
    2. If we inlcude a QDID: Shall we modify it to represent what the capabilities of our firmwware are  or leave it as it is?
    3. Eitherway the consistency check will force us to include functionalities we have not implemented as our product does not need to support it, like non-discoverable e.g. Is it ok if we write a special firmware just to cover these tests but which will not be part of the final product-firmware?

    Thanks in advance,

       Thomas

Children
No Data
Related