Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.
SimpleLink Bluetooth SIG Certification Update
This article provides customer updates to Bluetooth® SIG Certification status for Texas Instruments SimpleLink™ CC26xx and CC13xx wireless MCUs that support Bluetooth low energy (BLE). This information provided in this article is informative with Bluetooth SIG providing the normative requirements. TI recommends directing questions relating to Bluetooth SIG qualification requirements to a Bluetooth Qualified Expert (BQE).
The following SimpleLink wireless MCUs are covered by this article:
- SimpleLink CC2640R2F Bluetooth low energy wireless MCU
- SimpleLink CC2640 Bluetooth low energy wireless MCU
- SimpleLink CC2650 multi-standard wireless MCU
- SimpleLink CC1350 dual band wireless MCU
The Bluetooth low energy software stack (BLE-Stack) for CC26xx and CC13xx BLE enabled wireless MCUs uses Bluetooth Qualified Components which allow customers to substantially reduce the testing required to meet Bluetooth end product listing (EPL) qualification requirements while providing flexibility to the device configuration. Bluetooth SIG rules specify that Qualified Components have a validity period of three (3) years at which time they may not be available for new End Product Listings (EPLs). This article provides details as to which version of the TI BLE-Stack are available for Bluetooth Qualification (also referred to as Bluetooth Certification) so customers can select the version of software for development.
Bluetooth 4.1 for CC2640 / CC2650 / CC1350
The following SDKs supporting the Bluetooth 4.1 specification are impacted by this expiration of Qualified Design ID (QDID) 61713:
- BLE-Stack 2.0.0 – Released February 2015
- BLE-Stack 2.1.0 – Released July 2015
- BLE-Stack 2.1.1 – Released January 2016
No longer valid for new End Product Listing qualifications as of November 22, 2017 ("component expiration date"). Products that have completed the Bluetooth Qualification process by the component expiration date or products that use a newer TI BLE-Stack v2.2.x SDK supporting Bluetooth 4.2 are not impacted by this change in certification status.
This change only impacts new Bluetooth 4.1 end product certification listings that have not completed the Bluetooth qualification process by the component expiration date. Existing products that have already completed the Bluetooth qualification process by the component expiration date or products that use a TI BLE-Stack SDK v2.2.x supporting Bluetooth 4.2 are not impacted by this change in certification status. You may also continue to provide software updates to your Bluetooth 4.1 products beyond the component expiration date provided you have completed Bluetooth qualification by the component expiration date.
Bluetooth 4.2 for CC2640R2F / CC2640 / CC2650 / CC1350
All BLE-Stack v2.2.x and v3.x SDKs supporting Bluetooth 4.2 with QDID 82185 remain valid for new end product listings and are not subject to the component expiration date listed above. TI recommends that customers migrate their applications to BLE-Stack v2.2.1 or use CC2640R2F if they do not plan to complete Bluetooth qualification process by the Bluetooth 4.1 component expiration date.
The TI BLE5-Stack supporting Bluetooth 5 on CC2640R2F with QDID 94079 remains valid for new end product listings.
I’ve already shipped my product with one of these BLE-Stack SDK versions, do I need to updated my listing with SIG?
No, devices that have completed the Bluetooth Qualification and have been issued a Declaration ID do not need to be updated with SIG or revised regardless of whether the qualified component is still valid. If you intend to make changes to your product beyond the component expiration date, please see the following questions to help determine if you need to update your certification listing with SIG.
Can I issue software updates to my product beyond the component expiration date?
Yes, products that have completed the Bluetooth Qualification process can be updated provided there are no changes that affect Bluetooth Qualification. Please note that changing the product's use of Bluetooth features, e.g., upgrading from Bluetooth 4.1 to 4.2, may require an updated Bluetooth Qualification. Please contact a BQE for specific requirements.
Does this change impact any regulatory certifications (e.g., FCC, CE, IC, etc.)?
No, Bluetooth SIG certification is independent of any regulatory certification requirements.
How do I migrate my application to a Bluetooth 4.2 BLE-Stack SDK?
Please see the migration guide in the SW User's Guide
Do I need to certify or qualify my product with Bluetooth SIG?
This question is addressed in the How to Certify your Bluetooth product article
Why does TI use Bluetooth Qualified Components vs. Subsystems for CC26xx and CC13xx BLE products?
Qualified Components allow the end product to choose from different product configuration, such as selectively enabling or disable Bluetooth features, as well as using different antenna layouts to meed board design requirements. A Qualified Subsystem does not allow for such flexibility and requires the end product to use the subsystem exactly how it was qualified.
Will TI continue to make these BLE-Stack SDK versions available after the component expiration date?
Yes, TI will continue to make these SDKs available on ti.com.
I have a question not a listed here.
Please post your question to the Bluetooth low energy E2E Forum.