Bluetooth forum - Recent Threads

CC2340R2: CC2340R22N0RKPR Test Reports

Josh Batty — Tue, 19 May 2026 11:15:48 GMT

Part Number: CC2340R2

Hello,

We have had a request for the test reports for module: CC2340R22N0RKPR

Please can you send over the EN & FCC Radio, EMC and Safety reports?

Any issues just let me know.

AM625: CC3300 BLE Not Functioning Properly on AM62xx Custom Board

Navami GS — Mon, 18 May 2026 13:37:06 GMT

Part Number: AM625

Hi TI Team,

I am working on a custom board based on the AM62xx platform using Processor SDK Linux (Yocto-based) for AM62x-LP, based on TI SDK version 11.01.05.03.

We are interfacing the CC33xx (CC3300) WiFi/Bluetooth module over SDIO (MMC2). We are using the `k3-am625-sk-m2-cc3351.dtso` overlay. WiFi functionality over SDIO is working correctly, and BLE over UART is getting initialized.

For enabling Bluetooth over UART, I made modifications. Please refer to the attached file for the changes made.k3-am625-sk-m2-cc3351.txt

Below are the observed logs:

root@am62xx-lp-evm:/usr/share/cc33xx# hciconfig -a
root@am62xx-lp-evm:/usr/share/cc33xx# echo 1 > /sys/kernel/debug/ieee80211/phy0/cc33xx/ble_enable

[ 440.797132] Bluetooth: MGMT ver 1.23
[ 440.838564] NET: Registered PF_ALG protocol family

root@am62xx-lp-evm:/usr/share/cc33xx# hciconfig -a

hci0: Type: Primary Bus: UART
BD Address: 34:68:B5:88:3F:48 ACL MTU: 255:10 SCO MTU: 0:0
DOWN
RX bytes:276 acl:0 sco:0 events:22 errors:0
TX bytes:121 acl:0 sco:0 commands:22 errors:0
Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: PERIPHERAL ACCEPT

Current Issues Observed:

1. BLE scan on the AM62xx board is not detecting nearby BLE devices.
2. The AM62xx BLE device is not visible on external devices such as mobile phones or laptops.
3. Using applications such as SimpleLink or nRF Connect, I am occasionally able to see the AM62xx BLE device, but connection attempts fail.

Could you please help clarify the following:

* Are there any additional initialization or configuration steps required for BLE functionality with CC3300 on AM62xx?
* Is Bluetooth over UART the recommended approach for CC33xx, or Bluetooth over SDIO?
* Are there any required firmware files, DTS configurations, or BLE enable sequences that might be missing?

Please let me know if any additional logs or configuration details are required.

Thank you.
Navami

RE: AM625: CC3300 BLE Not Functioning Properly on AM62xx Custom Board

Navami GS — Tue, 19 May 2026 07:33:37 GMT

Hi Josh,

We are using cc3301.

RE: AM625: CC3300 BLE Not Functioning Properly on AM62xx Custom Board

Navami GS — Tue, 19 May 2026 07:31:43 GMT

Hi Josh,

Thanks for the reply.

1. i have added the bluetooth node inside the sdhci2 under WiFi
2. Can you confirm you are using this patch to the kernel to add BLE driver support - > Yes Applied this `cc33xx_linux_package_1_0_2_10` patch
3. Can you verify your kernel defconfig has the following -> yes

Please refer to the ble_logs.txt
e2e.ti.com/.../ble_5F00_logs.txt

Thanks & regards
Navami GS

WL1837MODCOM8I: Request for Updated Bluetopia Stack Library with -fPIC Compiler Flag

shailesh panchal — Tue, 12 May 2026 16:10:23 GMT

Part Number: WL1837MODCOM8I

We are currently integrating the Bluetopia stack into our application environment and require the latest/updated Bluetopia stack library compiled with the -fPIC compiler flag support.

Request you to please provide:

