• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 609 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.

With CC2564B, Frequent switch between CVSD and MSBC mode cause HCI transport error

user4527828
Intellectual 390 points

Hello,

We use CC2564B in our product phone with BT stack2.1 of alpwise, we use handset with MSBC mode and headset with CVSD mode to set up phone call.

When we make frequent switch between these 2 devices during a call, there will be HCI transport error or HCI fatal error with cause the BlueTooth not workable.

The log is collected, would you help check what cause this problem?

Thank you.Switch_cause_HCIerror.zip

Regards

Gao Hong

  • 0
    TI__Guru* 85400 points
    Hi Gao,

    Usually transport error occurs when the host does not receive a response to a command that it has sent to the device. But from the Logger logs, it looks to me that the device has responded to all the commands that it has received.

    The last command the device has received before the reset is HCI_Disconnect for which it sent a "Command Status Event" followed by a HCI_Disconnection_Complete_Event. Probably the host uart did not forward to the stack.

    Can you tell me from the host perspective, which command it did not receive a response to?
    Also, the device reset happens ~ 2seconds after the host has sent HCI_Disconnect. Can you tell me why does the host reset the device?

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Intellectual 390 points

    Hello,

    The problem happens when it tries to set up WBS voice link. HCC_DISCONNECT should be the command send but after that it will try to set up WBS connection again.

    But it gets hci transport error and stack call HCI deinit and send HCI fatal error so the host reset the device.

    So it maybe  HCI_Disconnect that failed to forward to the stack.

    Regards

    Gao Hong