CC2652R7: Clarification on UUID using in current code

mohan prasanna R

Part Number: CC2652R7

SDK Used : simplelink_cc13xx_cc26xx_sdk_7_10_01_24

Code Used : simple_peripheral_LP_CC2652R7_tirtos7_ticlang

Chipset Using : CC2652R7

In the simple peripheral code 0xFFF1, 0xFFF2, 0xFFF3, 0xFFF4 and 0xFFF5 UUID's are used for Read, write and notify purpose. Shall i continue with the same UUID for Huge Mass production or Any UUID to be purchase ? or Any Unique 128-bit UUID to be used ?

0000FFF1-0000-1000-8000-00805F9B34FB - In general this UUID is mentioned as "Bluetooth SIG-defined GATT profiles". Will be face any problem on this ?

over 1 year ago

0 Clément over 1 year ago

TI__Guru** 101450 points

Hi,

Thank you for reaching out.

For most of the use cases, 128-bit UUID are sufficient and nothing justify the extra costs of acquiring a 16-bit UUID.

Assuming you go for a 128-bit UUID, I would recommend you generate your own UUID base. Many generators are available out there (my personal preference goes to https://www.uuidgenerator.net/).

I hope this will help,

Best regards,

0 mohan prasanna R over 1 year ago in reply to Clément

Intellectual 710 points

Hi,

In case of using our own generated UUID base, what is the procedure to implement it on simple_peripheral code ? Is there any example code with 128-bit UUID implementation ?

SDK using : simplelink_cc13xx_cc26xx_sdk_7_10_01_24

0 Clément over 1 year ago in reply to mohan prasanna R

TI__Guru** 101450 points

Hi,

In the SDK, the project_zero uses mainly 128-bit UUIDs. You can find the implementation of the profiles in <SDK>\source\ti\ble5stack\profiles\project_zero.

You can also look at the following implementation on GitHub: https://github.com/TexasInstruments/ble_examples/blob/simplelink_cc13xx_26xx_sdk-6.40/source/ti/ble5stack/profiles/simple_serial_stream/simple_stream_profile_server.c

I hope this will help,

Regards,

Bluetooth®︎

Bluetooth forum

CC2652R7: Clarification on UUID using in current code