Latest/updated Bluetopia stack library
Library compiled with -fPIC option enabled
Any related build instructions or dependency information, if applicable

This support is required to integrate the library into our shared object build environment.

Please let us know if any additional information is needed from our side.

Looking forward to your support.

Regards,

Shailesh

RE: WL1837MODCOM8I: Request for Updated Bluetopia Stack Library with -fPIC Compiler Flag

shailesh panchal — Tue, 19 May 2026 03:14:59 GMT

Thanks for your update.

We are using the AM3352 as the host device. The toolchain is gcc-linaro-5.3-2016.02-x86_64_arm-linux-gnueabihf.

Please let us know if any further information is required.

DLPC4420AEVM: Connection issue on DLPC4420AEVM // SO# 513588

Lucas Lim — Tue, 24 Mar 2026 07:07:49 GMT

Part Number: DLPC4420AEVM

Hi TI team,

Good day!

Our customer purchased a Part# DLPC4420AEVM . They feedback that had tested on this board in both USB connection and HDMI display, but it cannot connect to computer after switching on and nor can it display HDMI input with the V-by-One board connected.

They have been troubleshooting for more than 1 week and this problem still exists., even tried another DLP660TEEVM board it still has the same problem.

Kindly review and advise whether this issue is considered as defective part? If not, could you explain or provide the criteria or relevant supporting documents for customer reference.

Part details: Supplier PO# 029-C1173 // Qty: 1pc // COO: US // Date code: 2346 // Lot code: 3014615SVT

And customers have further inquiry below, please review and advise on it.

They have this user guide already and have been following its instructions all the time. They have also changed cables but the problem still exists. The symptoms are below:

Connect J31 jumper and connect USB to computer, flash splash image using GUI, this is perfectly fine with J31 jumper installed.
Power off and remove J31, 12V power on and connect USB first then flip switch to on. Computer can detect USB when splash image is showing and D5 is blinking, but once D5 stops blinking, USB connection immediately disappears.
Power off and connect V-by-One board, connect HDMI cable to computer, power on again. USB connection still has the same problem, and HDMI is not showing.

Regards,

Lucas

Mouser Electronics Inc.

RE: DLPC4420AEVM: Connection issue on DLPC4420AEVM // SO# 513588

Lucas Lim — Tue, 19 May 2026 02:43:11 GMT

Hi Shivakumar,

Good day!

Is there any update on this customer latest inquiry. Please do share with us.

Regards,

Lucas

CC2745R10-Q1: Issues with Channel Sounding (CS) using SDK f3_sdk_9_20_00_81

Weiting Liao — Mon, 18 May 2026 09:27:38 GMT

Part Number: CC2745R10-Q1

Hi Ti support team,

I am currently working on bringing up Channel Sounding(CS) feature using the car_node and key_node examples from f3_sdk_9_20_00_81.

Both projects flashed successfully onto my Launchpads without any issues.

However, when running the Python script ble_device_car_node_with_distance, I encountered errors, and no distance information was displayed.

I have attached my Python script and the error log for your reference.
ble_device_car_node_with_distance_sdk_9_20_00_81.py.txt

CS abnormal log_sdk_9_20_00_81~2.txt

Could you please provide guidance on how to correctly configure and verify the CS function?

Thank you for your support.

Best regards,
WT

RE: CC2745R10-Q1: Issues with Channel Sounding (CS) using SDK f3_sdk_9_20_00_81

Weiting Liao — Tue, 19 May 2026 00:56:42 GMT

I ran the Python script from the old SDK(f3_sdk_9_14_02_16) and the car_node and key_node examples from f3_sdk_9_20_00_81.

CS works normally and displays the distance.

I have attached the script and log for your reference.

Am I missing any steps or modifications required to make the 9.20.00.81 version of ble_device_car_node_with_distance work properly?

