This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Bluetooth Module Certification

Other Parts Discussed in Thread: CC2541

Hello,


I am developing on the TI CC2541 Chip and I hope to launch my product to market in the near future. This is my first time launching an actual product, and I came upon this comment online that had me concerned:

"Bear in mind you’ll also need to get your bluetooth module certified by FCC, IC, ETSI, etc, which will end up being quite expensive (around $40k)"


Is this correct? Do I need to certify the Bluetooth module or is this already taken care of by TI?

Thank you!

  • Hello Ted, 

    If you are using TI reference design for CC2541 and the profiles are not changed, you may be able to avoid the process of certification. If not, based on where you plan to sell your product, FCC/ETSI/IC certification will be required. Please refer to the following document for more information regarding this. 

    http://processors.wiki.ti.com/index.php/How_to_Certify_your_Bluetooth_product

    - SS

  • Thank you for the quick response. I read over the document you provided, it was very useful. I just have another quick question if you do not mind, and I will accept your response for others with a similar question.

    When you say "profiles not changed", can you give me an exact example for what you mean? For example, I am working with KeyFobBLEDemo provided by TI. I hope to make changes to the device name, characteristic/services UUID and values accept by the characteristic. Would this count as "not changing the profile"?

    Thanks again!

  • Hi Ted,

    There are two types of certifications in your case:

    • FCC/ETSI (and ARIB etc.) are regulations on products using a radio in general. It's mandatory for you to certify based on which worldwide regions you are going to sell your product. The only way for you to "bypass" this requirement is to by a pre-certified module (which is slightly more expensive) from some of our module vendors (Murata (Jp), BlueGiga (Fi), ConnectBlue (Sw) etc.)  
    • BT Qualification is required if you are planning to release a Bluetooth product (as you are).The software stack has been qualified and the same goes for the Bluetooth SIG profiles we have included in our solution. You are referring to a custom "use-defined" profile which is not a subject for qualification, so don't worry. The only thing you need to do here is to become a Bluetooth SIG, member, create and End Product Listing (EPL) and pay a listing fee.

    I hope this clarifies a bit. Unfortunately, nothing comes for free.

    Best Regards

    Joakim

  • Perfect explanation. Thank you very much!