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: IO Capability of BTdevice

Part Number: CC2564

Hi,

We are using Ti stack with STM32F4 processor. As per our understanding, there are 4 types of IO capabilities viz Display only, Keyboard only, Display with Yes No, No Input nor Output and Keyboard Display. In the stack, the enum of IO capability doesn't have Keyboard Display option. As per our requirement, we are using simple secure pairing in our design and our device has a display, which display the passkey for the initiator.  So if the remote device (initiator) is a mobile device with Keyboard Display option, whether our device will support the device?  If no, how we can solve the issue?.  

Regards,

Manoj

  • Hi,
    We have received your query and will get back to you shortly .

    Thanks
    Saurabh
  • If the remote device has Keyboard Display, and the local device has Display Only, Secure Simple pairing should be supported.
  • In the Ti stack we are using, enum of IO capability doesn't have Keyboard Display option. My query is, if a host device comes with IO capability as keyboard display, whether our stack will display the passkey?
  • Please let me know if I have any details of your situation incorrect:

    You have a CC256x with an STM32 microcontroller with Display only running the TI stack, and a mobile device running some other stack with Keyboard Display option. When initializing connection from the mobile device, the two devices will exchange IO capability information. The initiator will see that the responder has a display, and the responder will see that the initiator has a keyboard input. The passkey should be displayed on the screen (or other display) of the device running TI stack, and the mobile device should be able to input the passkey.
  • Yes, as per bluetooth specification it will work. I am specifying to Ti's Bluetooth Stack. In Ti Bluetooth stack we are using, they don't have the option for keyboard display. My confusion is that, if we try to communicate with a device set with IOcapabilty as keyboardDisplay, whether our stack will fail?

    Also, I have another doubt: As per  Bluetooth specification, if one device is displayonly and another device is DisplayYesNo then it should work unauthenticated but we are getting passkey while try to pair with one device as  displayonly and another device is DisplayYesNo.

    Thanks 

    Manoj 

  • The Keyboard Display option (as seen in the spec) is only available for LE connections. If you look at any of the Low Energy demo applications included in the stack, you'll see the inclusion of Keyboard/Display as an IO Capability.

    With regards to the issue you are seeing where you are expecting no authentication but seeing it, could you capture firmware logs and attach them? That way I can see how the 2 devices are communicating, and what is being sent back and forth between them.

  • Hi,

    Regarding the authentication issue, please find the attached log "log_pairing" file we captured using "BTlogger". The steps are 

    1. "Device" in discoverable mode.

    2.  Paired  "Device" with android mobile phone.

    3.  Connected the "Device" using s2terminal app on mobile.

    4. Disconnected.

    Thanks and Regards,

    Manoj 

    log_pairing.txt

  • Apologies, I've just been able to get back around to this. Is this issue still persisting? If so I can take a look.
  • Yes, Issue is still open.

  • In addition to the logs, could you also send the UART console printout for this issue? Is it asking for a 4 digit pin or a Passkey?