CC2564: How to differentiate disconnection reason?

Hi Saurabh,

My device does not include UART output so I cannot access firmware logs anymore.
I can only share the BT logs from the TX_DBG pin. Is this relevant?

Regards,

Alain.

Hi Alain,

Yes, please share the BT firmware logs from the TX_DBG pin.

BT Logger User's Guide : 

BR,

Vihang

Hi Vihang,

I divided the logs into 3 files, each one representing a different scenario:

1. The first one shows a connection to the remote device (an android phone) which was previously paired with my device. There is no issue at this time.
2. The second file shows, after an established connection, a disconnection from the user. For that, I go into the Android Bluetooth Menu and click on my device name.
3. The last one shows, after an established connection, a disconnection from distance. For that I take my phone and go far away for my device until the Bluetooth Menu indicates no connection between them.

I would like to differentiate the scenario 2 and 3 on the device side; so in case 3 I launch a re-connection procedure and in case 2 I do nothing.

Thank you for your help,

Alain

Attached files:

logs.zip

Hi Vihang,

A little update on this matter:
From another of my post on this forum, Saurabh said that my logs were incomplete. So I logged, with right parameters this time, a disconnection from user on the remote side (see attached files) and studied the logs.

As I can see, there is a HCI_Disconnect command send from the host to the device with Reason 0x13 (Remote User Terminated Connection). It is this information that I would like to get on my microcontroller. Because my code do not send intentionally the HCI_Disconnect command, I suspect that is the library SS1BTHFR that is doing it.

I registered and added the HCI_Event_Callback in the idea of retrieving a etDisconnection_Complete_Event. Unfortunately, it never come.
Below a snippet of the HCI_Event_Callback:

static void BTPSAPI HCI_Event_Callback(unsigned int BluetoothStackID, HCI_Event_Data_t *HCI_Event_Data, unsigned long CallbackParameter)
{
  HCI_Disconnection_Complete_Event_Data_t *HCI_Disconnection_Complete_Event_Data;

  /* First, check to see if the required parameters appear to be       */
  /* semi-valid.                                                       */
  if((BluetoothStackID) && (HCI_Event_Data))
  {
    /* The parameters appear to be semi-valid, now check to see what  */
    /* type the incoming event is.                                    */
    switch(HCI_Event_Data->Event_Data_Type)
    {
      case etDisconnection_Complete_Event:

      HCI_Disconnection_Complete_Event_Data = HCI_Event_Data->Event_Data.HCI_Disconnection_Complete_Event_Data; 
      if(HCI_Disconnection_Complete_Event_Data->Reason == HCI_ERROR_CODE_OTHER_END_TERMINATED_CONNECTION_USER_ENDED)
      {
        while(1);
      }
      break;
    }
  }
}

So my question is still the same, is there a way to get the information remote user terminated connection on host side.

Best regards,

Alain.

Attached files:

2335.logs.zip

Hi Vihang,

I checked the unusual behavior you pointed out to me.
In fact I was monitoring the disconnection too early in the process (something like HFP close port indication) which triggered a shutdown of the BT module in my code.
Now I wait for the HCI disconnection event before closing anything and it works as expected !

Thank you very much for your help.

Best regards,

Alain.