We have a peripheral IoT product that incorporates the BGM11S (specifically BGM11S22F256GA) with Bluetooth SDK 184.108.40.206 (v2.5.5), and we are looking into Bluetooth SIG registration.
As described in the below document, we believe that we should register with Host stack 126252 and Link Layer 124272 or 127618 along with BGM11S module QDID 145424 based on the BGM11S Data Sheet. Is that correct?
The above software-based pre-qualified components are two out of the three components to integrate when proceeding with the "Qualification Process with Required Testing". Despite the “Required Testing", customers do not need to do any additional testing, given that the test reports are embedded in the pre-qualified components for the SIG to review.
If so, which Link Layer QDID should we use for Bluetooth SIG registration, 124272 or 127618 ?
For our future reference, can you tell me which Silicon Labs' document we should look through to identify the QDIDs used for Bluetooth SIG registration?
You are right that you should use our pre-qualified components Host stack 126252, Link Layer 127618 and RF-PHY BGM11S 145424.
You can search the SIG database for "Silicon Laboratories" listings here:
Thanks for your answer.
We understand we should use your pre-qualified BGM11S 145424, Host stack 126252, Link Layer 127618 under our condition with BGM11S and Bluetooth SDK 220.127.116.11 (v2.5.5).
However, we'd like to have a complete understanding by clarifying when to use Link Layer (Bluetooth 5.0 – including coded PHYs) 124272 instead of Link Layer (Bluetooth 5.1) 127618.
In which case should we use Link Layer (Bluetooth 5.0 – including coded PHYs) 124272 specifically?
Could you show us an example if we should use Link Layer Bluetooth 5.0 – including coded PHYs) 124272 instead of Link Layer (Bluetooth 5.1) 127618?
And what does "including coded PHYs" mean?
We recommend our customers selecting the latest QDID for the version of Bluetooth SDK used on their products. "Link Layer (Bluetooth 5.0 – including coded PHYs)" is an update to our old listing "Link Layer (Bluetooth 5.0)" where the Bluetooth SDK doesn't support Coded PHY. The customers who have used "Host stack (Bluetooth 5.0)" may select "Link Layer (Bluetooth 5.0 – including coded PHYs)" as the Bluetooth specification versions match.
In your case, you should select the components for Bluetooth 5.1. I guess you could use "Host stack (Bluetooth 5.0) 101550" and "Link Layer (Bluetooth 5.0 – including coded PHYs) 124272" if you were using Bluetooth SDK 2.10.x.
Coded PHY is a new physical layer data throughput configuration introduced in Bluetooth 5.0. You may read this document for further information: https://docs.silabs.com/bluetooth/latest/general/connections/using-2m-and-le-coded-phy-bt5
Thanks for the explanation. Understood.
And one more question.
Given that we launch our product with Bluetooth SDK 18.104.22.168, can we skip Bluetooth SIG re-registration with Link Layer (Bluetooth 5.2) 147971 and Host stack (Bluetooth 5.2) 146950 if we migrate to SDK v2.13.x and above after our product launch by distributing OTA update with newer Bluetooth SDK?
Our SDKs for Bluetooth 5.2 are backward compatible so yes you can skip Bluetooth SIG re-registration and retain your product Bluetooth 5.1 qualified in this situation.
Thank you very much for your answers.