e2e.ti.com/.../ble_5F00_device_5F00_car_5F00_node_5F00_with_5F00_distance_5F00_sdk_5F00_9_5F00_14_5F00_02_5F00_16.py.txt
e2e.ti.com/.../CS-normal-log_5F00_sdk_5F00_9_5F00_14_5F00_02_5F00_16.txt

RE: CC2745P10-Q1: build problem with "west" for simplelink-zephyr

Mike Crowe — Mon, 18 May 2026 21:56:24 GMT

I followed up on installing an older version of the sdk manually

wget https://github.com/zephyrproject-rtos/sdk-ng/releases/download/v0.16.5/zephyr-sdk-0.16.5_linux-x86_64.tar.xz

tar xvf zephyr-sdk-0.16.5_linux-x86_64.tar.xz

cd zephyr-sdk-0.16.5/

./setup.sh

yes to all

now

west build -p always -b lp_em_cc2745r10_q1/cc2745r10_q1 samples/basic/blinky

gets past the version number for the sdk e.g.

-- Found host-tools: zephyr 0.16.5 (/home/crowe/zephyr-sdk-0.16.5)

but now gives an error when looking for CMakeSources.cmake

-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/crowe/zephyr-sdk-0.16.5/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Error at /home/crowe/zephyrproject_ti/modules/hal/ti/simplelink_lpf3/source/ti/boards/CMakeLists.txt:34 (include):
include could not find requested file:

CMakeSources.cmake

-- Using ccache: /usr/bin/ccache
-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/bin/cmake -DWEST_PYTHON=/home/crowe/venv/West/bin/python3 -B/home/crowe/zephyrproject_ti/zephyr/build -GNinja -DBOARD=lp_em_cc2745r10_q1/cc2745r10_q1 -S/home/crowe/zephyrproject_ti/zephyr/samples/basic/blinky

I get the same error with any demo project. Ideas on how to proceed?

Cheers

CC2745P10-Q1: build problem with "west" for simplelink-zephyr

Mike Crowe — Fri, 15 May 2026 18:47:55 GMT

Part Number: CC2745P10-Q1

We want to start working with BLE mesh networking. We have been developing with the CC2745 SOC using Code Composer Studio. We understand, to implement mesh networking zephyr should be used.

Before starting we followed a generic Zephyr build as outlined in

https://docs.zephyrproject.org/latest/develop/getting_started/index.html

That built the blinky demo app without issue.

We installed the simplelink-zephyr from TI with

west init -m https://github.com/TexasInstruments/simplelink-zephyr --mr v3.7.0-ti-9.14.02_ea zephyrproject

cd ~/zephyrproject
west update

west zephyr-export
west packages pip --install

An error was encontered

west: unknown command "packages"; workspace /home/crowe/zephyrproject_ti does not define this extension command -- try "west help" and "west -vv status"

west sdk install

gave a similar error

we tried to compile anyway.

west build -p=always -b lp_em_cc2745r10_q1/cc2745r10_q1 -d build_peripheral_fota_f3 zephyr/samples/bluetooth/peripheral

Make Error at ~zephyrproject/zephyr/cmake/modules/FindZephyr-sdk.cmake:109 (find_package):
Could not find a configuration file for package "Zephyr-sdk" that is
compatible with requested version "0.16".

The following configuration files were considered but not accepted:

~/zephyr-sdk-1.0.1/cmake/Zephyr-sdkConfig.cmake, version: 1.0.1

We are new to zephyr and the "west" build system, so we are probably not understanding what is going on or what is needed. Any ideas would be helpfull.

Other details;

We are working on a linux platform and creating a python virtual environment via the usual methods.

Cheers

Mike

CC2745R10-Q1: Flash driver for SW update- CC2745R10-Q1

Marcus Frech — Wed, 13 May 2026 10:36:48 GMT

Part Number: CC2745R10-Q1

Hi Customer,

is devloping custom bootloader which receives a SW binary via UART and update in internal flash of CC2745R10-Q.

What is the best way to update the binary image in internal flash?

