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.

CC2640R2F: GATT_ERROR 0x85

Part Number: CC2640R2F

Hello,

I am using peripheral on cc2640R2 and android as Master device. Most of the time when i try to connect to cc2640R2f i get GATT_ERROR 0x85 (133) in connection State change callback in android.

I am wondering why it is happening. Is it the problem on peripheral that the Master is getting the error? Or is it a problem withe th on android device.

I have tested several android devices and all show the same problem.

I would be looking for your kind help.


Regards

MAbbas

  • Hi MAbbas,

    As per the Bluetooth Specification 4.2 Vol 3, Part F Section 3.4.1.1, the error codes in the range between 0x80-0x9F are "Application error code defined by a higher layer specification."

    Do the android docs provide more information about this or where this might come from?
    Do you have a sniffer capture of this?
  • Hi Sean,

    Thanks for replying. Unfortunately Android don,t provide any good documentation about these errors. It only says GATT_ERROR. Here is the link for android BLE error codes 

    https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/5738f83aeb59361a0a2eda2460113f6dc9194271/stack/include/gatt_api.h

    I have used the sniffer and it shows that the CONNECT_IND is sent from the android but no connection established. 

    The android application gets the 0x85 in call back.

    Regards

    MAbbas

  • Hi MAbbas,

    Thanks for the information.

    When you say that no connection is established, does this mean that you do not see the CC2640R2 show up on the data channel at the instant provided by the connection event? Does the master continue to provide connection events until declaring the connection as dropped?

    If you have the sniffer capture, would you mind posting it here?
  • Hi Sean,

    Thanks for your reply. I can see the cc2640R2 advertising and I also saw connection events. Yes, the master continues to provide connection events until the connection is established.

    I have not saved the sniffer logs but i just saw a few times ago.

  • Hi MAbbas,

    And none of these data channel/CE packets are acd'd by the peripheral?

    Does the peripheral keep advertising? If you attach the debugger to the peripheral, does it ever receive the link established event?