BT SIG certification with KW41Z (TCRL 2020-1)

[dcs_certif]

Hello, we are using KW41Z in BLE products used in industrial environment.

We started BT SIG qualification procedure last year, and we've just finished to pass RF-PHY.TS.15 tests. Unfortunately, BT SIG inconsistencies check tool (launchstudio) still gives several problems, coming from BT protocol stack (then NXP support is mandatory).

Problems are due to the new BT TCRL 2020-1.

Details about inconsistencies are at the end of this message.

I would like to know if a new QDID is available (or will be available) to support this new TCRL ?

If not, it seems impossible for any NXP customer to perform this BT SIG certification.

Thanks for your support !

BRs

Franck

[mario_castaneda]

Hi @dcs_certif,

I hope you are doing great.

We are not keeping component certifications in sync with TCRL releases (that would typically mean 2 certifications per year).

This approach has been used for all platforms since the beginning, but we had an exception to the rule with the security erratum 10734 which was critically and enforced by the BT SIG to keep existing certifications valid.

Some useful BT SIG material regarding product certification that imports a component https://support.bluetooth.com/hc/en-us/articles/360049491051-Component-Test-Evidence-Inheritance

For better information check this with the test house.

Regards,

Mario

[dcs_certif]

Hello Mario,

thanks for your answer...

As the original QDID of KW41Z was emitted since more than 3 years, missing tests have to be redone.

It is my undestanding of the situation.

That's why our BT conslutant and our test house ask us to contact NXP support...

To conclude, is it possible for us to perform these tests without NXP support ?

BLE protocol stack updates are not mandatory to perform these tests ?

Thanks for your support !

BRs,

Franck

[mario_castaneda]

Hi @dcs_certif,

KW41Z QDIDs were renewed in Q3 2019 based on TCRL 2018-2, see below, you were probably looking at the initial listing date.

However, new TCRL can come with new ICS validation issues (not necessarily new mandatory tests). There’s no plan for NXP to renew the KW41 certifications based on TRCL 2020-1.

Is it possible that you could provide a list of ICS consistency errors based on TCRL 2020-1?

Do you use both controller and host QDIDs in their product?

Controller

https://launchstudio.bluetooth.com/ListingDetails/13631

Host

https://launchstudio.bluetooth.com/ListingDetails/13630

Regards,

Mario

[dcs_certif]

Hello Mario,

Thanks for your feedback !

Yes, we are using QDIDs 84041 (host) and 84040 (controller).

I checked on Launch Studio, and these QDIDs are well updated (there is no last version, then as we created the project at the end of 2020, we have the last versions).

As ICS topic is very specific to BT protocol stack (then for specialist), I ‘ll try to sum up our BT consultant conclusion and our comments with colors…

New ICS
Supported in original NXP listing

SKF comments

Dependency Invalid

LL > 4.0HCI 15:C.3 | If [LL] (1/5) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (15/2c, 15/4c, and 15/8) are Mandatory (15/2 and 15/4 previously supported, now 15/2c and 15/4c)

LL > 4.0HCI 15:C.3 | If [LL] (1/4) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (15/2c, 15/4c, and 15/8) are Mandatory (15/2 and 15/4 previously supported now 15/2c and 15/4c)

LL > 4.0HCI 16:C.4 | If [LL] (9/1) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (16/32-36, 16/37b, 16/38b, and 16/39) are Mandatory – new ICS added after original listing

LL > 4.0HCI 16:C.7 | If [LL] (9/1 and 9/2) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (16/48b) is Mandatory – new ICS added after original listing

LL > 4.0HCI 5:C.9 | If [LL] is Supported and [LL] (9/13) is Not Supported then [4.0HCI] (5/27-32) are Excluded – can exclude now

LL > 4.0HCI 6:C.9 | If [LL] is Supported and [LL] (9/13) is Not Supported then [4.0HCI] (6/26) is Excluded – can exclude now

