CC256x Downloads

Return to CC256x Main Wiki

CC256x Service Packs - BTS Format

The CC256x Bluetooth Service Packs (SP) are mandatory initialization scripts that contain bug fixes and platform specific configurations. They must be loaded into the corresponding CC256x device after every power cycle. The CC256x SPs are delivered in the form of a Bluetooth Script (BTS) file. A BTS file is a scripted binary file which defines the actions that should be applied to the embedded HCI commands and HCI events within the file itself.

Conversion of Service pack in to ".h" format for TI’s Bluetooth stack

Note: In order to operate the chip, the Main BT init script must be loaded first, followed by either the BLE or AVPR addons.

initscripts-TIInit_VERSION_bt_spec_4.x - Main BT init script
initscripts-TIInit_VERSION_ble_add-on - BLE init script
initscripts-TIInit_VERSION_avpr_add-on - AVPR init script - WBS support and Assisted A2DP add on

You need to convert the Service pack (SP) from “.bts” format to “.h” format using the Bluetooth hardware evaluation tool (BHET), to use it with TI’s Bluetooth stack. The BHET Tool can be downloaded from the following link and how to modify and save it as in the desired format can be found here'. For all the latest TI’s Bluetooth stack versions you need to replace \Bluetopia\btpsvend\CC256XB.h (or \Bluetopia\btpsvend\CC256X.h) files respective (by taking the backup of the original file) depending on your Chip revision.

Note: The sleep mode should be turned off in the Service Packs (SP) since this configuration is done as part of the the TI’s Bluetooth stack initialization. If using the BHET tool, the sleep mode can be turned off in the SP Configurations Panel. This option disables the "Deep sleep enable" parameter in the HCI_VS_Sleep_Mode_Configurations (0xFD0C) command that is inside the SP.

This page holds all the Service Packs (SP) required for proper operation by the different variants of TI Bluetooth device CC256x. As noted previously, the CC256x SP must be loaded first during initialization each time the device boots up.

TI Device	Module(s)	Module Vendor	Filename	Version	Comments
CC2560 * * Not recommended for new designs	PAN1315	Panasonic	CC2560_BT_SP_BTS.zip	v2.44	Classic Bluetooth 3Mbps UART baud rate XTAL Support Sleep Enabled AKA TIInit_6.2.31.bts
CC2560A * * Not recommended for new designs	PAN1315A / PAN1325A	Panasonic	CC2560A_BT_SP_BTS.zip	v2.14	Classic Bluetooth 115.2Kbps UART baud rate XTAL Support Sleep Enabled AKA TIInit_6.6.15.bts
CC2564 * * Not recommended for new designs	PAN1316 / PAN1326, PAN1323	Panasonic	CC2564 BT BLE SP BTS.zip	v2.14	Classic Bluetooth and Bluetooth Low Energy 115.2Kbps UART baud rate XTAL Support Sleep Enabled AKA TIInit_6.6.15.bts
CC2560B	CC2560B QFN PAN1315B / PAN1325B	TI QFN Panasonic	CC2560B BT 4.0 SP CC2560B BT 4.1 SP CC2560B AVPR Add-On	Service Pack Download	Classic Bluetooth 115.2Kbps UART baud rate XTAL Support Sleep Enabled AKA TIInit_6.7.16.bts If you are using TI’s Bluetooth stack SDK for MSP430 V1.4 R2 , use initscripts-TIInit_6.7.16_bt_spec_4.1.bts service pack. For any other TI’s Bluetooth stack SDK for MSP430 version before V1.4 R2, use initscripts-TIInit_6.7.16_bt_spec_4.0.bts service pack. For Tiva C release V1.1, You would need to use the BHET tool and change the baud rate to 921600 before converting it to array format for the SP to load properly.
CC2564B	CC2564B QFN CC2564MODN PAN1316B / PAN1326B	TI QFN TI MODN Panasonic	CC2564B BT 4.0 SP CC2564B BT 4.1 SP CC2564B BLE Add-On CC2564B AVPR Add-On	Service Pack Download	Classic Bluetooth and Bluetooth Low Energy 115.2Kbps UART baud rate XTAL Support Sleep Enabled AKA TIInit_6.7.16.bts If you are using TI’s Bluetooth stack SDK for MSP430 V1.4 R2, use initscripts-TIInit_6.7.16_bt_spec_4.1.bts service pack. For any other TI’s Bluetooth stack SDK version for MSP430 before V1.4 R2, use initscripts-TIInit_6.7.16_bt_spec_4.0.bts service pack. For Tiva C release V1.1, You would need to use the BHET tool and change the baud rate to 921600 before converting it to array format for the SP to load properly.
CC2564C	CC2564C QFN CC256XCQFN-EM	TI CC256XCQFN-EM	CC2564C BT 4.2 SP - Main Script (initscripts-TIInit_6.12.26.bts) CC2564C BLE Add-On - Audio/Voice processing add-on (initscripts-TIInit_6.12.26_avpr_add-on.bts) CC2564C AVPR Add-On - BLE add-on (initscripts-TIInit_6.12.26.ble_add-on.bts)	Service Pack Download	Classic Bluetooth and Bluetooth Low Energy 115.2Kbps UART baud rate Sleep Enabled Note: For Linux Users: - The baud rate must be updated to 3000000 in the Main init script: “Send_HCI_VS_UPDATE_Uart_HCI_Baudrate 0xFF36, 115200 to 3000000. Also update Com_SetParams 3000000, 1 instead of Com_SetParams 115200. From here the following steps can be followed to merge the Main init script with either the BLE or AVPR addons.

