Testplan generation in Bluetooth Launch Studio

[WoutZenso]

Hello,

We are currently trying to find our way in all the documentation and procedures required to qualify our product with the Bluetooth SIG. I am using their Launch Studio for automatic generation of a testplan but I have some unclearities. I some of you have some experience using this tool.

Since we are using the nRF52832CIAA with S132 V5.0.0, I put 97989 as QDID in the "Previously Qualified Design Used in this Qualification" in the "Project Basics" tab. When I proceed to the "ICS Selection" tab, there are already a lot of boxes checked based on the layers selected in the "Layer Selection" tab, which are in turn based on the passed QDID. If I (un)check a box, a warning pops up indicating that the current selection is based on an integrated design and that changing the selection may lead to additional testing.

My question now is if we have to make a selection based on a generic use case (which will be the case for the QDID provided), or if we have to customize the selection based on our specific use-case? To illustrate I included a copy of a part of the GAP section of the "ICS Selection" tab

Modes

Table 5: LE Roles

Prerequisite: GAP 0/2

Support	Item	Capability	System Spec Reference	Status	Comment
x	5/1	Broadcaster	[3] or [7] 2.2.2	C.1	C.1: It is mandatory to support at least one of the defined roles.
x	5/2	Observer	[3] or [7] 2.2.2	C.1	C.1: It is mandatory to support at least one of the defined roles.
x	5/3	Peripheral	[3] or [7] 2.2.2	C.1	C.1: It is mandatory to support at least one of the defined roles.
x	5/4	Central	[3] or [7] 2.2.2	C.1	C.1: It is mandatory to support at least one of the defined roles.

All the boxes are checked initially, however we only require the Peripheral role. Should I uncheck the other boxes making it custom for our application (and opposing the warning that I am altering the selection based on the previously qualified integrated design), or can I leave the other boxes checked as we are using the QDID provided which is able to support all these roles?

Thank you for any enlightment on this subject!

[Kenneth]

Hi, you should not un-check anything. Leave them as-is, even if you don't use them all in your application.

[WoutZenso]

Thank you Kenneth for you answer.

This brings me to a second problem. When I perform the consistency check within Launch Studio, there seems to be an inconsistency with the L2CAP tab. By default, option 2/45 (Send Disconnect Request Commands) is checked. However, this requires 2/1 (Support of L2CAP signalling channel) to be checked as well, which it is not. The comments also state that this is mandatory for 0/1 (BR/EDR role) and 0/3 (BR/EDR/BLE role), but we only require 0/2 (BLE only role). If I uncheck 2/45, the popup warns me again that I am changing the integrated design.

Have you experienced this before?

Thanks!

[Kenneth]

2/45 can be checked if (2/40 and 2/46 is supported) OR (2/1 is supported).
We don't support 2/1, since it applies to BR/EDR. However we do support 2/40 and 2/46, so 2/45 can be checked.
So, not sure exactly what is causing the problem, maybe you have unchecked something elsewhere.

[WoutZenso]

Apparently there is also a 2/45a which is specific for BLE. I checked that box and unchecked the 2/45 one. There is still that warning popping up, but I can choose to 'cancel' it, with the box still being checked.