• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 298 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2640R2L: Missing Disconnection event from BLE to Host

Bhavin Parmar
Expert 1550 points
Part Number: CC2640R2L

Dear Team,

We are using CC2640R2L as SPI interface with Host micro. Where as this BLE module is in Slave mode while Host micro is in Master mode.

SDK version  : simplelink_cc2640r2_sdk_2_30_00_28

Example used : Host Test

Normal Scenario : Normally BLE-A module remains 99% in connected mode with other BLE-B module device ( Central Device ).Whenever this BLE connection breaks from opposite device due to any reason BLE-A module receives disconnection event thus host gets informed that BLE-A is disconnected within 25 second.

Issue :  While doing frequent power switching from Opposite device BLE-B, Always BLE-A must get disconnection event but sometimes this event not received by Host micro. We observed that Average 5 to 7 times missing out of 1000. We want to know what could be the cause of this issue.   

We gone through Errata sheet swrz085a and in this doc it is mentioned that 

Advisory 02 Motorola® SPI Format Slave Mode Writes to Transmit FIFO Can Lose Data

Is our issue is related to this Advisory only ?

We wanted to open workaround document but not able to open it. Can you please share this workaround doc.

Regards,

Bhavin P

 

  • 0
    TI__Mastermind 37805 points

    Hi Bhavin,

    The text of the errarata is located in the document, copied below for convenience.

    I think it's unlikely this is the issue you're seeing, but you can check by monitoring the SPI lines with a logic analyzer. Then you can see if the connection disconnected event is being sent at all. Once we figure out whether the BLE-A device is sending the host-microcontroller the disconnected event, then we will know what device the problematic behavior is occurring on (Host-micro or BLE-A)

    Best,

    Nate