Bluetooth forum - Recent Threads

CC2642R: Select right device for BLE Audio Profile

Motoyasu Hattori — Fri, 03 Jul 2026 05:42:32 GMT

Part Number: CC2642R

Hi,

My customer is looking for the TI's BLE module under following specification. Could you please let us know the right modules?

BLE Audio
Require UART and I2S
Require TI module
Need BLE's Audio Profile

Please advise us.

Thanks and best regards,
M.Hattori.

RE: CC2642R: Select right device for BLE Audio Profile

Lea — Fri, 03 Jul 2026 07:59:37 GMT

There are also custom BLE implementations of BLE audio that you can find here : https://software-dl.ti.com/lprf/simplelink_cc2640r2_latest/docs/blestack/ble_user_guide/html/voice/ble_voice.html

Depending on the type of product that you are building, a vendor-specific profile like this one could be enough.

Kind regards,
Lea

RE: CC2642R: Select right device for BLE Audio Profile

Lea — Fri, 03 Jul 2026 07:57:05 GMT

Hi !

Since Bluetooth 5.2, the SIG has designed the Basic Audio Profile, which is designed specifically for audio over BLE. You can read about this profile here : https://www.bluetooth.com/specifications/specs/basic-audio-profile-1-0-1/. This sounds like the profile you should use for inter-compatibility with audio devices on BLE.

Do note that TI does not currently provide an implementation of this audio profile. The customer will have to implement this profile themselves.

The recently released CC2340R5MODA has BLE and UART but no I2S.
The CC27xx devices have BLE, UART and I2S, but TI does not provide a module for these chips.
The CC2650MODA do not support Bluetooth 5.2

The CC2652RSIP / CC2652PSIP / CC2651R3SIPA all have an I2S, BLE 5.2 and UART. You can either chose one of these modules, or use a third party module for the CC27xx.

Kind regards,
Lea

RE: CC2745R10-Q1: CC2745 BLE Initialization

Ryan Brown1 — Thu, 02 Jul 2026 15:18:43 GMT

Please use Uniflash -> Settings & Utilities -> Read HSM information to confirm that it is version 3.0.0 or higher

[quote userid="706437" url="~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1657552/cc2745r10-q1-cc2745-ble-initialization/6402503"]Sorry for that path was "<SDK_INSTALL_DIR>\examples\rtos\<BOARD_NAME>\ble5stack\hexfiles\mcuboot_onchip_<BOARD_NAME>_nortos_ticlang.hex"

Which cannot found that hex file which using in document.[/quote]

This folder location does not intend to have on-chip MCUBoot/BLE application pre-build images. You will need to import the MCUBoot and on-chip basic_ble examples into Code Composer Studio, follow the README/SimpleLink Academy instructions, and build the projects to generate the necessary .hex and .bin files.

[quote userid="706437" url="~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1657552/cc2745r10-q1-cc2745-ble-initialization/6402506"]By the way, both cc2745R10 board now cannot using BLE even its same code as its already works. Its be like this after I tried OAD project. Did you have way to reset or restore some config on MCU?[/quote]

You should be able to re-program the basic_ble project without the OAD feature and, so long as the HSM is connected, see the UART UI and Bluetooth LE advertising packets.

Regards,
Ryan

CC2745R10-Q1: CC2745 BLE Initialization

Andrew Nguyen — Tue, 23 Jun 2026 04:54:54 GMT

Part Number: CC2745R10-Q1

Hi team,

Health Innovision is currently developing a project using CC2745. Can you have a look at their problems below and advise accordingly?

Here is a summary of our current critical issues and questions:

Critical Issues:

1. BLE Issue: The "Example basic_ble_oad_dual_image" source code is not working with the CC2745R10. We followed the instructions in the README.md file, but encountered an error during flashing.
2. Hardware Issue: One of our CC2745R10 boards is now unable to initialize BLE, despite running the exact same firmware that works on our other board. We can return this board to you for further investigation if needed.

Questions:

1. Project Structure: Most example projects share source files rather than dedicating specific files to individual projects. This makes modification difficult, as changing a shared file impacts subsequent projects. Do you have a recommended best practice to prevent this?
2. Concurrent Tasks: We need to run two or three tasks concurrently. Could you provide an example that demonstrates using BLE alongside a data gathering task that displays results on a TFT or LCD?

CC2745R10-Q1: Inconsistent CS results between car node and key node

Shreeya J — Thu, 02 Jul 2026 11:54:36 GMT

