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.

  • TI Thinks Resolved

CCS/CC2564: Bluetooth classic HID discovery issue with iOS

Prodigy 170 points

Replies: 7

Views: 499

Part Number: CC2564

Tool/software: Code Composer Studio

Hi, 

We have a Bluetooth Classic keyboard that is using CC2564MODN module with a MSP430F5529. FW for this product is based HID demo application and has no problem discovering and pairing with Windows or Android OS. When pairing with iOS 12 device the keyboard is not even discoverable. 

Does anyone experiences similar issue with iOS? 

Thanks for your help.

  • Hi,

    Could you please share the exact version of the host stack you are using?

    Best regards,
    Vihang
  • In reply to Vihang Parmar:

    Hi Vihang,

    I'm using BT stack for CC256xB with the latest service pack Rev 1.6.
    The iOS version , I'm trying to make the device discoverable, is 12.1.1 but it also failed with older version 10.
    Let me know if you need any additional information.

    Thanks,
  • In reply to przemkop:

    Hi,

    przemkop
    I'm using BT stack for CC256xB with the latest service pack Rev 1.6.

    Do you mean you are using the TI stack for CC256xB (e.g. CC256XMSPBTBLESW) or is it a third party stack?

    Best regards,

    Vihang

  • In reply to Vihang Parmar:

    Hi Vihang,

    I'm using TI Dual-mode Bluetooth stack for MSP430 P/N CC256XMSPBTBLESW.
    I also loaded the HIDDemo code with Service pack 1.5 R2 to MSP-EXP430F5438 dev board and try to initialize discoverability with different modes but it also failed to be work with iOS.

    Any idea what might be causing it? It works without any problem with Android or Windows OS.

    Best regards,
  • In reply to przemkop:

    Hi Vihang,

    I managed finally to make the device be discoverable with iOS by assigned the class of device to the code. For some reasons it was not required with Android and Windows OS.

    Next issue I'm having is selecting the right correct class of device. From the website calculator I found that for my combo keyboard/pointing device I should select 0x0005C0 but it didn't work. 

    I tried several other service/class device combination and the only one that worked was 0x240420. Any idea why 5C0 would not be recognizable? 

    Thanks,

    Andrew

  • In reply to przemkop:

    Can, you point to the website calculator used? We, will check and get back.. With the 0x240420 is it working with both IoS and Android devices?

    Thanks
  • In reply to Hari Nagalla:

    Not sure, if this is still a issue.. Closing for now. Please, reissue a new ticket if needs to be checked further.

    Thanks

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.