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.

LAUNCHXL-CC26X2R1: data transfer stop automatically in Throughput Peripheral example

Part Number: LAUNCHXL-CC26X2R1

Hi, 

when I change the "fill the notification with data" part in this example, after successful connection with phone or PC and set throughputOn to 1, data transfer

stop automatically.(throughputOn = 0) this happen after about 3 seconds for PC and about 16 seconds for android phone.

I didn't changed anything but "fill the notification with data" part.

here is my code

            if(cnt2)
                        {
                            for(i=0;i<=118;i++)
                                                           {
                                                           noti.pValue[i*2] = i >> 8 ;
                                                           noti.pValue[i*2+1] =i ;
                                                           }

                        }
                        else
                        {
                           for(i=0;i<=118;i++)
                                                           {
                                                           noti.pValue[i*2] = (i+122) >> 8 ;
                                                           noti.pValue[i*2+1] =i+122 ;
                                                           }

                        }

cnt2 is a boolean variable that toggle 

            if (status != SUCCESS)
            {
                // If noti not sent, free the message. (If it is sent, the BLE-Stack will free the message.)
                GATT_bm_free((gattMsg_t*) &noti, ATT_HANDLE_VALUE_NOTI);
            }
            else
            {
                cnt2 = !cnt2;
            }

SDK version for Throughput Peripheral example : SimpleLink CC13x2 26x2 SDK (5.10.00.48)

code composer studio version : 11.1.0.00011

Regards,

  • Hi,

    Looking at the code modification you have shared, I do not manage to identify the reasons why you have an issue.

    It would be helpful if you could do the following:

    • Identify the maximum size you manage to use before getting this issue
    • Collect Bluetooth traces (using a protocol analyzer) both for the expected and the non-expected behavior

    Best regards,