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.

weird behavior of CC2540 bonding with one device and then connect to other device

Other Parts Discussed in Thread: CC2540

Hi all,

My customer use the CC2540 dongle with BTOOL to pairing and bonding our device. The bonding setting and operating steps(>25 times) works very well. (bonding process refers CC2540miniDK user guide)

After the above steps, we use the TI BLE Device Monitor app to connect our device, it can be found. And we read "Simple Profile Characteristic" several times, it shows "Error:132". Even re-open APP, BT and our device.

But another new device(never pairing and bonding with BTOOL) is no problem.

Does anyone have any idea? thanks.

Does this issue link to known issue in readmein BLE stack?

- Use of the NV memory (to save application data or BLE Host bonding
  information) during a BLE connection may cause an unexpected disconnect.
  The likelihood of this happening increases with frequent usage, especially
  when using short connection intervals. The cause is related to the NV wear
  algorithm which at some point may cause an NV page erase which can disrupt
  system real-time processing. It is therefore recommended that the NV memory
  be used sparingly, or only when a connection is not active.

When host bonds the BLE device, it writes the bonding information to NV memory.
The problem is that if the bonding is again and again, then CC2540 BLE function maybe fail permanently?

  • Hi Natalie,
    That is probably not the issue here. The compacting process on the NV system happens when a 2 KB page is full. You have to bond a lot of times to make that happen. It may temporarily disrupt the BLE connection timing (especially for short connection intervals) and could potentially cause a disconnect. However, the device should be connectable again after.

    Do you have access to a BLE sniffer to see the response from the CC2540 on the connection request?

    Peder