Part Number: CC2745R10-Q1

Hello Team,

CCS IDE: 20.3.1

SDK: simplelink_lowpower_f3_sdk_9_14_02_15

Car node flashed in: CC2745R10-01 Launchpad having one antenna (initiator)

Key node flashed in: Custom board CC2745R10 having 2 antennas in PCB(reflector)

Distance between these two boards is fluctuating drastically, where car node is kept stationary and key node is moved away. The actual diastance is less than 1m, initially the car node shows 10cm after moving keynode and bringing to the previous position, it is showing 71cm. Sometimes distance is decreasing as keynode is moved farther away and shows more distance if the boards are closer. The results suddenly jumps from 30cm to 250cm, when the boards are staionary.

Note: python script is not used for CS here as shown in the original example of the stack. We modified the stack in car node to automatically connect with keynode and initiate CS procedure with default parameters set.

Please guide me through the changes to be done which can improve the results and reach me if any additional information is required.

please find below sysconfig screenshots of carnode and keynode.

regards,

shreeya

RE: CC2745R10-Q1: CC2745 BLE Initialization

Apinya Phanumphai — Thu, 02 Jul 2026 06:31:29 GMT

By the way, both cc2745R10 board now cannot using BLE even its same code as its already works. Its be like this after I tried OAD project. Did you have way to reset or restore some config on MCU?

RE: CC2745R10-Q1: CC2745 BLE Initialization

Apinya Phanumphai — Thu, 02 Jul 2026 06:28:47 GMT

Sorry for that path was "<SDK_INSTALL_DIR>\examples\rtos\<BOARD_NAME>\ble5stack\hexfiles\mcuboot_onchip_<BOARD_NAME>_nortos_ticlang.hex"

Which cannot found that hex file which using in document.

RE: CC2745R10-Q1: CC2745 BLE Initialization

Apinya Phanumphai — Thu, 02 Jul 2026 06:26:33 GMT

Answer:

Critical
1. No I only follow README file in project after imported. I just know HSM from link you provide so I still not do anything with its.
2. I will try but now not, No custom design just use demo kit.

CC2745P10-Q1: Programming CC2745 with CMSIS-DAP interface

Mike Crowe — Thu, 18 Jun 2026 19:28:38 GMT

Part Number: CC2745P10-Q1

I have been devloping wiht the lp_em_cc2745r10_q1 evaluation board using the TI branch of openocd (openocd_1_3.1.50). Our production programming environment uses CMSIS-DAP interfaces. When we adjust interface to the cmsis-dap e.g.

#source [find interface/xds110.cfg]
source [find interface/cmsis-dap.cfg]

we get the following error:

Open On-Chip Debugger 0.12.0+dev-00006-g98b4ef45b (2026-03-10-10:04)
Licensed under GNU GPL v2.
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
* init
Error: unable to find a matching CMSIS-DAP device

To validate the hardware, when the stock openocd application was used, the interface was found and even was able to reset the cc2745 before failing (we had to select a differnt chip to get things to go)

The stock openocd fails when encountering "-switch-thru-dormant" in target/cc27xx.cfg We tried to remove it, but it still faild

Any ideas of how to proceed would be useful.

Cheers

Mike

RE: CC2745P10-Q1: Programming CC2745 with CMSIS-DAP interface

Mike Crowe — Wed, 01 Jul 2026 22:26:02 GMT

I checked out the GitHub source and configured with

./configure --enable-cmsis-dap

it complained about needed hidapi which was fixed with

sudo apt install libhidapi-dev

./configure --enable-cmsis-dap

make

sudo make install

I then ran with my script and it worked without issue. I think my problem was that I had grabbed a binary ti version which must not have had the support enabled, certainly version 1.1.0 and 1.1.1 did not.

I consider this issue resolved.

Thank you so much for helping me with this. It will make my production guys happy!

Cheers

Mike

RE: CC2745P10-Q1: Programming CC2745 with CMSIS-DAP interface

Alex Fager — Wed, 01 Jul 2026 18:57:57 GMT

Hello Mike,

I would like to double check that all the dependenices are fuilfilled here? In the GitHub - TexasInstruments/ti-openocd: TI OpenOCD Fork · GitHub in the

OpenOCD Dependencies section.

Can you also detail your exact steps/commands used right before the build/flash fails?

Thanks,
Alex F

RE: CC2745P10-Q1: Programming CC2745 with CMSIS-DAP interface

Mike Crowe — Wed, 01 Jul 2026 15:51:49 GMT

