• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 329 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC2564MODAEM: Audio gateway(HFPAG) with a commercial headset problem

CC2564MODAEM: CC2564MODEAEM (HFPAG example): problem with the connection establishment to a headset

Michael Pietsch
Prodigy 130 points
Part Number: CC2564MODAEM
Other Parts Discussed in Thread: CC2564

Hello TI team,

I have a similar problem as described in https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/844824?tisearch=e2e-sitesearch&keymatch=CC2564CSTBTBLESW

I also use a CC2564MODEAEM with the HFPAG example.

I have two headsets from different suppliers.

The connection to one of them works fine.

The connection to the other one will closed at the same point.

And I do not understand why.  

I use a STM32F4 microcontroller with the CC2564 bluetooth module.

I try to log the HCI interface as you describe in the swpa234.pdf “CapturingBluetoothHostControllerInterface(HCI)Logs”.

For my opinion the connection starts and I can get the "HFRE Call Waiting Notification Activation Indication, ID: 0x0001, Enabled: TRUE." message but after a few seconds the headset close the port.

And I get the message "HFRE Close Port Indication, ID: 0x0001, Status: 0x0001."

Do you have any idea if there is something missing in the communication on the audio gateway side?

I have a command and a HCI log file from the connection establishment.

You can find them in the zip file below.

HFPAG_cc2564_hci_log.zip

  • 0
    TI__Mastermind 22935 points

    Hi Michael,

    The sniffer file you provided is limited. When you followed the guide did you use the hcisniffer tool? It should have given you a .log file. Please provide that file.

    Jesu

  • 0 in reply to Jesu
    Prodigy 130 points

    Hello Jesu,
    thank you for your reply.
    I think I found the problem.
    I use the function "HFRE_Open_Remote_HandsFree_Port" but the parameter for the remot server port was not right.  
    Now I use the function "SDP_Service_Search_Attribute_Request" to find the right remote server port.
    As you describe in "CC256x TI’s Bluetooth Stack Basic HFGAGDemo APP" ( processors.wiki.ti.com/.../CC256x_TI’s_Bluetooth_Stack_Basic_HFGAGDemo_APP )

    To your question yes I use the hci sniffer command line tool with this command
    "java -jar hcisniffer.jar <COM Port#1> <COM Port#2> <hci baud rate#> <bt-snoop logfile#>"
    but i change the log file type from ".log" to ".cap".
    Because i use wireshark to look at the hci communication.  

    Regards Michael