1) Using internal TI Flash driver from SDK

2) Using NVS Driver

3) other?

What are the pro's and con's?

Many thanks and best regards

Marcus

RE: CC2745R10-Q1: Flash driver for SW update- CC2745R10-Q1

Evan W — Mon, 18 May 2026 21:27:55 GMT

Hi Marcus,

Best course of bath would to definitely be to use the NVS Driver.

RE: CC2745P10-Q1: build problem with "west" for simplelink-zephyr

Mike Crowe — Mon, 18 May 2026 20:34:25 GMT

Hi Ryan

I believe that I have. To be sure, I started over by deleting zyphyrproject and creating a new one called zyphyrproject_ti. I was carefull about the tag, I used

v3.7.0-ti-9.22.00_ea ,

the docs.zephyrproject.org site provided the following information

Document Release Versions
latest
4.4.0
4.3.0
3.7.0 (LTS)

the 3.7.0 matches the upstream tag for what I used as part of the tag.

west init -m github.com/.../simplelink-zephyr --mr v3.7.0-ti-9.22.00_ea ~/zephyrproject_ti

This worked without any apparent problem.

after that I did

west update

which updated things

next I tried

cd ~/zephyrproject/zephyr
west sdk install

which gave the following error

west: unknown command "sdk"; workspace ~zephyrproject_ti does not define this extension command -- try "west help" and "west -vv status"

but I continued with

west build -p always -b lp_em_cc2745r10_q1/cc2745r10_q1 samples/basic/blinky

and got a CMake error

CMake Error at /home/crowe/zephyrproject_ti/zephyr/cmake/modules/FindZephyr-sdk.cmake:109 (find_package):
Could not find a configuration file for package "Zephyr-sdk" that is
compatible with requested version "0.16".

The following configuration files were considered but not accepted:

/home/crowe/zephyr-sdk-1.0.1/cmake/Zephyr-sdkConfig.cmake, version: 1.0.1

The version ../../zephyr-sdk-1.0.1/ had been installed when following the

https://docs.zephyrproject.org/latest/develop/getting_started/index.html instructions, probably with west sdk install which worked there.

It seems I have an incompatible (later) version of the sdk as 0.16 was requested and I have 1.0.1 installed. Where might I tell cmake to use 1.0.1 instead. That might work.

Cheers

Mike

RE: AM625: CC3300 BLE Not Functioning Properly on AM62xx Custom Board

Josh Prushing — Mon, 18 May 2026 17:10:26 GMT

Hi Navami,

You can disregard the previous message, if you are using the CC3300 device, BLE is not supported on this device. Either CC3301 or CC3351 are our CC33xx BLE supported devices. You can see on our portfolio page which devices are BLE enabled under the 'Technology' tab: https://www.ti.com/product-category/wireless-connectivity/wi-fi/products.html#-1=cc33%3Bfalse&

Best Regards,

Josh Prushing

RE: WL1837MODCOM8I: Request for Updated Bluetopia Stack Library with -fPIC Compiler Flag

BLiu — Mon, 18 May 2026 16:40:58 GMT

Hi Shailesh, what host device are you using?

RE: AM625: CC3300 BLE Not Functioning Properly on AM62xx Custom Board

Josh Prushing — Mon, 18 May 2026 15:26:47 GMT

Hi Navami,

Can you try/verify a few of things?

in &sdhci2, can you add the following under wifi section?
- bluetooth: cc33xxbt@3 {
  compatible = "ti,cc33xxbt";
  reg = <1>;
  };
Can you confirm you are using this patch to the kernel to add BLE driver support? https://github.com/TexasInstruments-Sandbox/cc33xx-linux-mpu-ports/tree/main/ti-linux-6.12.y
Can you verify your kernel defconfig has the following? (see this thread for more information on this)
- CONFIG_BT_TI=n
- CONFIG_BT_TI_SDIO=n
- CONFIG_BT_TI_UART=m