CC256xB - Updated Fixes in Service Pack 1.6

Subject	Description	Comments
BLE	When there was already one or more BLE connection active for at least 12 hours, connecting another BLE device resulted in a non-optimal BLE connection offset ('d'). This bug caused a lag in BLE data which was sent only after the link supervision timeout.
BLE	BLE disconnection might have occurred after several minutes if an already existing BLE connection in parallel with an ACL connection (slave mode) was present.

CC256xB - Updated Fixes in Service Pack 1.5

Subject	Description	Comments
BT BLE Coex	On certain race conditions, the device could lockup while BLE and ACL connections were active, and another BLE connection was being established.
SW Flow Control	For hosts working with SW flow control, there could be a missed tx packet during excessive BLE continuous transmission.

CC256xB - Updated Fixes in Service Pack 1.4

Subject	Description	Comments
Initialization	In certain platforms, there could be a race condition where calibration didn't complete successfully during init, which resulted in device becoming unresponsive

CC256xB - Updated Fixes in Service Pack 1.3

Subject	Description	Comments
BT BLE Coex	If BLE interval was shorter than 24 frames, A2DP quality was degraded due to using only 3DH1 packets
BT BLE Coex	BLE interval was multiplied (x2 or x3) during BT high throughput scenario without notifying the peer
BLE	In a certain rare/race condition, BLE connection complete event was malformed
BLE	Device could reach a lockup state if BLE Adv interval was very short
BT Connection	BT connection might not have been established successfully if both local and peer started the process at the same time
IOP	If host disabled role switch, connection to iPhone 6 was not set up successfully
Current Consumption	AVPR processor did not go into low power mode. This resulted in higher current consumption
WBS	The PCM clock accuracy had to be less than 10ppm when the CC256XB was the PCM slave during WBS mode. Higher PPM deviation may have lead to high packet loss (“ticks”) at the PCM interface, or device lockup due to the clock drifts between the BT network and PCM bus
A3DP	Device could reach a lockup state when using A3DP SOURCE to 2 SINK devices feature
BLE	Fixed an issue where packets with bad CRC were sent to remote device
BLE	Fixed an issue where device could reach a lockup state if both local and peer devices terminated the BLE connection at the same time
Test Mode	BLE TX start needed to be issued twice if number of packets was set in “HCI_VS_Set_LE_Test_Mode_Parameters” command
Configuration	There was an issue in the HCI_VS_Write_CODEC_Config (0xFD06) command when using “Fsynch Multiplier” field. If the “Frame-sync duty cycle” is set to 0 (50% duty cycle), this value may not have been calculated correctly
HFP/A3DP	No voice was heard when creating NBS after closing the A3DP stream and without disconnecting the ACL
BT SIG	BT4.0 was reported instead of BT4.1 in LMP_VER_RES
BLE A2DP Coex	Device could reach a lockup state if BLE and A2DP were working concurrently
BT Connection	6 sniff connections and 1 active ACL connection resulted in device lockup. Solution is to limit the number of sniff connections to only 5 in the controller, where the rest of the connections (2) would be active
Inquiry Scan	In rare conditions, inquiry scan could have gotten stuck, which lead to device not being discoverable

