• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 1221 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.

CC2640R2F: Odd connection and gatt error 129

Robin Beilvert
Prodigy 105 points

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640, CC2540

Hi everyone,

I am facing an issue with a connection between a custom CC2640 board and a Samsung Galaxy J3.

With most phones, once the devices connected the connection is working well, but with that one, I get a gatt error 129 on service discovery.

I sniffed the packets exchanged with a CC2540 USB dongle and the TI Packet Sniffer software. It appears that instead of the empty PDUs that are exchanged during healthy connections, the devices are exchanging L2CAP-S messages with ACK Status "Unexp. NESN", the direction of the communications being unknown by the packet sniffer.
I can send the whole packet sniffer data on request for more details.

Something else: on most phones, I sometimes get a gatt error 133 when I try to connect to my custom board, which is solved by retrying to connect a few times. I suspect the Android stack to be a huge mess, but if anyone has a fix about that, it will be most welcome.

Looking forward for some tips !

Best regards,

Robin B.

  • 0
    TI__Guru** 105180 points
    Hello Robin,

    There isn't much specific information I can provide here as you'll need to debug the GATT errors on the handset since they are reported by its stack. I'm assuming if you don't have issues if you connect with a properly implemented GATT Client and you don't have any HW or RF configuration issues with your board.

    For Android specific questions, other users have found help on sites such as stackoverflow.net.

    Best wishes