• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1059 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: How to close A2DP/ HFP profile in Serial Port Profile demo of TI Bluetooth Stack Add-On For Linux platform with WL18xx and CC256x

Gavin Jiang
Intellectual 1470 points
Part Number: CC2564


Dears,

My customer are running the Serial Port Profile demo of "TI Bluetooth Stack Add-On For Linux platform with WL18xx and CC256x". And they found that the A2DP and HFP profile are opened as well.

could you please advise how to close A2DP and HFP profile at Serial Port Profile demo? thanks!

  • 0
    TI__Expert 6335 points
    Gavin,

    What exactly do you mean that A2DP and HFP profile are open? Have the streams been opened or just the profiles are active?

    Is this just the SPPDemo out of box with no modifications?
  • 0 in reply to dale
    TI__Intellectual 1470 points
    Hi Dale,
    It's the SPPDemo out of box;
    The mobile phone is able to discover there are HFP and A2DP service at CC2564 side, and Mobile phone can successfully connect CC2564 by HFP/ A2DP service.
  • 0 in reply to Gavin Jiang
    TI__Expert 6335 points

    Gavin,

    In the SPPDemo, both A2DP and HFP profiles are configured upon initialization. If you open BTPMMODC.c under static MOD_ModuleHandlerEntry_t ModuleHandlerList[], you can disable A2DP from initializing by commenting out the AUDM_InitializationHandlerFunction line (and same for HFP with the HFRM_InitializationHandlerFunction line)

  • 0 in reply to dale
    Prodigy 10 points
    Hi dale：
    I has close all the profile initializing in the BTPMMODC.c,but phone also connect the A2DP and HFP proflie.

    static MOD_ModuleHandlerEntry_t ModuleHandlerList[] =
    {
    //{ AUDM_InitializationHandlerFunction, NULL, AUDM_DeviceManagerHandlerFunction },
    //{ BASM_InitializationHandlerFunction, NULL, NULL },
    //{ FMPM_InitializationHandlerFunction, NULL, FMPM_DeviceManagerHandlerFunction },
    //{ FTPM_InitializationHandlerFunction, NULL, FTPM_DeviceManagerHandlerFunction },
    //{ HDPM_InitializationHandlerFunction, NULL, HDPM_DeviceManagerHandlerFunction },
    //{ HDSM_InitializationHandlerFunction, NULL, HDSM_DeviceManagerHandlerFunction },
    //{ HFRM_InitializationHandlerFunction, NULL, HFRM_DeviceManagerHandlerFunction },
    //{ HIDM_InitializationHandlerFunction, NULL, HIDM_DeviceManagerHandlerFunction },
    //{ HOGM_InitializationHandlerFunction, NULL, HOGM_DeviceManagerHandlerFunction },
    //{ HRPM_InitializationHandlerFunction, NULL, NULL },
    //{ MAPM_InitializationHandlerFunction, NULL, MAPM_DeviceManagerHandlerFunction },
    //{ OPPM_InitializationHandlerFunction, NULL, OPPM_DeviceManagerHandlerFunction },
    //{ PANM_InitializationHandlerFunction, NULL, PANM_DeviceManagerHandlerFunction },
    //{ PBAM_InitializationHandlerFunction, NULL, PBAM_DeviceManagerHandlerFunction },
    //{ PXPM_InitializationHandlerFunction, NULL, PXPM_DeviceManagerHandlerFunction },
    { NULL, NULL, NULL }
    } ;
  • 0 in reply to dale
    TI__Intellectual 1470 points

    Hi Dale, 

    Could you please help to look into it? Is there something we are missing? thanks!