Bluetooth forum - Recent Threads

CC2745P10-Q1: SimpleLink Connect crashes when Provisioning

Mike Crowe — Wed, 20 May 2026 22:20:09 GMT

Hello TI BLE developers!

I have FLASHED a cc2745 eval board with zephyr/samples/bluetooth/mesh_uart_bridge as suggested at https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AaJ-ylOFolFnxondJMqyzQ__SIMPLELINK-ACADEMY-CC23XX__gsUPh5j__LATEST

I get to step 5 and press the Provision button. The progress bar gets to ~60% then SimpleLink Connect crashes. I am using "west init -m https://github.com/TexasInstruments/simplelink-zephyr --mr v3.7.0-ti-9.14.02_ea zephyrproject_ti" as the downstream code base.

I've tried this on a tablet and a cell phone and gotten the same result. The code on the evaluation board doesn't crash, but to repeat the crash I do have to reprogram the evaluation board.

Any ideas on how to proceed?

Cheers

Mike

CC2340R5-Q1: How to find BLE pairing keys to be able to decrypt BLE sniffer packets.

Rasikraj Deshmukh — Wed, 20 May 2026 12:32:06 GMT

Part Number: CC2340R5-Q1

Hello team,

I wanted to insert manulaly the BLE pairing keys within sniffer tools (e.g. Ellisys)

As I know, it can be done by follwoing way as highlighted.

However, if I want to get these keys from within debug session in the software e.g., copy it manually and insert this into BLE sniffer tool, then how this shall be done?

Regards,

Rasikraj.

CC2745R10-Q1: Secure boot key update process

Abhirami K — Wed, 20 May 2026 06:05:22 GMT

Part Number: CC2745R10-Q1
Other Parts Discussed in Thread: UNIFLASH

I'm trying to perform a key update using the following steps:

1. Generating keys using the ./imgtool keygen commands.

2. Generating the key update image signed with the default TI key using ./sbtool init --key-update-key command.

3. Flash the application image signed by the test keys (from SDK) in the primary slot.

4. Use the generated app_kui.bin and flash it via Uniflash at an unused address in the main flash region (Eg. 0xE0000).

5. Call the following code from the current application:

HapiSbSetUpdateImageAddress( 0xE0000 );

HapiSbSetId( 3 );

6. Reset

However, when I read the status of the operation using HapiSbGetStatus(), it returns 3 (Image rejected).

Is there something missing in the steps or that should be done differently?
Should the security counter of the key update image be increased? If yes, how can it be done from the command?
And should the version of the key update image be higher than the application? If yes, how can it be done from the command?

CC2652R7: Zephyr reboot not working

Kent Hauser — Wed, 20 May 2026 01:30:50 GMT

Part Number: CC2652R7

I am trying to reboot my device (a CC2652R7 LaunchPad) after writing configuration data to flash. I use the standard zephyr command:

sys_reboot(SYS_REBOOT_WARM)

which (after locking IRQs) resolves on cortex-M to "NVIC_SystemReset()"

This doesn't work. The LaunchPad doesn't restart. Is there a better way (a driverLib fn) to reset board? Of all the things that could be blocking, I didn't expect this!

FWIW, I'm using an external jLink debugger instead of the onboard XDS110.

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
Other Parts Discussed in Thread: CC3300, CC3301, CC3351

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

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

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: Dual image OAD cannot jump to new image

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

Part Number: CC2745R10-Q1
Other Parts Discussed in Thread: UNIFLASH

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

CC2642R-Q1: EXT_EP-11975 (BLE_AGAMA-4810): Fix logic, and is there an application-level workaround without upgrading the SDK?

Chad Ou — Fri, 15 May 2026 10:20:11 GMT

Part Number: CC2642R-Q1
Other Parts Discussed in Thread: CC2642R

Body

Hi,

I am following up on JIRA ticket EXT_EP-11975 / BLE_AGAMA-4810:
"Connection param and channel map update callbacks are coming earlier than the actual instant where the change is reflected in the connection, causing CM instability."

The release notes of SimpleLink CC13xx/CC26xx SDK v8.32 state this issue is fixed, but the description is very brief.

My setup: CC2642R as the main BLE peripheral connected to a phone, with another CC2642R running a Connection Monitor (CM) following the same link.

Could you please clarify:

Fix logic — at the flow level, when is the application callback now raised relative to the actual instant of the parameter / channel map change? A short description of the new sequence would be enough.
Application-level workaround without upgrading — if I stay on the older SDK, is it possible to mitigate this purely from the application layer (e.g., delaying the forwarding of the callback to the CM device until the instant is reached)? If yes, what information is available to the application to determine the correct instant?

