• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 421 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.

CC2564: Unexpected disconnection

Mirco
Intellectual 470 points
Part Number: CC2564

Hello

During my test with CC2564 (Bluetopia 1.2 stack) on Tiva MCU, after some time I get an "HCI_Disconnect - wrong reason" (packet 313031 in the attached log). This situation appears several times, after 1 or 2 hours of connection... Can you find anything unusual? Or is it simply a radio problem?

Thank you

disconnection.rar

  • 0
    TI__Mastermind 35795 points
    Hi Micro,
    Can you also please explain the test scenario in more detail ? What happens after HCI disconnect msg ?

    Thanks
    Saurabh
  • 0 in reply to S
    Intellectual 470 points
    In my scenario I have a Bluetooth device which streams data to the CC2564 on SPP with a rate of 100kbps. After the HCI disconnection the two devices returns in standby, waiting for a new connection. Analysing the log, I can see "hcic_process_hci_commands: HCI_DISCONNECT (Group 1 Opcode 0x6)" before the disconnection... So it's the host to ask for disconnection?
  • 0 in reply to Mirco
    TI__Mastermind 29311 points

    Mirco said:
    So it's the host to ask for disconnection?

    That is correct. The host sends HCI_Disconnect command to the controller. 

    Mirco said:
    During my test with CC2564 (Bluetopia 1.2 stack) on Tiva MCU, after some time I get an "HCI_Disconnect - wrong reason" (packet 313031 in the attached log)

    This is just a warning trace from the CC256x firmware. There are 6 valid reason codes for the HCI_Disconnect command (0x05, 0x13, 0x14, 0x15, 0x1A and 0x29). If the reason code used by the host is not a valid one, the CC256x firmware will print this warning trace and process the HCI_Disconnect request regardless.

    Since the attached logs do not include the HCI/LMP traces, it is not possible to know from the logs exactly which reason code is used by the host. However, the "HCI_Disconnect - wrong reason" is more of an after effect of the issue that triggers the disconnection. You may want to debug further on the host stack/application side to better understand the root-cause of this disconnect.

    Best regards,

    Vihang