CC256xB - Updated Fixes in Service Pack 1.2

Subject	Description	Comments
New Init scripts	New init scripts added divided into three different files: Main init script - BT file with latest improvements BLE init script - BLE add on AVPR init script - WBS support and Assisted A2DP add on	In order to operate chip first use the Main init script and use the relevant add on. Important Note: Both add on files can't operate at the same time
PCM Clock extension	PCM clock extension support When CC2564 device is the master of the PCM BUS, allows the system to keep the PCM clock running even when no A3DP channel is open	The new VS command HCI_VS_Enable_PCM_Clock_Extension 0xfe4c Receives one parameter (UINT16) which indicates the time to keep the pcm clock on 0 - Keep PCM clock on forever 0xFFFF - Disable PCM clock extension - default value
Sniff	Improved collision handling in Sniff mode Fixed collision between Sniff sub rate and exit sniff

CC256xB - Updated Fixes in Service Pack 1.1

Subject	Description	Comments
Assisted A2DP	PCM clock tracking mechanism when Master over the PCM, Improved skew alignment between channels	New features added to Multi Room support
LM	Improved multiple LMP handling simultaneously. Receiving packet type table request during secure simple pairing resulted in unsuccessful connection, this issue is fixed in this version
Clock accuracy	Better clock resolution result received from hci_read_clock	Resolution of 312.5 uS
BLE stability	Improved Interoperability for spec 4.1
Low power support	Better Immunity to hardware noise over the UART lines

CC256xB - Updated Fixes in Service Pack 1.0

Subject	Description	Comments
BT SIG	BT 4.1 support	No new features were added
Host I/F	Added new event "vs_reject_voice_link_event" upon remote attempting to establish 3rd voice connection (2 voice connections are already active)
ETSI	ETSI 300 328 version 1.8.1 might still have failed despite the fix in service pack 0.2
Stability	Remote name request during A2DP data streaming might have resulted in BT getting stuck
Stability	When running loop of BLE connect-disconnect (with page scan running in background), slave side might get stuck at establishment of BLE connection
Assisted A2DP	Add support for host flow control in assisted A2DP SNK
Assisted A2DP	Fix occasional drop outs in assisted A2DP SNK
BLE	BLE slave ignored "LL terminate" indication if was busy with other peer transaction
Current Consumption	High current draw due to slave exiting latency from reception of “LL channel map” or “LL connection update” until instant
Current Consumption	Device did not enter deep sleep in sniff mode after setting LSTO to 5 seconds

CC256xB - Updated Fixes in Service Pack 0.2

Subject	Description	Comments
ETSI	ETSI 300 328 version 1.8.1
Assisted A2DP	Assisted A2DP Sink - Audio Dropout Issue
Assisted A2DP	Update Codec Configuration API to support better frequency resolution	processors.wiki.ti.com/index.php/CC256x_VS_HCI_Commands#HCI_VS_Write_CODEC_Config_.280xFD06.29
Host I/F	Added support to host flow control during assisted A2DP
BLE	Fix BLE slave latency behavior during transactions

CC256xB - Updated Fixes in Service Pack 0.1

Subject	Description	Comments
Current Consumption	Deep Sleep was not enabled after enable and disable advertising mode	Recreated 15% of the time when enable and disable advertising within a 2-3 second period
BLE	Missing BLE disconnection event after sending HCI disconnect command	The command status event was executed

CC2560A/CC2564 - Updated Fixes in Service Pack 2.14

Subject	Description	Comments
ETSI	ETSI 300 328 version 1.8.1 threshold fine tuning
IOP	Improved BLE connection statistics with LPRF 2540 device

CC2560A/CC2564 - Updated Fixes in Service Pack 2.12

Subject	Description	Comments
ETSI	ETSI 300 328 version 1.8.1
Throughput	Data streaming throughput with peer 1 drops, and stays low after attempting to connect to peer 2, and canceling create connection
Voice	WBS Audio to peer 1 lost upon connection and disconnection with any peer 2 device
Voice	Device connected with WBS to peer 1 and to peer 2. After disconnecting peer 2, when disconnecting and reconnecting to peer 1, there is no audio on peer 1
IOP	When in Master role, response to peer initiated "LMP_Feature_Request" with "LMP_Not_accepted" and reason invalid parameter, peer device crashes and connection drops

Related Documents

• CC256x Bluetooth Hardware Evaluation Tool