Sorry for the delay, I was pulled onto another project for a few days.

I downloaded both version and gave them a try.

1.1.0

sudo ./bin/openocd -f gcdc1483-program.cfg -d

gave the following during the enumeration process

Debug: 87 63 cmsis_dap_usb_bulk.c:170 cmsis_dap_usb_open(): found product string of 0x0d28:0x0204 'DAPLink CMSIS-DAP'
Debug: 88 63 cmsis_dap_usb_bulk.c:190 cmsis_dap_usb_open(): enumerating interfaces of 0x0d28:0x0204
Debug: 89 64 cmsis_dap_usb_bulk.c:250 cmsis_dap_usb_open(): skipping interface 0, has only 1 endpoints
Debug: 90 64 cmsis_dap_usb_bulk.c:300 cmsis_dap_usb_open(): skipping interface 1, class 10 subclass 0 protocol 0
Debug: 91 64 cmsis_dap_usb_bulk.c:237 cmsis_dap_usb_open(): found interface 2 string 'QYF-CMSIS-DAP'
Debug: 92 64 cmsis_dap_usb_bulk.c:257 cmsis_dap_usb_open(): skipping interface 2, endpoint[0] is not bulk out
Debug: 93 65 cmsis_dap_usb_bulk.c:237 cmsis_dap_usb_open(): found interface 3 string 'WebUSB: CMSIS-DAP'
Debug: 94 65 cmsis_dap_usb_bulk.c:250 cmsis_dap_usb_open(): skipping interface 3, has only 0 endpoints

1.1.1 gave a similar result

Debug: 85 31 cmsis_dap_usb_bulk.c:170 cmsis_dap_usb_open(): found product string of 0x0d28:0x0204 'DAPLink CMSIS-DAP'
Debug: 86 31 cmsis_dap_usb_bulk.c:190 cmsis_dap_usb_open(): enumerating interfaces of 0x0d28:0x0204
Debug: 87 32 cmsis_dap_usb_bulk.c:250 cmsis_dap_usb_open(): skipping interface 0, has only 1 endpoints
Debug: 88 32 cmsis_dap_usb_bulk.c:300 cmsis_dap_usb_open(): skipping interface 1, class 10 subclass 0 protocol 0
Debug: 89 32 cmsis_dap_usb_bulk.c:237 cmsis_dap_usb_open(): found interface 2 string 'QYF-CMSIS-DAP'
Debug: 90 32 cmsis_dap_usb_bulk.c:257 cmsis_dap_usb_open(): skipping interface 2, endpoint[0] is not bulk out

Debug: 91 33 cmsis_dap_usb_bulk.c:237 cmsis_dap_usb_open(): found interface 3 string 'WebUSB: CMSIS-DAP'
Debug: 92 33 cmsis_dap_usb_bulk.c:250 cmsis_dap_usb_open(): skipping interface 3, has only 0 endpoints
Error: 93 34 cmsis_dap.c:287 cmsis_dap_open(): unable to find a matching CMSIS-DAP device
Debug: 94 34 command.c:529 exec_command(): Command 'init' failed with error code -4

Any other ideas?

Cheers

Mike

RE: CC2745R10-Q1: CC2745 BLE Initialization

Ryan Brown1 — Wed, 01 Jul 2026 13:01:48 GMT

Hi Apinya,

The image you tried to share did not attach correctly, and so I do not know what hex file path you are referring to. Keep in mind that hex files have to be generated by building the project and are typically accomplished through a Project Properties -> Build -> Steps -> Post-build step.

Regards,
Ryan

CC2652P: Does it back off from 20dB to 14dB sometimes?

Raphael Fischer — Fri, 26 Jun 2026 09:17:41 GMT

Part Number: CC2652P

Hello everyone!

We are running a PCB based on the Launchpad CC1352P1-2 (the 20dBm circuit). It has the CC2652P and a DC/DC converter to 3.3V in front of it. We have configured our firmware to have two advertisement sets: One at 1M phy and one at coded-8, both at 20dBm:

We then took a power profiling measurement and were quite surprised by the fact that some peaks, especially all of the longer coded8 advertisement packets, only go up to 45mA.

The current consumption at 20dBm is 85mA. We asked Claude about this and it suspected that for regulatory or overheating reasons, the chip automatically backs of to around 14dBm in some cases.
Is this true? Can you please give us more details about this?

Thank you for your help and kind regards,
Raphael

RE: CC2652P: Does it back off from 20dB to 14dB sometimes?

