• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 1465 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Regarding the Bluetooth Qualification and declaration

Parth Dholakiya
Expert 1245 points
Other Parts Discussed in Thread: CC2541

Hi,

We have design and developed a ble enabled product in which we have used CC2541 and BLE 1.4.1 stack. We have designed our custom board for this product.While designing the board we have referred the Cc2541 reference design given by ti. We have modified the application layer of the ble stack as per our requirements.

Now our product is ready for production.

So i want to know do we need to list and qualify our product?

Waiting for your reply.

Thanks in advance!

  • 0
    TI__Guru* 81801 points
    Hi Vidula,

    We have a wiki article on "How to Certify your Bluetooth product": processors.wiki.ti.com/.../How_to_Certify_your_Bluetooth_product

    Cheers,
    Marie H.
  • 0 in reply to Marie H
    Expert 1245 points

    Thanks for your reply,But my question is do i need to qualify my product?

  • 0 in reply to Parth Dholakiya
    Expert 1245 points
    Hi,
    In my application i have created a custom profile so can i use the Profile QDID 46840 in certification process? if not then what i need to do?
    I think i can use 23454 (controller qdid), 26384 (host qdid),but not sure about profile qdid.
    Sorry i am not familiar with this process so kindly help me on this.
    Waiting for your reply its really very urgent!!!!
    Thanks!
  • 0 in reply to Parth Dholakiya
    TI__Guru** 105180 points

    Hi,

    Please refer to the FAQ in the aforementioned certification wiki:

    I have created my own proprietary profiles, do I need to qualify them?

    Although many customers have successfully used the guidance & information on the wiki to list their product, if you are not comfortable with the BT certification process, please consider using a Bluetooth Qualification Expert (BQE). A BQE will, for a nominal fee, guide you through this process.

    Best wishes

  • 0 in reply to JXS
    Expert 1245 points

    Hi ,

     We have designed a ble based product for consumer.The product consist of cc2541 ble chip with ble 1.4.1 stack running on it. We have developed our application using Keyfob demo project. The product consist of load cell and thermister interfaced to cc2541 adc.

    The cc2541 read data from both the sensor and send it over bluetooth.

    In order to send data over ble we have used following profiles.

    Product Name

    Service Name

    Service UUID

    Characteristic Name

    Characteristic UUID

    (Holds Data)

    Characteristic

    Properties

    Data Length

    Product Information

    (ID # only)

    Device Info service

    0X180A

    Model Number

    String

    0X2A24

    Read

    11 Bytes

    Firmware Revision String

    0X2A26

    Read

    13 Bytes

    Hardware Revision

    String

    0x2A27

    Read

    13

    Bytes

    Battery level

    Battery Service

    0X180F

    Battery Level

    0X2A19

    Read/Notify

    1 Byte

    Battery Alert

    0x2A1A

    Read/Notify

    1 Byte
    Temperature value

    iThermo

    0xFF00

    TEMPERATURE

    0xFF01

    Notify

    3 Bytes
    Weight value

    Proximity Reporter

    0X1804

    Single Load

    0X2A07

    Notify

    3 Bytes
    4 Temperature value

    Accelerometer

    0XFFA0

    Multi Thermo

    0XFFA3

    Notify

    16 Bytes

    Temperature value and weight value

    Health Thermometer

    0x1809

    Thermo & Load

    0x2A1C

    Notify

    8 Bytes
    2 weight values

    Simple Profile

    0XFFF0

    Multi Load

    0XFFF1

    Notify

    8 Bytes

    along with this some other custom services. Now i want to know will this create issue while software certification?Can i do the software certification with all this profiles.

    My product is in pre production phase and my client does not want any change in software.

    Please help.

  • 0 in reply to Parth Dholakiya
    TI__Guru** 105180 points
    Hello Vidula,

    As I mentioned back in October, the wiki article describes the qualification process for adopted (SIG defined) profiles and custom profiles. If you are using a TI supplied adopted profile, then you do not need to test/qualify these for CC254x devices. If you are using a SIG adopted profile not provided by TI, then you need to perform PTS testing for that profile. Custom profiles/services (e.g., SimpleProfile) are not subject to qualification testing provided you use a 128-bit UUID (or purchase a 16-bit UUID).

    Note that if you are using SIG adopted profiles/services, you cannot modify the implementation of the service/profile such that you break PTS compliance. If you do need to modify an adopted service/profile, this is OK, however, you must use a 128-bit UUID and thus the profile/service becomes "custom".

    Best wishes
  • 0 in reply to JXS
    Expert 1245 points
    Hi,
    Now somewhat clear to me .I referred "processors.wiki.ti.com/.../How_to_Certify_your_Bluetooth_product", So i understand that if i am creating any custom service then i have to use 128bit UUID. I think same is done in sensor tag project,in that all the services are customize.

    1) Now i wanted to know for 128 bit uuid i will need a base uuid ,so i should use any base uuid or i need to use same base uuid given in ti ble stack ?
    128 bit base uuid in sensor tag project:
    "0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xB0, 0x00, 0x40, 0x51, 0x04, LO_UINT16( uuid ), HI_UINT16( uuid ), 0x00, 0xF0 "
    2) As per my understanding i just need to modify service uuid and characteristic value uuid to 128 bit. Others i.e. client characteristic configuration (0x2902) ,characteristic description(0x2901), characteristic declaration ( 0x2803 ) will remain as it is. right?
  • 0 in reply to Parth Dholakiya
    TI__Guru 56590 points
    Hello Vidula,
    1)
    You should use a random base UUID. Consider the case where multiple customers use the same base-UUID as used by the Sensortag project. Then there is a good chance of several different projects with different profile/services implementations end up using the same UUID for entirely different functions. That can cause problems for GATT client implementations which might assume a certain UUID is related to a specific given function.

    Please take a look at the Bluetooth Low Energy trainings in simplelink_academy for some more details:
    software-dl.ti.com/.../overview.html

    Also here is a section on UUID in a obsolete guide which you might find useful:
    processors.wiki.ti.com/.../Tutorial:_How_to_Create_a_Custom_Bluetooth_Smart_Embedded_Application_with_the_CC2650DK

    2)
    For example, 0x2803 is defined as Characteristic Declaration in the specification by bluetooth SIG. They must remain as is or else your GATT server attribute list will not make any sense.
  • 0 in reply to Eirik V
    Expert 1245 points
    Thanks for your quick reply.

    2) Yes, the syntax as it is. no change.