update softdevice version

[moon.kim]

Hello.

I developed the device using the nRF52810.

SDK 15.0.0 and S112 6.0.0 were used.

I recently noticed a new Bluetooth Core Specification v5.1 update to S112 Ver 7.0.1.

Do I need to change my soft device version for certification like Bluetooth SIG / CE / FCC?

[bjorn-spockeli]

Hi Moon.kim, 

No, an End Product QDID is valid as long as the underlying specification it is qualified against is not deprecated or withdrawn. So you can safely use the S112 v6.0.0 End Product QDID, https://launchstudio.bluetooth.com/ListingDetails/12514, when listing your product as this QDID is qualified against the Bluetooth v5.0 specification, which is not going to be withdrawn for a very long time. 

There should be no issues to get CE and FCC certification with the S112 v6.0.0 running on the nRF52810. 

Best regards

Bjørn

[moon.kim]

Hello.

Thank you for your quick response.

I found TCRL 2019-2 released at the link below.

https://www.bluetooth.com/specifications/qualification-test-requirements/

The TCRL version of QDID you gave me is 2017-1.

Should I use the latest TCRL version for Bluetooth SIG certification? Is it possible to use Bluetooth SIG certification with this version?

[bjorn-spockeli]

When using our End Product QDID you should select the Qualification Process with No Required Testing in Launch Studio as you are fulfilling the requirements below. 

The Qualification Process with No Required Testing path applies to the following scenarios when you are:

• Using another member organization’s previously qualified Bluetooth End-Product or Subsystem in your product with no changes or additions to the Bluetooth design
• Purchasing a Bluetooth product manufactured by a third party and distributing it with your organization’s name or logo (also referred to as “white-labeling“).
• Creating combinations involving only previously qualified Bluetooth End Products or Subsystems and you make no design changes.

This path will not ask you for which TCRL you want to test against, since you do not need to perform any retesting. The S112 v6.0.0 End Product QDID is valid as long as the Bluetooth 5.0 spec is valid, regardless of the TCRL version used in the qualification by Nordic. 

Best regards

Bjørn

[moon.kim]

Hello.

Thank you for your support.

I have one more question

This is a list of support layer for the nRF52810 QDID 102861.

Attribute Protocol
Generic Access Profile
Generic Attribute Profile
Logical Link Control and Adaption Protocol
Low Energy Link Layer
Low Energy RF PHY
Security Manager Protocol

This list does not contain profiles or services.

Does the nRF52810 have a QDID that includes profiles or services like BAS or DIS or GLS?

[bjorn-spockeli]

Yes, we have a Profile Subsystem( QDID: 45222) that includes the following services

Battery Service
Blood Pressure Profile
Blood Pressure Service
Device Information Service
Health Thermometer Profile
Health Thermometer Service
Heart Rate Profile
Heart Rate Service
Immediate Alert Service
Interoperability Test Specification
Link Loss Service
Proximity Profile
Running Speed and Cadence Profile
Running Speed and Cadence Service
TX Power Service

see https://launchstudio.bluetooth.com/ListingDetails/25150 for details.

[moon.kim]

Hello

This QGID is missing GLS.

I need a QDID which includes GLS and DIS, BAS. May you check it again?

And The design name is nRF51 SDK. I need nRF52 SDK because I use nRF52810.

[bjorn-spockeli]

We do have a Profile Subsystem that includes the GLS service, see https://launchstudio.bluetooth.com/ListingDetails/12505,  but this listing does not mention the S112 SD. I have contacted the qualification team regarding adding this SD to the listing. Will update. 

The Profile subsystem with QDID 45222 is valid for the nRF5x series devices utilizing the S110, S112,S113, S120,S130,S132 and S140 SoftDevices from Nordic Semiconductor. Hence you can safely use it with the nRF52810.

-Bjørn

[moon.kim]

Hello

Finally, I want to check it again.

I checked QDID 49943. This QDID has the service I want.

The model number is written  'multiprofile subsystem for nRF5x'.

However, the design name is written 'nRF51 SDK'. Is this QDID valid for nRF52 using S120?