CC2642R-Q1: passkey_entry disconnect but fail to reconnect

Hello,

Thank you for posting on the E2E forums! What SDK is the CC2642R-Q1 currently running on? 

Best,

Nima

hi Nima,

The SDK version is 5.40

Hi Simon,

Thank you. Is there any way you could provide a sniffer log? 

Best,

Nima

Hi Nima,

Sorry for late response, that's because I'm trying to get the sniffer log. please check from below tidrive link

tidrive.ext.ti.com/.../a26b260b-b7e1-4dbc-81a9-b6077c1a177e

Hi Simon,

No worries! Thank you for the sniffer logs those are helpful. What are the advertisement and connection parameters for the CC2642R-Q1 device, and if possible the same for the non-TI BLE device?

Best,

Nima

Hi Nima,

For 2642 it is the same as multi_role example code.

For non-TI device is 50ms interval , 2s timeout, 0 latency

Hi Simon,

After reviewing the logs, it appears that the peripheral is sending out a feature request and getting no response from the central device. I tested a TI peripheral and TI central with the same connection parameters that you gave and had no issues connecting after powering off and powering on the central device. If possible, try to find out why the central device is not responding to the feature request sent by the peripheral. If you can provide those logs that would be helpful as well.

Best,

Nima

Hi Nima,

Thanks for your help. Just to clarify, did you test in passkey mode and bond? It seems this problem only happens after bonding.

HI Nima,

In addition, I asked customer to provide a sniffer log with whole set of non-TI device, please check as below.

tidrive.ext.ti.com/.../72c1d8b6-a8a9-4e88-bc3c-bd32ae819d9c

Hi Simon,

Thank you for the logs, I will look into them and get back to you.

Best,

Nima

Hi Nima,

Any update?

Hi Simon,

I'm still looking into this and will get back to you with more updates tomorrow. Thank you for your patience.

Best,

Nima

moving to email for further talk.