Thanks!

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
Other Parts Discussed in Thread: SYSCONFIG

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

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
Other Parts Discussed in Thread: LP-CC1352P7

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

CC2755P10: Step by Step how to measure RSSI in Smart RF Studio 8

Bailey Looper — Wed, 13 May 2026 22:32:46 GMT

Part Number: CC2755P10

Hello

Can you please provide a step by step guide on how to measure RSSI in Smart RF Studio 8? This tool lacks a guide overall and there are no testing guides available. My customer is looking to measure the RSSI in radiated method and are asking which client is used.

For example, can this be done using x1 LP or are x1 needed? What is reccomended to achieve the best performance, x1 or x2 launch pads?

I previously directed my customer to measeure RSSI by enabling the following

1. Continuous RX

2. Packet TX to Packet RX (RX side will show packet info and also the detected RSSI)

However that was not sufficient to conduct this measurement.

Thank you.

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

CC2642R: Clarification on CSP (Critical Security Parameter) Key Update Mechanism in CC2642R

Asao Makino — Wed, 13 May 2026 03:37:51 GMT

Part Number: CC2642R

Dear Texas Instruments Support Team,

I would like to request clarification regarding the security capabilities of the CC2642R SimpleLink™ MCU, specifically in relation to Critical Security Parameters (CSP), such as cryptographic keys.

Based on the official datasheet and available technical documentation, we understand that the CC2642R provides the following security-related features:

True Random Number Generator (TRNG)
Cryptographic accelerators (AES, ECC, SHA)
Secure key storage
Secure boot and debug protection

However, we could not find any explicit description of a hardware-based mechanism for automatic or periodic key update (key rotation) of CSPs.

Therefore, we would like to confirm the following points:

Does the CC2642R include any dedicated hardware mechanism that automatically or periodically updates cryptographic keys (CSPs), without software or protocol intervention?
If such a mechanism exists,
- Could you please provide the relevant documentation or reference describing it?
If such a mechanism does NOT exist,
- Is it correct to understand that key lifecycle management (including generation, update/rotation, and deletion of CSPs) is entirely handled by higher-level software, such as:
  - BLE stack procedures (e.g., re-pairing), or
  - Application-level implementations?
Additionally, regarding BLE operation:
- Is it correct that CSP updates (e.g., regeneration of LTK/IRK/CSRK) only occur during pairing or re-pairing procedures, and not during normal reconnection using existing bonding information?

Our goal is to accurately describe the security design in the context of compliance requirements (e.g., ISO/SAE 21434, FIPS-like concepts), and your clarification would be highly appreciated.

Thank you very much for your support.

Best regards,
Asao Makino

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

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

Part Number: WL1837MODCOM8I
Other Parts Discussed in Thread: AM3352

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

CC2745R10-Q1: Inquiry About BLE Channel Sounding Distance Measurement Drift

Jiahao Fan — Tue, 12 May 2026 10:04:43 GMT

Part Number: CC2745R10-Q1

Hello, TI support team

I am currently testing the Bluetooth Channel Sounding feature for distance measurement and have encountered an issue for which I would like to request technical support.

My current development environment is as follows:

SDK: SimpleLink Low Power F3 SDK v9.14.02.16
car_node:
- CC2745 LaunchPad
- Dual antenna configuration
key_node:
- CC2340R53 LaunchPad
- or a custom CC2340R53 hardware board

The observed behavior is described below:

When the key_node remains stationary, the continuously measured distance values are relatively stable with only small fluctuations.

For example:
- The initial measured distance is around 160
- Subsequent readings remain stable around this value
However, if the key_node is slightly moved and then placed back to the original position, the measured distance changes significantly, even though the physical position is nearly unchanged.

For example:
- The initial stable value is around 160
- After moving and placing it back, the stable value may become around 100
- The new readings are also stable, but with a noticeable offset from the previous value

Currently observed characteristics:

The readings are stable over short periods when stationary
After repositioning, the measurement settles to a different stable value
Even after returning the device to the original location, the measured distance does not recover to the previous value

I would like to ask the following questions:

Is this behavior considered normal for the current Channel Sounding implementation?
Are there any possible solutions or recommended debugging methods for this issue?

Thank you for your support.

Best regards,

Jiahao Fan.

CC2755P10: Can't scan TI referance board using TI SimpleLink at Andriod Phone.

JEONG H SEO — Mon, 11 May 2026 23:25:57 GMT

Part Number: CC2755P10