Best Regards,

Josh Prushing

CC2744R7-Q1: CC2744R7-Q1 - how to change max num of bonding devices

Kai Kim — Fri, 15 May 2026 05:42:00 GMT

Part Number: CC2744R7-Q1

Hi Team,

Could you please guide how to change max num of bonding devices?

When modifying the maximum number of bondings, should all three parameters — GAP_BONDINGS_MAX, CFG_MAX_NUM_RL_ENTRIES, and CFG_MAX_NUM_AL_ENTRIES — be updated to the same value simultaneously?
It was initially assumed that when the maximum number of bondings has been reached and a new pairing request is received, the pairing process itself would fail. However, it appears that the pairing proceeds successfully, but the bonding information is simply not stored.
Could you please confirm whether this is the intended behavior?
Could you please advise whether there are any separate options or mechanisms available for handling cases where the maximum number of bondings is exceeded?

Best Regards,
Kai Kim

RE: CC2744R7-Q1: CC2744R7-Q1 - how to change max num of bonding devices

Barbara Wu — Mon, 18 May 2026 14:45:23 GMT

In sysconfig, under BLE -> Bond Manager, Maximum Number of Supported Bonds and LRU Bond Replacement

CC2652P7: On-Chip OAD does not success(device reset) on our custom PCB

Bank — Fri, 15 May 2026 03:44:37 GMT

Part Number: CC2652P7

Hi TI team,

I am seeing an issue with CC2652P7 On-Chip OAD on our custom PCB.

During the OAD process, the device resets before completion.

However, using the same firmware and OAD procedure on a 3rd-party PCB works normally without any issue.

Current observations:

Normal BLE operation is stable
Reset occurs only during OAD flash activity
Issue is reproducible on our custom board
See more in VDO as link below

https://drive.google.com/file/d/1SPD_FKqYAMnTbLJXbAmUBkPXXlfEqx0-/view?usp=drive_link

https://drive.google.com/file/d/1D5834ymeuhCwhrRztzAsDjdWUYWpIpOC/view?usp=drive_link

Initial checks already performed:

Same firmware/image with working board
Verified basic power stability
Reviewed reset circuit

I would like to ask for recommendations on additional debugging points or hardware checks related to On-Chip OAD/reset behavior on CC2652P7.

Schmatic: CC2652_RGBW_BLE_SMA_CHIP.pdf

Setup:

Best regards,

Bank

RE: CC2652P7: On-Chip OAD does not success(device reset) on our custom PCB

Bank — Mon, 18 May 2026 09:41:10 GMT

Hi Ryan Brown,

I add OSC debug code as below

{
    uint32_t hf      = 0;
    uint32_t lf      = 0;
    uint32_t amp     = 0;
    uint32_t avg_amp = 0;
    uint32_t startup = 0;

    hf = OSCClockSourceGet(OSC_SRC_CLK_HF);
    lf = OSCClockSourceGet(OSC_SRC_CLK_LF);

    /* =========================
     * HF Clock
     * ========================= */
    switch(hf)
    {
        case OSC_RCOSC_HF:
            Log_info0("HF = RCOSC_HF");
            break;

        case OSC_XOSC_HF:
            Log_info0("HF = XOSC_HF");
            break;

        default:
            Log_info1("HF = UNKNOWN (%u)", hf);
            break;
    }

    /* =========================
     * LF Clock
     * ========================= */
    switch(lf)
    {
        case SCLK_LF_FROM_RCOSC_HF:
            Log_info0("LF = Derived from RCOSC_HF");
            break;

        case SCLK_LF_FROM_XOSC_HF:
            Log_info0("LF = Derived from XOSC_HF");
            break;

        case OSC_RCOSC_LF:
            Log_info0("LF = RCOSC_LF");
            break;

        case OSC_XOSC_LF:
            Log_info0("LF = 32k XTAL");
            break;

        default:
            Log_info1("LF = UNKNOWN (%u)", lf);
            break;
    }

    /* =========================
     * Crystal Amplitude
     * ========================= */
    amp = OSCHF_DebugGetCrystalAmplitude();
    Log_info1("Amp = %u mV", amp);


    avg_amp = OSCHF_DebugGetExpectedAverageCrystalAmplitude();
    Log_info1("AvgAmp = %u mV", avg_amp);

    /* =========================
     * Crystal Startup Time
     * ========================= */
    // startup = OSCHF_DebugGetCrystalStartupTime();

    // Log_info1("HF startup = %u LF edges", startup);
  }

  {
    /* Route 32k clock to DIO11 */
    IOCPortConfigureSet(
        IOID_11,
        IOC_PORT_AON_CLK32K,
        IOC_STD_OUTPUT
    );

    /* Enable 32k clock output */
    AONIOC32kHzOutputEnable();
  }

