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: Unwanted connection request from client

Part Number: CC2564

Hello,

I have a customer who is using CC2564B with SPP profile.
They use only Classic SPP mode.

Customer reported even though they use only SPP mode, client side PC connects with other profile(A2DP, etc.).
It depends on client PC.
CC2564B works as server and port is opened, client requests A2DP profile and it seems Bluetopia stack automatically accepts the connection.

How to avoid such unwanted connection request from client ?

Thanks and regards,
KoT

  • Our BT stack expert will get back shortly..

    Thanks
  • Hello Koichiro-san,

    Which profiles will be connected from the remote device (PC in this case) depends on the Service Discovery Protocol (SDP) record on the local side (SPP). The default SDP record on the SPPDemo of the TI Dual-mode Bluetooth stack only has the serial port profile (SPP). So I do not see any case why the remote device would find any other profile to connect to.

    If you have Bluetooth Sniffer logs of this test, I would be more than happy to take a look at what is going on.

    Best regards,
    Vihang
  • Hi Vihang,

    The profile used is HandsFree profile.

    And I missed an important point. Customer uses AM335x as host processor.
    So they does not use TI SPPDemo application. They uses SS1BTPM and LinuxSPPM on top of Linux.
    In this case, other profiles are on SDP record ?

    Thanks and regards,
    KoT

  • Vihang,

    Can you reply this item ?

    Thanks and regards,
    KoT

  • KoT said:

    So they does not use TI SPPDemo application. They uses SS1BTPM and LinuxSPPM on top of Linux.
    In this case, other profiles are on SDP record ?

    Yes, other profiles are present on the SDP record when using the BluetopiaPM on Linux. In order to remove the A2DP, you will need to modify the ModuleHandlerList[] in the BTPMMODC.c to replace AUDM functions and (void*)(&AudioInitializationInfo) with NULL.

    You will need to recompile the sample applications and SS1BTPM after that. Instructions can be found at: 

    With the AUDM initialization excluded from the ModuleHandlerList, the connecting device will not connect A2DP. 

    Best regards,

    Vihang