I am verfying to use CC2755P10 referance board.
However can't scan TI referance board using TI SimlpeLink in Phone.
How can setup to the referance board for the scan?
Note) 1. Board have SDK9.14.00 version.
2. I verifyied Tx Power using SmartRF Studio 8.

CC2340R5: host test example and RF studio comunication

Abinesh Rajendran — Mon, 11 May 2026 11:46:40 GMT

Part Number: CC2340R5

Hi Team,

I am using CCS IDE 12.8 with SDK version 8.40.

For RF certification testing, I am using the HostTest example project along with SmartRF Studio for communication and RF verification across different channels and PHYs.

My requirement is to:

Change BLE channels (37, 38, 39, etc.)
Change PHY settings
Perform modulated and unmodulated RF testing through UART HCI commands

I tried sending multiple HCI/UART command combinations to the HostTest firmware. Although UART communication is working and responses are received from the device, I am unable to observe a continuous/straight RF waveform on the receiver side in SmartRF Studio, similar to a connected continuous TX state.

Currently:

HCI Reset command is working correctly
Vendor-specific commands are responding
However, RF continuous TX/modem test does not seem to start successfully

Could you please suggest:

The correct UART HCI commands for continuous TX RF testing in HostTest
The proper command format for channel and PHY selection
Whether any additional configuration is required in SDK 8.40 or HostTest project settings
Recommended SmartRF Studio receiver configuration for verifying CW/modulated transmission

Please let us know how to proceed to achieve proper RF continuous TX testing for certification purposes.

Thanks & Regards,

Abinesh R

CC2652R7: Firmware working in debug mode, but when flashing the .bin directly it is not working

Arun T — Mon, 11 May 2026 06:20:59 GMT

Part Number: CC2652R7

Hi Team,

We are facing an issue with the CC2652R7 controller where the firmware works correctly during a debug session from CCS, but the controller does not boot when the same image is flashed and power-cycled/reset standalone.

Setup:

Controller: CC2652R7
IDE: CCS 20.4.0.13
Image contains both bootloader and application
Flashing method: JFlash Lite
Output format: Combined .bin

Observed behavior:

During debugger session:
1. Controller boots successfully
2. Application runs correctly
After flashing standalone:
1. The controller does not boot
2. No application activity observed

Additional observations:

The same binary behaves differently between debug and standalone mode. This issue is observed only in few controllers and not in all controllers.

Current implementation:

Custom bootloader + application
Application is jumped from bootloader
Combined image generated as single .bin

Any guidance or reference examples would be helpful.

CC2652R7: Sleep Mode and Wake-Up Issues

Nick Yao — Sat, 09 May 2026 01:15:10 GMT

Part Number: CC2652R7

Sleep Mode and Wake-Up Issues
I am currently developing a product using the CC2652R7. I am using SDK version simplelink_cc13xx_cc26xx_sdk_8_32_00_07.

The following is my main() function:

int main()
{
/* Register Application callback to trap asserts raised in the Stack */
RegisterAssertCback(AssertHandler);

Board_initGeneral();
PowerCC26X2_ResetReason resetReason = PowerCC26X2_getResetReason();
if (resetReason == PowerCC26X2_RESET_SHUTDOWN_IO) {
//Press the button to wake up the system; the program will run normally.
} else {
// Other cases (cold boot or manual reset) → Enter standby mode and wait for a button press to wake up
int i;
for(i=0; i<31; i++)
GPIO_setConfig(i, GPIO_CFG_INPUT | GPIO_CFG_IN_NOPULL);

GPIO_setConfig(6, GPIO_CFG_IN_PU | GPIO_CFG_IN_INT_FALLING);
GPIO_clearInt(6);
GPIO_enableInt(6);

//Shutdown
Power_shutdown(0, 0);
}

// Enable iCache prefetching
VIMSConfigure(VIMS_BASE, TRUE, TRUE);
// Enable cache
VIMSModeSet(VIMS_BASE, VIMS_MODE_ENABLED);

#if !defined( POWER_SAVING )
/* Set constraints for Standby, powerdown and idle mode */
// PowerCC26XX_SB_DISALLOW may be redundant
Power_setConstraint(PowerCC26XX_SB_DISALLOW);
Power_setConstraint(PowerCC26XX_IDLE_PD_DISALLOW);
#endif // POWER_SAVING

/* Update User Configuration of the stack */
user0Cfg.appServiceInfo->timerTickPeriod = Clock_tickPeriod;
user0Cfg.appServiceInfo->timerMaxMillisecond = ICall_getMaxMSecs();

/* Initialize ICall module */
ICall_init();

/* Start tasks of external images - Priority 5 */
ICall_createRemoteTasks();

#ifdef PTM_MODE
/* Start task for NPI task */
NPITask_createTask(ICALL_SERVICE_CLASS_BLE);
#endif // PTM_MODE
Myapp_createTask();
SimplePeripheral_createTask();

/* enable interrupts and start SYS/BIOS */
BIOS_start();

return 0;
}

