• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 270 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2340R5: When using the CC2340R5 as the central device, more transparent data from peripheral devices cannot be received.

Joey Li
Prodigy 120 points
Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Hello, TI Team.

I am using CC2340R5 as the central device for transparent transmission with peripheral devices that are also CC2340R5. The peripheral sends about 30 bytes of data to the central device every 500ms, at which point the MTU is a maximum of 251 bytes.

When the central device receives about 1800 bytes of data, the central device appears to no longer receive the data transmitted by the peripheral device, and the peripheral device continues to transmit data. I tried several times with the same result.

The code below is where the data is finally received, printed to the PC via the serial port.

My colleague had the same problem.

Best Regards,

Joey.

  • +1
    TI__Expert 3290 points

    Hi Joey,

    Thanks for reaching out! From what you have shared, it sounds like your setup is correct but the buffer may not be clearing properly. Could you share what base project and SDK you are using as well as any changes/additions you have made to it (including SysConfig)?

    I am also curious as to what you are sending from the peripheral device as well as how you are clearing the central device (if at all).

    Best regards,

    Luke

  • 0 in reply to Luke
    Prodigy 120 points

    Hi Luke,

    You are correct. The reason for this is that the buffer was not cleared. When I add GATT_bm_free(&(gattMsg->msg), gattMsg->method) to the end of the GATT_EventHandler function to free the buffer, the situation described above does not currently occur.

    By the way, I discovered a problem some time ago. In the ATT_MTU_UPDATED_EVENT, The actual updated value of the MTU is not ((attMtuUpdatedEvt_t *)pMsgData)-> what the MTU points to. This value is always fixed at 176. The correct value should be what gattMsg->msg.mtuEvt.MTU points to.

    The version of SDK I am using is simplelink_lowpower_f3_sdk_7_20_01_10.

    Best Regards, 

    Joey

  • 0 in reply to Joey Li
    TI__Expert 3290 points

     Joey,

    Glad that was able to resolve your issue and thanks for sharing this other problem you've found as well! I will report this to our internal team so they can fix this as soon as possible.

    Best regards,

    Luke