-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: Bluetooth qualification #9705
Conversation
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
daad174
to
c9bd5cf
Compare
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Note: This message is automatically posted and updated by the CI |
f488c8b
to
089920d
Compare
089920d
to
610b8aa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a few minor comments to clarify.
610b8aa
to
9539196
Compare
9539196
to
ed65c0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The update looks good.
ed65c0f
to
023ab4f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK.
0fccd7a
to
25a82ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments about text cohesion.
As a side note, I would like to see some figures that present the whole process visually. Bluetooth SIG's resources are text-heavy and I couldn't find any overview diagram under the links used on the page. It's really hard to go through wall of texts with different naming conventions for people new to the process, and the more we can do to save tech support some time, the better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me.
0f899c8
to
f61f1d4
Compare
73ebc2f
to
a19f96f
Compare
Hi All, the PR is ready for your final review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed from the Bluetooth stack user perspective, I don't know much about the qualification process itself so I leave this aspect to other reviewers.
The chapter looks very good, it's well-organized and informative.
It may require a certain level of maintenance in case links, terminology or BT SIG policy changes in future.
|
||
Any qualified design offered by Nordic Semiconductor (for example, :ref:`ug_bt_mesh` versions) can be qualified independently by the customers. | ||
However, this process may be complex and time-consuming, thus it is recommended to inherit Nordic Semiconductor's design qualifications in your End Product's listing. | ||
If you want to create a Profile Subsystem that is not on the `Bluetooth Qualification Listing`_ yet, run the relevant tests through the `Profile Tuning Suite (PTS)`_ tool and qualify the product. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to create a Profile Subsystem that is not on the `Bluetooth Qualification Listing`_ yet, run the relevant tests through the `Profile Tuning Suite (PTS)`_ tool and qualify the product. | |
If you want to create a Profile Subsystem that is not on the `Bluetooth Qualification Listing`_, run the relevant tests through the `Profile Tuning Suite (PTS)`_ tool and qualify the product. |
|
||
Before you start the `Bluetooth SIG's Qualification Process`_, ensure the following: | ||
|
||
1. You have access to your member company's account. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. You have access to your member company's account. | |
#. You have access to your company's member account. |
1. You have access to your member company's account. | ||
To check if your company is already a SIG member, go to `Join Bluetooth SIG`_ page and search the Member Directory list. | ||
|
||
2. Get acquainted with the Program Reference Document (PRD) and Declaration Process Document (DPD), that will help you to understand the basics. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. Get acquainted with the Program Reference Document (PRD) and Declaration Process Document (DPD), that will help you to understand the basics. | |
#. Get acquainted with the Program Reference Document (PRD) and Declaration Process Document (DPD) to understand the basics of the qualification process. |
To check if your company is already a SIG member, go to `Join Bluetooth SIG`_ page and search the Member Directory list. | ||
|
||
2. Get acquainted with the Program Reference Document (PRD) and Declaration Process Document (DPD), that will help you to understand the basics. | ||
Log into your member company's account to review both `PRD and DPD`_ documents. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Log into your member company's account to review both `PRD and DPD`_ documents. | |
Log into your company's member account to review both `PRD and DPD`_ documents. |
Qualification process | ||
********************* | ||
|
||
Although you can use pre-qualified designs, any Bluetooth Product qualification cannot be simply inherited with no action required from your end. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although you can use pre-qualified designs, any Bluetooth Product qualification cannot be simply inherited with no action required from your end. | |
Although you can use pre-qualified designs, Bluetooth Product qualification can only be inherited through action on your end. |
* You want to switch to another major |NCS| version for an existing product. | ||
* In some cases, if you want to switch to another minor |NCS| version for an existing product. | ||
|
||
It may happen that you would need to alter the configuration of the qualified design or slightly modify small parts of the existing design to better fit your application needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may happen that you would need to alter the configuration of the qualified design or slightly modify small parts of the existing design to better fit your application needs. | |
You might need to alter the configuration of the qualified design or slightly modify parts of the existing design to better fit your application needs. |
* Ensure that the resulting design does not change the Implementation Conformance Statement (ICS) that has already been declared for a relevant Nordic Semiconductor's qualified design. | ||
* Ensure that the resulting design does not break the qualification of the existing design. | ||
|
||
You can do so by running relevant qualification tests using test tools indicated in the 'Launch Studio'_ tool. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can do so by running relevant qualification tests using test tools indicated in the 'Launch Studio'_ tool. | |
You can complete the checks by running relevant qualification tests using test tools indicated in the 'Launch Studio'_ tool. |
|
||
#. Open the Bluetooth QDIDs article and, based on the table, confirm the following information: | ||
|
||
* That the version you want to use is compatible with versions of other Subsystems you want to keep for your product. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* That the version you want to use is compatible with versions of other Subsystems you want to keep for your product. | |
* The version you want to use must be compatible with versions of other Subsystems you want to keep for your product. |
|
||
#. Navigate to the relevant Compatibility Matrix directory. | ||
|
||
#. Open the Bluetooth QDIDs article and, based on the table, confirm the following information: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#. Open the Bluetooth QDIDs article and, based on the table, confirm the following information: | |
#. Open the Bluetooth QDIDs article and, based on the table, confirm the following: |
#. Open the Bluetooth QDIDs article and, based on the table, confirm the following information: | ||
|
||
* That the version you want to use is compatible with versions of other Subsystems you want to keep for your product. | ||
* That relevant Host and SoftDevice Controller Subsystems implemented in the |NCS| version you want to use are pre-qualified. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* That relevant Host and SoftDevice Controller Subsystems implemented in the |NCS| version you want to use are pre-qualified. | |
* Relevant Host and SoftDevice Controller Subsystems implemented in the |NCS| version you want to use must be pre-qualified. |
776fb36
to
0889264
Compare
Hello, I think the PR is good enough, and it will be nice to merge it as soon as possible. |
@annakielar, please rebase as it is having conflict. |
b8a0d6a
to
d40e24a
Compare
Added a new article about the Bluetooth qualification process. Added a page gathering all Bluetooth-related topics in Protocols. Added a few links to links.txt. Signed-off-by: Anna Kielar <anna.kielar@nordicsemi.no>
d40e24a
to
cc50e4e
Compare
[celebrate] Kulkarni, Omkar reacted to your message:
…________________________________
From: Jamie ***@***.***>
Sent: Tuesday, September 26, 2023 10:47:36 AM
To: nrfconnect/sdk-nrf ***@***.***>
Cc: Kulkarni, Omkar ***@***.***>; Mention ***@***.***>
Subject: Re: [nrfconnect/sdk-nrf] doc: Bluetooth qualification (PR #9705)
Merged #9705<#9705> into main.
—
Reply to this email directly, view it on GitHub<#9705 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHTKHAC5PGVA6GG4CY3HU4DX4KXERANCNFSM6AAAAAAS7WCJNQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
[celebrate] Kulkarni, Omkar reacted to your message:
…________________________________
From: Grzegorz Ferenc ***@***.***>
Sent: Tuesday, September 26, 2023 10:46:42 AM
To: nrfconnect/sdk-nrf ***@***.***>
Cc: Kulkarni, Omkar ***@***.***>; Mention ***@***.***>
Subject: Re: [nrfconnect/sdk-nrf] doc: Bluetooth qualification (PR #9705)
@greg-fer approved this pull request.
—
Reply to this email directly, view it on GitHub<#9705 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHTKHACKT27BOLXFHFWEB73X4KXBFANCNFSM6AAAAAAS7WCJNQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Added a new article about the Bluetooth qualification process. Added a few links to links.txt.
Signed-off-by: Anna Kielar anna.kielar@nordicsemi.no