LL > 4.0HCI 7:C.10 | If [LL] is Supported and [LL] (9/13) is Not Supported then [4.0HCI] (7/39 and 7/40) are Excluded – can exclude now

LL > 4.0HCI 7:C.24 | If [LL] is Supported and [LL] (9/13 and 5/4) are Not Supported then [4.0HCI] (7/38) is Excluded – can exclude now

LL > 4.0HCI 8:C.3 | If [LL] (1/5) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (8/5b, 8/6, 8/7, and 8/8b) are Mandatory – new ICS added after original listing (8/8 previously supported, now 8/8b)

LL > 4.0HCI 8:C.3 | If [LL] (1/4) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (8/5b, 8/6, 8/7, and 8/8b) are Mandatory - new ICS added after original listing (8/8 previously supported, now 8/8b)

25:C.5 | If [GAP] (5/3 and 25/9) are Supported then [GAP] (25/13) is Mandatory – new ICS added after original listing

35:C.4 | If [GAP] (5/4 and 35/9) are Supported then [GAP] (35/13) is Mandatory– new ICS added after original listing

Any test cases triggered by new ICS will require additional test evidence, NXP would need to provide this by comparing their old Test Plan to a new one with ICS inconsistencies cleared.

Do you think that QDIDs from Q3/2019 (based on TCRL 2018-2) will solve these issues ?

If not, and assuming that NXP will not update KW41 certification, SKF will not pass BT SIG certification.

The next two are related to Core Erratum and need to be fixed.

34:C.9 | If [SUM ICS] (31/17 and 52/1) are Supported then [SUM ICS] (34/15) is Mandatory – this relates to Core Erratum 11838 Key Size Updates. Adopted 13 August 2019 (has to be implemented)

21:C.4 | If [SUM ICS] (21/14) is Supported then [SUM ICS] (21/19) is Mandatory – this relates to Core Erratum 11838 Key Size Updates. Adopted 13 August 2019 (has to be implemented)

Do you think that QDIDs from Q3/2019 (based on TCRL 2018-2) will solve these 2 issues ?

If not, and assuming that NXP will not update KW41 certification, SKF will not pass BT SIG certification.

Thanks for your support !

BRs

Franck

[mario_castaneda]

Hi @dcs_certif,

We have created 2 new Bluetooth Launch Studio projects for controller and host, based on the existing QDIDs, and updated them to TCRL 2020-1. You could easily generate those on your end.

Please find my analysis below in purple.

Based on this analysis, NXP has to provide evidence only for 2 Host test cases that are related to core erratum 11838 (see attachment with the logs to be shared with the test house).

Could you please confirm that you are working with the KW41Z connectivity software - SDK 2.2.3 (MR4.1), Oct-2020, which includes a fix for erratum 11838.

New ICS
Supported in original NXP listing

SKF comments

Dependency Invalid

LL > 4.0HCI 15:C.3 | If [LL] (1/5) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (15/2c, 15/4c, and 15/8) are Mandatory (15/2 and 15/4 previously supported, now 15/2c and 15/4c)

LL > 4.0HCI 15:C.3 | If [LL] (1/4) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (15/2c, 15/4c, and 15/8) are Mandatory (15/2 and 15/4 previously supported now 15/2c and 15/4c)

LL > 4.0HCI 16:C.4 | If [LL] (9/1) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (16/32-36, 16/37b, 16/38b, and 16/39) are Mandatory – new ICS added after original listing

LL > 4.0HCI 16:C.7 | If [LL] (9/1 and 9/2) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (16/48b) is Mandatory – new ICS added after original listing

• [NXP] No new tests for additional ICS, and the feature is already supported in KW41Z

LL > 4.0HCI 5:C.9 | If [LL] is Supported and [LL] (9/13) is Not Supported then [4.0HCI] (5/27-32) are Excluded – can exclude now

LL > 4.0HCI 6:C.9 | If [LL] is Supported and [LL] (9/13) is Not Supported then [4.0HCI] (6/26) is Excluded – can exclude now

