Connection Terminate with 0x05/0x16 during bonding request.

Ramesh Kumar Jayaraj

Other Parts Discussed in Thread: CC2540

Hello,

I am using CC2540 USB BLE Dongle with PC Application implemented in .Net.

Following Bond parameter has been set during initialization of this dongle.

GAPBOND_PAIRING_MODE -> 01-GAPBOND_PAIRING_WAIT_FOR_REQ
GAPBOND_MITM_PROTECTION -> 00-Disabled
GAPBOND_BONDING_ENABLED -> 01-Enabled
GAPBOND_IO_CAPABILITIES -> 03-No I/p No O/p

We are facing some issues in bonding when connected with the central devices, and receiving terminate command with reason code 0x05 in peripheral device.

But the Central device receiving terminate command with reason code 0x16.

This teminate command with reason code with 0x05/0x16 is not occuring when connection happening with pairing request.

After the devices gets paired, in the next connection with Bonding the devices, after connection establishment, terminate happens.

Kindly let us know the possiblity of the terminate connection with reason code 0x05 during bonding request.

Also please let us know is there any work arround or solution to resolve the problem with his terminate connection.

Note:

When we flash the host test image with bonding enabled, the issues is not occurring till some 10+ central devices get connecting with it.

After that we start receiving termination command with 05, once the connection gets established.

Regards,

Ramesh Kumar

over 10 years ago

0 Zahid Haq over 10 years ago

TI__Mastermind 25035 points

Hi,

Are you using the CC2540 dongle as the slave? what are you using as the master? Can you get us a sniffer log of the issue? If you disable bonding, there's no disconnect?

Best wishes

0 Ramesh Kumar Jayaraj over 10 years ago in reply to Zahid Haq

Intellectual 310 points

Hi,

Yes. We are using CC2540 dongle as the salve and Smart RF board as Central.

Please find the sniffer log of the issue occurring with the CC2540 dongle connected with more that 10 different centrals.

"If you disable bonding, there's no disconnect?" - I'm not clear about what you are asking.

05_issue.zip

Thanks and Regards,

Ramesh Kumar

0 Ramesh Kumar Jayaraj over 10 years ago in reply to Ramesh Kumar Jayaraj

Intellectual 310 points

HI Zahid Haq ,

Have you gone the sniffer logs? I am waiting for the remedy to fix the Connection termination with reason code 0x05 in peripheral.
Is there any way related with BONDING? and how should I use ERASE_ALL_BONDING command to clear the bonding information in peripheral part?

0 Zahid Haq over 10 years ago in reply to Ramesh Kumar Jayaraj

TI__Mastermind 25035 points

Hi,

Please see this relevant post:

The maximum number of bonding allowed is 10 in the CC254x. You should erase some or all bonds after reaching this max number before attempting another bonded connection.

Best wishes

0 Ramesh Kumar Jayaraj over 10 years ago in reply to Zahid Haq

Intellectual 310 points

Hi Zahid Haq,

Please find the below post which I posted related to the issue in clearing the bonding in peripheral side.

e2e.ti.com/.../506783
Erase All Bonded devices from Peripheral

Kindly go through the post and help me in clearing the bonding information in peripheral side.

Thanks and Regards,
Ramesh Kumar

Bluetooth®︎

Bluetooth forum

Connection Terminate with 0x05/0x16 during bonding request.