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

Unexpected Disconnection due to HCI TIME OUT

qinghui tang
Intellectual 590 points
Other Parts Discussed in Thread: CC2564

Our BLE device experienced lot of disconnection due to supervision time out
UART terminal log looks like:
etLE_Disconnection_Complete with size 9.
   Status: 0x00.
   Reason: 0x08.
   BD_ADDR: 0x5901C63D627C.
   
After BLE device built a connection with iOS device or android device, after maybe 5~20 minutes,
the connection would drop due to reason 0x08 (HCI_ERROR_CODE_CONNECTION_TIMEOUT)
We used TI Wireless Log tool captured HCI event from TX_DBG pin of CC2564,
The log shows that just before the time out of connection, 
there are many HCILL_GOTO_SLEEP_IND messages.
(not sure is it from controller to host or host to controller)
It is very strange since in our code we never called any command to enter sleep mode
Not sure whether this is a coincidence or actually cause of disconnectioon.
In a 20 minute log file, HCILL_GOTO_SLEEP_IND was not found in previous 19 minute log,
only found before time out disconnection happens
  • 0
    Intellectual 590 points

    Also, after the time out happens,

    BLE device is actually not be able to broadcast any advertisement packets.

    (observed by BLE sniffer), neither can it receives any advertisement or connection request.

    Bluetopia is not returning any error codes for any GAP_LE_Advertising_Enable() or GAP_LE_Set_Advertising_Data() or GAP_LE_Advertising_Disable(). 

    As suggested by Stonestreeone suppport, it could be a hardware issue of CC2564

     

     

  • 0 in reply to qinghui tang
    TI__Mastermind 23565 points

    Hi,

    What service pack version are you using?

    Miguel

  • 0 in reply to Miguel
    Intellectual 590 points

    Try different Bluetopia version and TI patch combination,

    all have supervision time out issue, but some more severe (more frequently)

    BLE Stack 1.4                             OK, some time out
    BLE Stack 1.4     + 2.14 patch    More time out
    BLE Stack 1.5R1 + 2.12 patch    More time out
    BLE Stack 1.5R1 + 2.14 patch    More time out 

     

    I have capture TX_DBG output for several times, it all seems

    have something to do with HCILL_GOTO_SLEEP_IND_MSG

    Also I saw and old post about supervision time out, also not solved

     

    http://e2e.ti.com/support/wireless_connectivity/f/660/t/292276aspx

     

  • 0 in reply to qinghui tang
    TI__Mastermind 32615 points

    Hi,

    Could you provide us the logger logs you have captured.

  • 0 in reply to Sundeep Javvaji
    Intellectual 590 points

    Hello Sundeep,

    I just send the log files to your email

    With the title "Unexpected Disconnection due to HCI TIME OUT"

     

     

  • 0 in reply to qinghui tang
    TI__Mastermind 32615 points

    Hi,

    From the logs you have provided the disconnection is due to connection timeout(0x08).

    Once the connection is established, if there is no indications or notifications (that is no data to transfer) it will wait for the idle connection timeout and disconnect. Please see the Bluetooth specification for more details.

  • 0 in reply to Sundeep Javvaji
    Intellectual 590 points

    Hi Sundeep,

    Thanks for the answer about as supervision time out.

    1) But why did it happened?

    Time out sometimes it happened

    a few minutes after connection, sometimes after 20~30 minutes.

    In our test, there is data transfer every 10 second.

    When test with iOS App, iOS also reported the disconnect reason as unexpected time out.

    We have tried different iOS / Android devices, all have the same issue time out issue.

    2) It is hardly can be observed with Bluetopia v1.4 and older one.

    3) In addition, how about those goto sleep HCI event,

    I have capture several DX_TBD logs, and those goto sleep event always happens,

    only happens before supervision time out.

    Thanks.

  • 0 in reply to qinghui tang
    TI__Mastermind 32615 points

    Hi,

    1)As mentioned earlier once the connection is established, if there is no indications or notifications (that is no data to transfer) it will wait for the idle connection timeout and disconnect. Please see the Bluetooth specification for more details.

    2) If there is no interaction in the idle connection timeout then there will be a disconnect.

    You can try increasing the "connection timeout", "connSlaveLatency and "connInterval" values in connection request and check.

    3) If the sleep mode is enabled, then if we have no activity on the module for 100ms we inform the host that we are going in to sleep and once we get the acknowledgment from the host.  we go to sleep.

    I don't see any problem with the sleep mode, as and when you have some activity on the module it is coming out of sleep (AWAKE state).