LL > 4.0HCI 7:C.10 | If [LL] is Supported and [LL] (9/13) is Not Supported then [4.0HCI] (7/39 and 7/40) are Excluded – can exclude now

LL > 4.0HCI 7:C.24 | If [LL] is Supported and [LL] (9/13 and 5/4) are Not Supported then [4.0HCI] (7/38) is Excluded – can exclude now

• [NXP] Removed from Bluetooth Launch Studio project

LL > 4.0HCI 8:C.3 | If [LL] (1/5) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (8/5b, 8/6, 8/7, and 8/8b) are Mandatory – new ICS added after original listing (8/8 previously supported, now 8/8b)

LL > 4.0HCI 8:C.3 | If [LL] (1/4) and [4.0HCI] (1a/4) are Supported then [4.0HCI] (8/5b, 8/6, 8/7, and 8/8b) are Mandatory - new ICS added after original listing (8/8 previously supported, now 8/8b)

• [NXP] No new tests for additional ICS, and the feature is already supported in KW41Z

25:C.5 | If [GAP] (5/3 and 25/9) are Supported then [GAP] (25/13) is Mandatory – new ICS added after original listing

35:C.4 | If [GAP] (5/4 and 35/9) are Supported then [GAP] (35/13) is Mandatory– new ICS added after original listing

•  [NXP] No new tests for additional ICS, and the feature is already supported in KW41Z

Any test cases triggered by new ICS will require additional test evidence, NXP would need to provide this by comparing their old Test Plan to a new one with ICS inconsistencies cleared.

Do you think that QDIDs from Q3/2019 (based on TCRL 2018-2) will solve these issues ?  If not, and assuming that NXP will not update KW41 certification, SKF will not pass BT SIG certification.

• All new ICSes mentioned above should be checked in the product project based on TCRL 2020-1, they are supported and do now require additional test evidence.

The next two are related to Core Erratum and need to be fixed.

34:C.9 | If [SUM ICS] (31/17 and 52/1) are Supported then [SUM ICS] (34/15) is Mandatory – this relates to Core Erratum 11838 Key Size Updates. Adopted 13 August 2019 (has to be implemented)

21:C.4 | If [SUM ICS] (21/14) is Supported then [SUM ICS] (21/19) is Mandatory – this relates to Core Erratum 11838 Key Size Updates. Adopted 13 August 2019 (has to be implemented)

Do you think that QDIDs from Q3/2019 (based on TCRL 2018-2) will solve these 2 issues ? If not, and assuming that NXP will not update KW41 certification, SKF will not pass BT SIG certification.

• Only the Host ICS related to core erratum 11838 comes with additional testing: GAP/SEC/SEM/BI-09-C, GAP/SEC/SEM/BI-10-C. Attached new test evidences to be used for the current product certification based on TCRL 2020-1.

Regards,

Mario

[dcs_certif]

Hello Mario,

thanks for your answer.

On Lanch studio, when you select KW41Z, there is no choice on QDID.

I checked it in July, and it was the same choice as 6 months ago.

As NXP has created new projects, when new QDIDs will be available ?

SDK version is under checking...

I don't find attachment you mentionned for erratum 11838.

Thanks

BRs

Franck

[mario_castaneda]

Hi @dcs_certif,

The information will be handled internally. An NXP representative will get in contact with you.

Regards,

Mario

[dcs_certif]

Hello Mario,

thanks for the internal handling...

I'm still waiting the NXP representative contact.

Do you have a delay for this contact ?

Thanks for your support !

Franck

[mario_castaneda]

Hi @dcs_certif,

I could provide the information that you need internnaly

Could you please look at the next link?

https://www.nxp.com/video/tutorial-for-nxp-support-case-portal:NCP-VIDEO

https://support.nxp.com/s/

Regards,

Mario

[mario_castaneda]

Hi Frank,

I could answer these questions internally.

Could you please look at the next link

https://www.nxp.com/video/tutorial-for-nxp-support-case-portal:NCP-VIDEO

https://support.nxp.com/s/

Regards,

Mario