Raphael Fischer — Wed, 01 Jul 2026 09:27:54 GMT

Hi Jan!

Here are the measurements with the Smart RF studio: On the left, you see the configuration, on the right the measurement. I measured the three BLE advertising channels 37, 38 and 39:

Thank you for your help!

Best,
Raphael

PS: Sorry, for some reason it doesn't want me to upload the picture with channel 39. The average current there is 90.89mA

RE: CC2745R10-Q1: CC2745 BLE Initialization

Apinya Phanumphai — Wed, 01 Jul 2026 07:20:21 GMT

Its have no hex file in that path.

RE: CC2745R10-Q1: CC2745 BLE Initialization

Apinya Phanumphai — Wed, 01 Jul 2026 07:20:06 GMT

test

RE: CC2745P10-Q1: Channel sounding procedure getting timeout error

Vaibhav Patil — Wed, 01 Jul 2026 05:58:46 GMT

Hi Eshaan,

Any updates? we are waiting for response.

Regards

Vaibhav

CC2745P10-Q1: Channel sounding procedure getting timeout error

Vaibhav Patil — Wed, 10 Jun 2026 12:11:49 GMT

Part Number: CC2745P10-Q1

Hi Forum,

I am working on an application where the reflector may go out of range temporarily. When the reflector comes back into range, I attempt to restart the Channel Sounding (CS) procedure by executing below statements. But i am getting the timeout error.

Output logs:

SDK Version : 9.14.01.16

Car_node : CC2745R10-Q1

Key_node : CC2340R53

Regards
Vaibhav

RE: LAUNCHXL-CC26X2R1: Missing BLE Packets

Ravi Rawat — Wed, 01 Jul 2026 04:45:38 GMT

Currently, I scan for 300 ms at a time and repeat the scan 5 times. The BLE device advertises approximately once every second. Increasing the scan duration will increases the overall production cycle time, which is a concern for our application.

what would you recommend as the best scanning strategy to maximize detection reliability while keeping the cycle time as short as possible?

LAUNCHXL-CC26X2R1: Missing BLE Packets

Ravi Rawat — Tue, 30 Jun 2026 10:21:31 GMT

Part Number: LAUNCHXL-CC26X2R1

I am using a CC26X2R1 LaunchPad flashed with the HostTest firmware and communicating through BTool.

I am trying to scan and read the advertisement data from a BLE device. However, BTool occasionally fails to detect this some devices, even though it is advertising correctly. After stopping and restarting the scan (or retrying a few times), the device is eventually discovered.

This issue occurs more frequently when there are many BLE devices advertising nearby (approximately 10–50 devices in a production-line environment).

Are there any recommended scan parameters (scan interval, scan window, active/passive scan, duplicate filtering, etc.) for improving device discovery in a high-density BLE environment?
Are there any known limitations of HostTest/BTool when scanning in environments with many simultaneously advertising devices?

Any suggestions or recommendations would be greatly appreciated.

CC2340R5: Zephyr lpn node publish nodel issue

Michael Ostrovsky — Tue, 30 Jun 2026 21:01:12 GMT

Part Number: CC2340R5

I designed lpn node using CC2340r5MODA. During provisioning I publish battery model to be transmitted periodically. After provisioning everything works correctly. Battery information is correctly periodically transmitted, but after cycling power model publish information is lost, probably never storded to flash or never extract back, but address to publish is rememberd. Everything else is working correctly.

What do I need to do to to make it work correctly. Publish address for battery model is correct and rememberd duriong cycling power (it used to send other command messages from lpn node), but battery information never gets published after cycling power.

Thanks,

Michael Ostrovsky

RE: LAUNCHXL-CC26X2R1: Missing BLE Packets

Jan — Tue, 30 Jun 2026 20:20:48 GMT

Hi,

Thank you for reaching out. Can you provide some details on your set up? What SDK version are you using? What are the scan parameters and advertising parameters used by host_test and the nearby devices)? Typically for scanning, you want to scan more than twice as long as the advertising interval of the device you want to scan to maximize the change you hear it. That said, if you are in a very noisy environment here is chance that some packets will be missed due to interference and packet collisions.

Best Regards,

Jan

CC2340R5: DCDC Switching Frequency

Til Schoengarth — Tue, 30 Jun 2026 11:06:06 GMT

Part Number: CC2340R5

Hello team,

when using the internal DCDC, will the switching frequency always stay at the same frequency (I measured it is 2MHz)?

BR,

Til