CC2541: 128 Bit UUID SimpleBLE

javer Valino

Part Number: CC2541

Hi,

I followed the instruction in the link below so I can have a 128bit UUID for my CC2541. However seems that something is wrong in the example.

Please obseved that after the first cortrect 128bit uuid "0xF000FFF104514000B000000000000000", the following 128bit uuid is in different series "0x2A252A242A232A041801280028012803".

Also why Im getting "0A:25:00:00:00:00:00:00:00:00:B0:00:40:51:04:F1:FF:00:F0" as value of "0x2803" UUID?

over 8 years ago

0 Eirik V over 8 years ago

TI__Guru 56590 points

Hello Javer,
Did you use the 1.2 version of the stack when testing this?
Did you simply merge the contents of 128bitUUID.zip into your application?

0x2803 is the UUID of the “Characteristic Declaration” attribute as defined by the blueooth SIG:
www.bluetooth.com/.../declarations

0 javer Valino over 8 years ago in reply to Eirik V

Intellectual 280 points

Hello Eirik,

Thanks for the reply.

I use BLE-CC254x-1.4.0 in my testing. Is this the correct project should I use?
Yes, I simply merge it with "SimpleBLEPeripheral" sample inside BLE-CC254x-1.4.0.

Yup, I understand that 0x2803 is the UUID of the “Characteristic Declaration” attribute as defined by the blueooth SIG.
However, I'm wondering why I'm getting "0A:25:00:00:00:00:00:00:00:00:B0:00:40:51:04:F1:FF:00:F0" which seems to be a 128 + 16 bit UUID.

Sorry for this newbie questions, I'm very new GATT protocol.

BR,
Javer

0 javer Valino over 8 years ago in reply to javer Valino

Intellectual 280 points

Hello,

Can someone help me on the above issue?

Thanks,
Javer

0 Eirik V over 8 years ago in reply to javer Valino

TI__Guru 56590 points

Hello Javer,
This patch was intended for an old release (1.2). There could be other conflicts when you do a simple merge. I suggest you diff every file in the patch (for example WinMerge or other compare plugin to a text editor ) and change the source files manually.

Bluetooth®︎

Bluetooth forum

CC2541: 128 Bit UUID SimpleBLE