• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1168 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.

Random Disconnect issue with CC2650

Sid Saxena
Expert 1530 points

Other Parts Discussed in Thread: CC2650

I am facing an issue with the CC2650 in Central mode. Once the connection is established, sometimes the device disconnects from the peripheral.  I could see the disconnect event on the peripheral but CC2650 doesn't enters the GAP_LINK_TERMINATED_EVENT . 2650 still assumes its in connected state. Is there a way to determine the connection status or a way to determine if I am still connected to the peripheral (considering 2650 never enters the disconnect) 

  • 0
    TI__Guru** 105180 points

    Hello Sid,

    Is this related to your other post: BLE Read on Central device.? Can you post the BLE air sniffer log?

    Best wishes

  • 0 in reply to JXS
    Expert 1530 points
    that post is totally a different issue. Can Air Sniffer be used on 2650 as well. the wiki shows its support for 2540 only.
  • 0 in reply to Sid Saxena
    TI__Mastermind 33460 points
    Hi Sid,

    The OTA sniffer firmware is only supported on 254x devices. However, for it's value it's a very good deal and an excellent tool for debugging BLE projects.

    If you cannot obtain a sniffer, I would suggest trace through the GAP peripheral state machine and toggle GPIO(s) at key places to indicate where you are in the code. Then provide a logic trace to explain what the code is doing. This will help you to determine what is happening in code without interrupting it with the debugger.
  • 0 in reply to Sean2
    Expert 1530 points
    Hi Sean,

    Thank you for the suggestion I tried adding debug statement in each function to see what the code is doing. but it seems to follow it actual execution flow without even knowing that it has been disconnected from the peripheral.

    On the peripheral side I see the disconnection event occurring but on 2650 central it follows its actual code flow, without knowing it disconnected.
  • 0 in reply to Sid Saxena
    TI__Mastermind 33460 points
    Hi Sid,

    There could be a number of issues causing this. Can you explain what you mean by a debug statement? Also, what project is your code based on and what changes have you made (i.e. SimpleBLECentral).