My original intention was for the system to enter shutdown mode after power-on or a reset, and then wait for a button press to wake it up. I connected a 1000k pull-up resistor and a button to IO6; pressing the button grounds IO6.
The problem now is that with this configuration, IO6 cannot wake up the program. Is there something wrong with my code, and what is the correct way to implement this?

CC2745R10-Q1: Unable to Get Raw Data from BLE Agent in New CC2745 SDK (simplelink_lowpower_f3_sdk_9_20_00_8)

Pallavi Arage — Fri, 08 May 2026 12:13:08 GMT

Part Number: CC2745R10-Q1

Hi TI Support Team,

SDK Version: 9_20_00_81
Board Details: CC2745R10-Q1 LaunchPad
CCS Version: 20.5.0.28__1.11.0

I am currently evaluating the newly released SDK for the CC2745R10-Q1 LaunchPad using the Car Node and Key Node examples along with the BLE Agent Python tools provided in the SDK.

I have followed all requirements, setup steps, and configurations mentioned in the provided requirements text files for both the SDK examples and BLE Agent setup.

The procedure configuration and enable sequence appear to execute successfully. However, I am unable to receive the expected raw distance/ranging data from the BLE Agent.

Below is the observed console output during execution:

Procedure Enable successful
Waiting for NWP_CS_APP_DISTANCE_EXTENDED_RESULTS
Message received:
No NWP_CS_APP_DISTANCE_EXTENDED_RESULTS event received

The procedure repeatedly starts again, but no extended distance results or raw measurement data are received.

Could you please help clarify the following:

Are there any additional configurations required to enable extended/raw ranging results?
Has the event/data flow changed compared to previous SDK versions?
Are there any known limitations or additional steps required in the current SDK release for accessing raw ranging data?

Your guidance would be greatly appreciated.

Thank you.

CC2340R5: FaultISR on CC234R5

Sandeep Singh — Fri, 08 May 2026 07:25:17 GMT

Part Number: CC2340R5

Hi Team,

SDK used: 9_20_00_81

Chipset: CC2340R53

We have taken CC2340R5 's basis_ble example code as a base and have written a central based application on to it. The application for the most part runs smoothly without any issues but under certain random instances we see that the device goes into faultISR Handler.

I have checked the PC and LR as well but I am not able to extrpolate anything from it.

PC points to the while(1) present in the faultISR and LR contains a junk address.

Other than the above two registers, Can TI suggest what must we look at to figure out what the cause of the fault is? Unlike cortex M3 & M4 we do not have a various registers to isolate the cause of the fault.

Kindly help us understand how we can debug faultISR related issues.

Thanks and regards,

Sandeep

CC2745R10-Q1: How to perform CS range test

Jerry Kuo — Fri, 08 May 2026 01:25:23 GMT

Part Number: CC2745R10-Q1

Hi team,

Customer want to do Channel Sounding range test like below. They ask for any SOP or suggestion about how to do such test. Thank you.

CC2340R5: Custom Board Boot Issue: Program only runs after Debug Restart, not on Power-On Reset

bai zhang — Thu, 07 May 2026 09:30:29 GMT

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Body:

Dear TI Support Team,

I am working on a custom board using CC2340R52E0RGER and Code Composer Studio.

Issue Description:
My program does not execute when I simply power up the board (Power-On Reset). However, if I connect the debugger (e.g., XDS110), enter the Debug session, and click the "Restart" button within the Debug view, the program runs perfectly as expected.

My Question:
What is the fundamental difference between a Power-On Reset (POR) and the "Restart" command issued by the CCS debugger?
Specifically, why would the debugger's Restart cause the program to boot correctly, while a standard hardware power cycle does not?

Relevant Context:

MCU: CC2340R5
Debugger: XDS1110
CCS Version: 20.1.0.6
Custom Board: Four-layer PCB.

Could this be related to the Boot Mode pins (e.g., GPIO pins for boot mode selection) on my schematic? Is it possible that debugger's Restart bypasses the initial Boot ROM check, while the POR is getting stuck at a wrong boot mode (e.g., Wait Mode or SCI Boot)?

Thank you for your help.