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.

CC2651R3SIPA: Sending more than 16Bytes UUID with simple_peripheral example

Part Number: CC2651R3SIPA
Other Parts Discussed in Thread: SYSCONFIG

Hi,

My customer is trying to send more than 16bytes UUID using two LP-CC2651R3SIPA boards.
host_test sample is running on one board. Modified simple_peripheral is running on another board.

He can send up to 16bytes of notification with below changes, but cannot over 16bytes.
Here are update source files and which lines are changed.

3482.simple_gatt_profile.c
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
/******************************************************************************
@file simple_gatt_profile.c
@brief This file contains the Simple GATT profile sample GATT service profile
for use with the BLE sample application.
Group: WCS, BTS
Target Device: cc13xx_cc26xx
******************************************************************************
Copyright (c) 2010-2023, Texas Instruments Incorporated
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

2844.simple_peripheral.c

File name Line#
simple_gatt_profile.c 79
simple_gatt_profile.c 181
simple_gatt_profile.c 302
simple_gatt_profile.c 502
simple_gatt_profile.c 505
simple_gatt_profile.c 569
simple_gatt_profile.c 632-634
   
simple_peripheral.c 1402-1441

Here is log output at Host side.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
--------------------------------------------------------------------
[391] : <Rx> - 01:27:01.651
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x18 (24) bytes(s)
Event : 0x051B (1307) (ATT_HandleValueNotification)
Status : 0x00 (0) (SUCCESS)
ConnHandle : 0x0000 (0)
PduLen : 0x12 (18)
Handle : 0x002E (46)
Value : 87:32:F2:2C:F0:F8:35:0C:35:0C:35:0C:32:0C:35:0C
Dump(Rx):
0000:04 FF 18 1B 05 00 00 00 12 2E 00 87 32 F2 2C F0 ............2.,.
0010:F8 35 0C 35 0C 35 0C 32 0C 35 0C .5.5.5.2.5.
--------------------------------------------------------------------
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


Could you point me where should be corrected to send over 16bytes?

Thanks and regards,
Koichiro Tashiro

  • Hi Kochiro,

    Thanks for reaching out and sharing the specific changes made! We will look into this to recreate the issue if possible and get back to you soon. In the meantime, could you share what version of the SDK is being used by the customer?

    Best regards,

    Luke

  • Hi Luke,

    SDK version is 7.10.02.23.

    Thanks and regards,
    Koichiro Tashiro

  • Koichiro,

    Thanks for sharing the SDK version. The customer should be able to send a longer UUID by going into the Sysconfig settings, under BLE, selecting Broadcaster Configuration and opening up the Advertisement Set 1 and then Advertisement Parameters 1 and changing it within there.

    If more questions arise or clarification is needed, please let me know.

    Best regards,

    Luke

  • Hi Luke,

    The customer is asking exactly which parameter should be changed in below window.
    Could you tell me?


    Thanks and regards,
    Koichiro Tashiro

  • Koichiro,

    Apologies, I meant to say advertisement data 1, not advertisement parameters 1. Opening up advertisement data 1 gives you the following options would should be helpful to the customer:

    Best regards,

    Luke

  • Hi Luke,

    The customer still wants to know exactly which parameter should be checked in "advertisement data 1".
    Which checkbox(es) should be checked?

    Thanks and regards,
    Koichiro Tashiro

  • Koichrio,

    The customer should select the More128-bit UUIDs Available option and then update the Num of UUIDs field as necessary.

    Best regards,

    Luke