Release Notes History
www.ti.com
102
SWRU271H–October 2010–Revised April 2019
Submit Documentation Feedback
Copyright © 2010–2019, Texas Instruments Incorporated
General Information
– The simple GATT profile has a new fifth characteristic. This characteristic is 5 bytes long, and has
readable permissions only while in an authenticated connection. It should serve as a reference for
development of other profiles which require an encrypted link.
– All GATT profiles have been updated to properly handle client characteristic configurations for both
single and multiple connections. Characteristic configurations now get reset to zero (notifications /
indications off) after a connection is terminated, and the bond manager now stores client
characteristic configurations for bonded devices so that they are remembered for next time when
the device reconnects.
– Added linker configuration file for support of 128kB flash versions of the CC2540. An example is
included in the SimpleBLEPeripheral project.
– The SimpleBLEPeripheral project "CC2540 Slave" configuration has been updated to better support
the SmartRF05EB + CC2540EM hardware platform, making use of the LCD display.
Bug Fixes:
• The following bugs have been fixed in the controller stack:
– Scanning now working for master devices with power savings enabled.
– RSSI reads no longer require a data packet to update.
– Improved stability when using very high slave latency setting
– HCI LE direct test modes now working properly.
– HCI Read Local Supported Features now returns the proper value.
– Use of two advertising channels now works.
– When connecting to a device on the whitelist, the correct peer device address is returned to the
host.
• The following bugs have been fixed in the host stack:
– Pairing no longer fails when either device is using a static, private resolvable, or private non-
resolvable address.
• The following bugs have been fixed in the profiles and applications:
– Reading of RSSI with peripheral role profile now working.
– Peripheral role profile now allows all legal whitelist modes.
– Can now connect with short connection intervals (such as 7.5 ms), since bond manager now reads
data from NV memory upon initialization rather than immediately after a connection is established.
Pairing still may not be stable when using the bond manager with very short connection intervals
(for reason noted in the following Known Issues section)
Known Issues:
• Use of the NV memory (to save application data or Bluetooth Low Energy Host bonding information)
during a Bluetooth Low Energy 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.
• Duplicate filtering does not work when scan is used in combination with a connection.
For technical support, visit the Texas Instruments Bluetooth Low Energy E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
To Next Page
Loading...
Need help?
General