3rd-party PCB

#000004 [ 0.047 ] INFO: (../Application/init.c:122) HF = XOSC_HF
#000005 [ 0.047 ] INFO: (../Application/init.c:148) LF = 32k XTAL
#000006 [ 0.051 ] INFO: (../Application/init.c:160) Amp = 375 mV
#000007 [ 0.051 ] INFO: (../Application/init.c:164) AvgAmp = 465 mV

Custom PCB

#000004 [ 0.047 ] INFO: (../Application/init.c:122) HF = XOSC_HF
#000005 [ 0.047 ] INFO: (../Application/init.c:136) LF = Derived from RCOSC_HF
#000006 [ 0.051 ] INFO: (../Application/init.c:160) Amp = 540 mV
#000007 [ 0.051 ] INFO: (../Application/init.c:164) AvgAmp = 465 mV

Regards,

Bank

RE: CC2744R7-Q1: CC2744R7-Q1 - how to change max num of bonding devices

Kai Kim — Mon, 18 May 2026 06:21:32 GMT

Hi Barbara,

3. Could you point out where I can find the configuration of max bonding situation?
I couldn't find it from the guide documentation.

Best Regards,
Kai Kim

RE: CC2745R10-Q1: Dual image OAD cannot jump to new image

Kevin Qiu — Mon, 18 May 2026 06:19:01 GMT

Hi Shuyang,

I will check this today

Regards,
Kevin

CC2745R10-Q1: Dual image OAD cannot jump to new image

Shuyang Zhong — Fri, 15 May 2026 10:46:18 GMT

Part Number: CC2745R10-Q1

I am tying to test the dual image oad example from simplelink_lowpower_f3_sdk_9_14_02_16 on a CC2745 LaunchPad. But I could not manage to jump to the new image after OAD tranfer is done.

I tried the following:

Create 2 images with image version 1.0.0 and 2.0.0 seperately. Here's my configuration for 2.0.0 project:

2. Flash the v1.0.0 hex(basic_ble_oad_dual_image_LP_EM_CC2745R10_Q1_freertos_ticlang_sb.hex), then flash the v2.0.0 bin(basic_ble_oad_dual_image_LP_EM_CC2745R10_Q1_freertos_ticlang_v2_0_sb.bin).

3. Reset the device, but the device still starts from the v1.0.0 image.

From Uniflash I can also confirm the secondary slot is not erased, which means the secure boot did not copy the new image to the primary slot, even if the version number in the image header was 2.0.0:

To confirm my steps are proper, I also verified with SimpleLink Connect app, with my v1.0.0 image and the dual_image_oad_v2 binary from the server, I can manage to complete the OAD and see the image version updated to 2.0.0 after a reset.

However, with my v2.0.0 binary, the OAD transfer can be finished, but the device still starts from the old image after a reset.

My customer sees the same with 9.20 SDK. I am not able to find what has been missing. This issue can be reproduced with the dual image OAD example in 9.14 SDK. Please help reproduce the issue and locate the reason, thanks.

Best regards,

Shuyang