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.

CC256XSTBTBLESW: HFPAG Demo Application

Part Number: CC256XSTBTBLESW

Hello,

I have a question regarding the CC256x STM32 Bluetopia SDK demo applications.

I use the components "CC256xCQFN+STM3240GEVAL+CC256XEM-STADAPT" and the sample application HFPDemo_AG.

I can connect and pair to a HFP headset device, also commands like RingIndication work (I hear a ringing sound at the headset output). When I try to accept a call on the headset (pushbutton pressed) no further action will be taken. I cannot start a voice transmission.

My question is: How can I accept a call enabling audio transmission over bluetooth or send some audio to the headset?  In the HandsFreeProfileAPI documentation I found a prototype function "int BTPSAPI HFRE_Send_Audio_Data(unsigned int BluetoothStackID, unsigned int HFREPortID, Byte_t AudioDataLength, Byte_t *AudioData)", but this is not implemented in the sample code. Do I have to implement it myself or should the audio transmission already work after the command ManageAudio 1 with Return 0 -> Success?

Any ideas or suggestions?

Thanks in advance.

Regards

Tim

  • Tim,

    Apologies for the delayed reply. The audio connection should be set up after a successful ManageAudio, can you capture firmware logs of attempting to set up the audio connection?
  • Hi Tim,

    Were you able to capture firmware logs of the issue?
  • Hi Dale,
    I captured a firmware log:

    Attribute ID 0x0001
    Type: Data Element Sequence
    Type: UUID_16 = 0x111E
    Type: UUID_16 = 0x1203
    Attribute ID 0x0004
    Type: Data Element Sequence
    Type: Data Element Sequence
    Type: UUID_16 = 0x0100
    Type: Data Element Sequence
    Type: UUID_16 = 0x0003
    Type: Unsigned Int = 0x02
    Attribute ID 0x0005
    Type: Data Element Sequence
    Type: UUID_16 = 0x1002
    Attribute ID 0x0009
    Type: Data Element Sequence
    Type: Data Element Sequence
    Type: UUID_16 = 0x111E
    Type: Unsigned Int = 0x0106
    Attribute ID 0x0100
    Type: Text String = HFP service
    Attribute ID 0x0311
    Type: Unsigned Int = 0x003B

    HFP AG>OpenAudioGatewaylient 2 2
    Bluetooth Device Address: 0x0CE0E4E5C9D6
    Open Remote HandsFree Port = 0002
    HFRE_Open_Remote_HandsFree_Port: Function Successful ID = 0001.
    OpenRemoteHandsFreePort: HFRE_Update_Current_Control_Indicator_Status Function Status 0.

    HFP AG>
    HFP AG>
    atLinkKeyRequest: 0x0CE0E4E5C9D6
    GAP_Authentication_Response() Success.

    HFP AG>
    HFRE Open Port Confirmation, ID: 0x0001, Status: 0x0000.

    HFP AG>
    HFRE Open Servce Level Connection Indication, ID: 0x0001
    RemoteSupportedFeaturesValid: TRUE
    RemoteSupportedFeatures: 0x0000009B
    RemoteCallHoldMultipartySupport: 0x00000000
    HFRE_Enable Call Line Identification

    HFP AG>HFRE Call Waiting Notification Activation Indication, ID: 0x0001, Enabled: TRUE.

    HFP AG>
    Unknown HFRE Event Received: 11.

    HFP AG>HFRE Speaker GaiIndication, ID: 0x0001, Speaker Gain 0x0008.

    HFP AG>manageaudio 1
    HFRE_Setup_Audio_Connection: Function Successful.

    HFP AG>
    HFRE Audio Connection Indication, ID: 0x0001, Status: 0x0000.


    There is an unknown HFRE Event 11 that is received. However, the ManageAudio Command is executed successful.

    Regards
    Tim
  • Tim,

    Could you use the Logger tool to capture the firmware logs?

  • Hi Dale,
    where can I find the HCILib.xml file? It is not located in "C:\Program Files (x86)\Texas Instruments\Wireless Tools"

    Edit: I'm used the following xml file: TIInit_6.12.26.xml (CC256XC_BT_SP).

    Attached you can find the firmware log using HFP_AG demo.HFP_AG_Logger.zip

    Regards Tim

  • Hi Dale,

    did you already take a look at the firmware log file? For me it seems that the audio stream was opened successfully.

    Thanks in advance.

    Regards,
    Tim
  • Tim,

    I've taken a look at the firmware logs. Have you made sure that both the CC256xC board and the Adapter board have the hardware correctly configured? The CC256xC board should be in slave mode (www.ti.com/.../swru498a.pdf) and the Adapter board should have the EVAL USART6_I2S2 configuration (www.ti.com/.../swru416.pdf)