CC2642R-Q1: unexpected terminating when repeat disconnect and connect after bonding.

Simon Huo

Intellectual 1790 points

Part Number: CC2642R-Q1

Hi engineers,

My customer is reporting a termination issue between CC2642 and a bonded phone.

SDK version: 5.20

reproduce environment: seldom on out of box simple peripheral example code. frequent on customized code.

reproduce steps are easy, keep disconnect and reconnect to CC2642, sometime the phone will notify disconnect due to the pairing message does not exist. But this issue can be fixed by both re-pairing and reset bluetooth (without re-pairing). Any ideas on this issue?

over 2 years ago

0 Clément over 2 years ago

TI__Guru** 101030 points

Hi Simon,

I am looping in the right team.

It would be nice you share Bluetooth LE sniffer log traces if you have some.

Best regards,

0 Simon Huo over 2 years ago in reply to Clément

TI__Intellectual 1790 points

Untitled.btt

Don't know if you can download this one.

0 Simon Huo over 2 years ago in reply to Clément

TI__Intellectual 1790 points

Hi Clement,

Do we have any update?

0 Jan over 2 years ago in reply to Simon Huo

TI__Mastermind 37550 points

Hi Simon,

Apologies for the delay, I have assigned your thread to a relevant expert and they will reply shortly. Is the customer observing this behavior on an unmodified example? If not, then could you provide a description of the modifications the customer has made?

Best Regards,

Jan

0 Barbara Wu over 2 years ago

TI__Intellectual 2260 points

Hi Simon

Can you share the sniffer log for this issue? We need more information to narrow down the reason.

Best regards,

Barbara

0 Simon Huo over 2 years ago in reply to Barbara Wu

TI__Intellectual 1790 points

Hi Barbara,

please check the sniffer log on my former reply on this thread. Let me know if you need anything else

0 Barbara Wu over 2 years ago in reply to Simon Huo

TI__Intellectual 2260 points

If the log stands here is Untitled.btt, it is not a Bluetooth Low Energy Air log, it is a HCI Injection Overview log. Can you please share air sniffer log?

0 Simon Huo over 2 years ago in reply to Barbara Wu

TI__Intellectual 1790 points

that would be a problem because now customer don't have air sniffer. what is missing in HCI log.

+1 Barbara Wu over 2 years ago in reply to Simon Huo

TI__Intellectual 2260 points

The issue is during disconnect and reconnect, we need to see ADV, CON_IND and other operation during the connection establishing process rather than the HCI command which are mostly for something after connection established. There is rarely information in current log for the issue.

Bluetooth®︎

Bluetooth forum

CC2642R-Q1: unexpected terminating when repeat disconnect and connect after bonding.