Changelog
Table of Contents
New Features
BLE5-Stack
ID | Summary |
---|---|
None | None |
BLE-Stack
ID | Summary |
---|---|
None | None |
TI Proprietary-RF
ID | Summary |
---|---|
None | None |
TI-RTOS and Drivers
ID | Summary |
---|---|
TIRTOS-1953 | Update CC26X0R2 driverlib which includes updated RF/BLE settings |
Fixed Issues
BLE5-Stack
ID | Summary |
---|---|
BLESTACK-5210 | Fixed issue with unexpected pairing package that caused responder to crash |
BLESTACK-5083 | In certain cases ICall events can be lost |
BLE-Stack
ID | Summary |
---|---|
BLESTACK-5248 | Updated simple peripheral application to re-initiate advertising upon a connection fail event caused by invalid connection PDU parameters |
BLESTACK-5211 | Fixed issue with unexpected pairing package that caused responder to crash |
BLESTACK-5194 | Wrong channel is reported back after a channel map indication |
BLESTACK-5182 | [TOF] ToF Master/Slave may go out of sync when RSSI is below -60 |
BLESTACK-5181 | [RTLS] Angle performance is not stable when antenna array 2 is used |
BLESTACK-5159 | Simple Peripheral: Advertising always uses default settings. |
BLESTACK-5075 | TI Central Device does not scan smartphone as a peripheral after turning BLE advertisements on/off |
BLESTACK-4637 | LL Fast Tx handled wrong for combination states |
TI Proprietary-RF
ID | Summary |
---|---|
None | None |
TI-RTOS and Drivers
ID | Summary |
---|---|
TIDRIVERS-3843 | CC26XX I2C driver needs to power on module before initializing |
Known Issues and Limitations
BLE5-Stack
ID | Summary |
---|---|
BLETOOLS-14 | [BTool App] Discovered devices list is never cleared |
BLESTACK-5121 | host_test app with peripheral and observer cannot be built due to memory limitation |
BLESTACK-5120 | host_test app with central and broadcast cannot be built due to memory limitation |
BLESTACK-4893 | No L2CAP connection parameter update request sent when peer device does not support LL |
BLESTACK-4058 | Host test and other applications do not receive the HCI Command Complete when HCI_LE_Rand is called |
BLESTACK-3877 | Maximum supported number of concurrent BLE connections: 2 (embedded sample applications), and 3 (Host Test). Additional connections can be supported when using Cache-As-RAM |
BLESTACK-3834 | Periodic advertisements are not supported |
BLESTACK-3685 | Number of simultaneous connections may be limited when attempting concurrent LE Secure Connections pairings |
BLESTACK-3678 | Host test peripheral + central build is not supported |
BLESTACK-2711 | Issue when Scanning for extended advertisements using the 2M PHY |
BLE-Stack
ID | Summary |
---|---|
BLETOOLS-14 | [BTool App] Discovered devices list is never cleared |
BLESTACK-5152 | Multi Role with Cache as RAM app fails to pair to 8 devices |
BLESTACK-5149 | [RTLS Passive] AoA angle calculation is deviated for boundary angles |
BLESTACK-5009 | Peer's RPA is not re-generated on address resolution timeout when local IRK is all zeros |
BLESTACK-4909 | No L2CAP connection parameter update request sent when peer device does not support LL |
BLESTACK-4902 | [RTLS] TOF is not stable for connection interval greater than 1 second |
BLESTACK-4511 | CC2640R2 OAD target boots into user app after receiving reset command during unsecure on-chip OAD with a secure BLE connection |
BLESTACK-4505 | Enabling a specific off-chip image is not working for CC2640R2 |
BLESTACK-4459 | Revert to factory image not working for CC2640R2 off-chip OAD |
BLESTACK-4263 | BIM reserves extra pages of flash when not using secure OAD |
BLESTACK-4133 | Simple Observer: Cancel the discovery during discovery process received ERROR and need to reset the board |
BLESTACK-3934 | L2CAP recombination failing in some cases when data length update combines with L2CAP packet |
BLESTACK-3641 | L2CAP Connection Oriented Channels are not available in multi-role configurations |
BLESTACK-3640 | Number of simultaneous connections may be limited when attempting concurrent LE Secure Connections pairings |
BLESTACK-2706 | Multi-role incorrectly sets gapRole_AdvEnabled when enabling non-connectable advertisements. |
TI Proprietary-RF
ID | Summary |
---|---|
None | None |
TI-RTOS and Drivers
ID | Summary |
---|---|
TIDRIVERS-3636 | I2C_transfer() occasionally fails when called from an interrupt context |
TIDRIVERS-3635 | UART_read returns 0 in portable after a power-cycle on CC13x0 and CC26x0 devices |
TIDRIVERS-1642 | NVSSPI25x driver does not work when using internal SPI CS |