Bluetooth forum - Recent Threads

CC2340R5: PAwR (Periodic Advertising with Responses) and EAD (Encrypted Advertising Data)

O.H — Fri, 17 Apr 2026 00:58:37 GMT

Part Number: CC2340R5

Hi experts,

Could you please confirm whether the SDK for CC2340, “SIMPLELINK-LOWPOWER-F3-SDK,” supports PAwR (Periodic Advertising with Responses) and EAD (Encrypted Advertising Data)?

If not, are there any plans to support them in the future?

I could not find any mention of these features in the sample projects or in the BLE5-Stack User’s Guide, so I would appreciate your confirmation.

Best regards,
O.H

CC2340R5: Getting HAL_ASSERT_CAUSE_HW_ERROR Cause and HAL_ASSERT_CRYPTO_INIT_ERROR Subcause During vTaskStartScheduler

Alexander Trujillo — Thu, 16 Apr 2026 15:01:24 GMT

Part Number: CC2340R5
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I am working on porting my BLE application from version v8.20.00.119 to v9.14.02.16 for the CC2340R53. The project is RTOS is FreeRTOS. It seems that when it tries to start the task scheduler, I get a stack assert with the cause HAL_ASSERT_CAUSE_HW_ERROR (3) and the subcause HAL_ASSERT_CRYPTO_INIT_ERROR (3). I noticed in the porting guides that there were some changes to the crypto drivers.
I've made sure to add secure_drivers_cc23x0r5.a to my linker libraries path. I am wondering if there are any other obvious things that I would be missing regarding the changes to the drivers.

I am not using a CCStudio-based build system so unfortunately any automatic porting that can be done via CCStudio would not work.

Let me know if there is any information that I can provide to debug this issue. Also, if there is any documentation that I likely haven't seen on this please share a link!

Thanks,
Alex Trujillo

CC2340R5: Basic BLE standby

William Cullen — Wed, 15 Apr 2026 23:15:43 GMT

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG, ENERGYTRACE

I have product firmware that uses pretty much everything on this chip. Timers, SPI, I2C, UART etc. I would like to take the MCU in and out of standby based on a bluetooth message. The message is properly received into an application task that has its own event loop. The task handles all the buses and data flow, so the handler is in this context. The handler sets a semaphore and waits on it to suspend the app task and ideally puts the chip in standby. It does not work now but rather continues to run normally with BLE advertising and such.

To start with something simple, what modifications to the Basic BLE example would need to be made to have it enter standby, say maybe on a button press? I have added the policy function setting standby in sysconfig and added the predifined symbol POWER_SAVING to the project based on some things I've read. Is there a list of items to set/change I can follow?

With two event loops, I can imagine things are more complicated. How do I handle the Blutooth task?

Thanks,

Bill

CC2340R2: TI CC2340 controllers ROM bootloader is capable to verifying the application signature

srinivasa rao veeravalli — Wed, 15 Apr 2026 14:22:06 GMT

Part Number: CC2340R2
Other Parts Discussed in Thread: CC2340R5

we looking for a secure boot support for one of us project, Is TI CC2340 controllers ROM bootloader is capable to verifying the application signature and jump to application when verification got succeed.

CC2745R10-Q1: CC2745R10-Q1 App_StackInitDoneHandler not triggered on custom board

YOU AlanWS — Wed, 15 Apr 2026 08:06:55 GMT

Part Number: CC2745R10-Q1

Hi team,

I am running a BLE example (car_node) with SimpleLink SDK (v9.14.02.16).

On EVK board → works correctly
On custom board → App_StackInitDoneHandler was not triggered.

Observation

BLEAppUtil_init() is called
BLEAppUtil_createStackTasks() returns successfully
BLEAppUtil task is running
But App_StackInitDoneHandler() is never reached

Questions

What could cause App_StackInitDoneHandler not to be triggered?

CC2642R: How can I obtain the LTK in the CC2642 simplelink_cc13xx_cc26xx_sdk_5_40_00_40 SDK

zhijie lin — Wed, 15 Apr 2026 05:36:08 GMT

Part Number: CC2642R

How can I obtain the LTK in the CC2642 simplelink_cc13xx_cc26xx_sdk_5_40_00_40 SDK?

CC2340R5: Getting "conflicting types for 'icall_directAPI'" error while attempting to port application from simplelink f3 sdk v8.20.00.119 to v9.14.02.16

Alexander Trujillo — Tue, 14 Apr 2026 16:08:32 GMT

Part Number: CC2340R5
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I was wondering if someone could provide some insight to this problem I am having while porting over my application for the CC2340R53 mcu from version v8.20.00.119 to version v9.14.02.16 of the simplelink f3 lowpower sdk.

I keep getting this error that looks to be a conflicting macro with the same name as a function. In ble_dispatch_lite.h, the function buildRevision is declared as:

extern uint8 buildRevision(ICall_BuildRevision *pBuildRev);

(and is defined in ble_dispatch_lite.c)

However, it seems that from my build error, the declaration in ble_dispatch_lite.h is getting expanded to the macro declared in icall_ble_api.h:

#define buildRevision(...)       (icall_directAPI((uint32_t) IDX_buildRevision , ##__VA_ARGS__))

When building, it gives this error message:

submodules/simplelink-lowpower-f3-sdk/source/ti/ble/stack_util/icall/stack/ble_dispatch_lite.h:141:42: error: expected ')'
  141 | extern uint8 (icall_directAPI((uint32_t) buildRevision ,ICall_BuildRevision *pBuildRev));
      |                                          ^
submodules/simplelink-lowpower-f3-sdk/source/ti/ble/stack_util/icall/stack/ble_dispatch_lite.h:141:30: note: to match this '('
  141 | extern uint8 (icall_directAPI((uint32_t) buildRevision ,ICall_BuildRevision *pBuildRev));
      |                              ^
submodules/simplelink-lowpower-f3-sdk/source/ti/ble/stack_util/icall/stack/ble_dispatch_lite.h:141:15: error: conflicting types for 'icall_directAPI'
  141 | extern uint8 (icall_directAPI((uint32_t) buildRevision ,ICall_BuildRevision *pBuildRev));
      |               ^
submodules/simplelink-lowpower-f3-sdk/source/ti/ble/stack_util/icall/app/icall.h:1097:10: note: previous declaration is here
 1097 | uint32_t icall_directAPI(icall_lite_id_t id, ... );
      |          ^
2 errors generated.

From this error, it looks like buildRevision is being erroneously expanded to (icall_directAPI((uint32_t) IDX_buildRevision , ##__VA_ARGS__)).

For most of the naming changes and stuff, I have used this guide as a reference: https://software-dl.ti.com/simplelink/esd/simplelink_lowpower_f3_sdk/9.14.01.16/exports/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/porting-guides/cc23xx/CC23XX_SDK_8.40_to_9.10.html
However, we are not developing with CCStudio anymore and have changed over to a custom Makefile based build for the project, so CCStudio-based solutions would not work for this specific issue.

Let me know if there is any other information I can provide to help with this issue!

Thanks,
Alex Trujillo

CC2640R2F: CC2640R2F ADC Gain Error Anomaly After 85°C/90% RH Reliability Test (Single Unit)

Mike Wu1 — Tue, 14 Apr 2026 10:08:51 GMT

Part Number: CC2640R2F

Dear TI Team, (or replace with the specific AE's name)

We have a customer utilizing the CC2640R2F in their end product (a battery tester). During their recent product reliability testing, they observed an anomaly regarding the ADC reading accuracy. We are reaching out to seek your technical support and recommendations on this issue.

Below is a summary of the system background and the observed anomaly:

[System Background & Application]

End Application: Battery tester. The CC2640R2F ADC is used to measure external battery voltage (measurement range: 4V to 31V).
Hardware/Software Architecture: The hardware utilizes a voltage divider network and an operational amplifier (OPA) to step down the high voltage to an ADC-acceptable range. On the software side, initial calibrations have been implemented to compensate for hardware component tolerances (e.g., resistor variations, OPA offset errors), ensuring that the accuracy meets product specifications at room temperature.

[Anomaly Description]

Test Conditions: High Temperature/High Humidity (Damp Heat) at 85°C / 90% RH. Measurements were taken after the units returned to room temperature.
Sample Size: 5 prototype units (each containing one CC2640R2F).
Observed Issue:
- After returning to room temperature, 4 out of the 5 units maintained ADC measurement accuracy within specifications.
- However, 1 unit exhibited a significant error amplification.
- Characteristics: For voltages below 14V, the accuracy remains within spec. However, for voltages above 14V, the error exceeds the specification, and the error increases proportionally as the measured voltage gets higher. This behavior strongly resembles an ADC Gain Error or a drift in the internal Reference Voltage (Vref).

[Assistance Required from TI]

We would greatly appreciate it if you could help evaluate this phenomenon and provide further analysis and debugging recommendations. Your guidance will be highly valuable for us to assist the customer in resolving this issue.

Thank you very much for your support!

Best Regards,

Mike1

CC2650STK: Humidity data not displaying and TMP007 "not mounted" error on CC2650 SensorTag

Swallow Tsai — Tue, 14 Apr 2026 02:38:28 GMT

Part Number: CC2650STK
Other Parts Discussed in Thread: CC2650, , HDC1000

Hi Team,

I am experiencing an issue with my CC2650 SensorTag where the humidity data fails to display in the App. It consistently shows --%rH or 0, and the graph remains empty even after enabling the sensor in the configuration menu.

Additionally, I noticed a recurring error message at the top of the screen: "TMP007 Sensor not mounted."

Here are the details of my setup:

Device: CC2650STK SensorTag
App: TI SensorTag App (iOS/Android)
Observed Symptoms: 1. Toggling the Humidity sensor "ON" in "Configure Sensor" does not trigger any data reading. 2. The IR Temperature (TMP007) is reported as "not mounted." 3. Other sensors (like Barometer/Movement) seem to be functioning, but the environmental sensors (Temp/Humidity) are unresponsive.

Steps I have already tried:

Replaced the CR2032 battery with a brand new one to ensure full power.
Adjusted the reporting interval (from 0.5s to 2.5s) to see if it triggers a response.
Restarted the App and re-paired the Bluetooth connection multiple times.

Could this be a hardware failure related to the I2C bus, given that both the TMP007 and the humidity sensor (HDC1000) are failing? Or is there a specific firmware update/reset procedure I should follow?

Any guidance would be greatly appreciated. Thanks!

CC2340R2: 32kHz Internal Oscillator Accuracy

Luke — Mon, 13 Apr 2026 20:50:30 GMT

Part Number: CC2340R2

Hi,

Following up on the related thread, customer has done some preliminary testing of the LF internal oscillator accuracy. As we understand it, the accuracy at 25°C should be 500 ppm.

Their results are nowhere near that accurate. For this testing, the FW selects the LFOSC and outputs it on DIO12. Near 25°C, they see frequencies of approximtely 32.601kHz, 32.970kHz, 32.688kHz. These are thousands of ppm off.

At higher and lower temperatures, they do see the expected drift, well under 600 ppm/C.

Their questions are:

Do you have any comment on the magnitude of the inaccuracy at 25°C?
I doubt that the frequency I am measuring includes any correction factor. Is there a way for me to measure the internal oscillator with the correction factor applied? Or somehow determine what the correction factor is?

Best,
Luke

CC2642R: Regarding the issue of slow RSSI acquisition on CC2642

junjie Deng — Mon, 13 Apr 2026 10:17:49 GMT

Part Number: CC2642R

Dear TI Official Engineers,

We are using the **simple_peripheral** example project for the CC2642R chip and need to obtain the RSSI value of the connected device.
Our current implementation creates a timer to call `HCI_ReadRssiCmd(connHandle)` every 50ms, and then retrieves the RSSI value afterward.

However, the RSSI update rate is very slow – we only get a new reading approximately every 300ms.

Is there any way to increase the frequency of RSSI readings?
Looking forward to your reply.
Sincerely
Deng Junjie

CC2745R10-Q1: How to add commands to BTool

Yasukane Yamanaka — Mon, 13 Apr 2026 09:59:34 GMT

Part Number: CC2745R10-Q1

We are using “SimpleLink Low Power SDK ver.9.14.00.”

With “BTool” included in this SDK, it is possible to use HCI commands, but is it possible to add commands?

If possible, we would like to add both commands specified by the Bluetooth SIG and vendor-specific commands.

Best regards

CC2745R10-Q1: CC2745 Not connecting with SmartRF 8

Muhsin Ali — Mon, 13 Apr 2026 09:56:56 GMT

Part Number: CC2745R10-Q1

Hello,

I am using LP-CC2625RB to connect with CC2745R10 for some RF testing. While connecting SWD pins and Uart TX & RX i am not able to detect and connect CC2745 with SmartRF 8. Kindly provide guidance for the same.

Regards,

Muhsin Ali

CC2642R-Q1: CC2642 can't pass CVE bug detection tool

Island Wei — Mon, 13 Apr 2026 02:41:22 GMT

Part Number: CC2642R-Q1

Hi team,

My customer find CC2642 cannot pass these 3 test case in CVE test.

The SDK version is 5.40, do you know whether it's SW related or HW limitation?

https://nvd.nist.gov/vuln/detail/CVE-2019-19193

https://nvd.nist.gov/vuln/detail/CVE-2020-10069

https://nvd.nist.gov/vuln/detail/CVE-2020-13594

CC2745R10-Q1: Channel Sounding – Range computation, on-chip feasibility, and BLE concurrency

Vaibhav Patil — Fri, 10 Apr 2026 10:06:55 GMT

Part Number: CC2745R10-Q1

Hi team,

SDK: 9.140.1.16
Target: CC2745R10

I am working with the channel sounding example:
car_node_LP_EM_CC2745R10_Q1_freeRTOS_ticlang

I have a few specific questions:

1. Range Computation

In this example, where is the range (distance) computation actually performed?
Is the CC2745R10 only sending raw channel sounding data to the host (Python), with all processing done there?
If yes, which part of the firmware is responsible for exporting this raw data?

2. On-Chip Range Computation

Is it feasible to implement distance estimation directly on the CC2745R10 instead of relying on the host?
Are there any constraints in terms of CPU load, memory, or timing when attempting this?
Any recommended approach or reference for doing this on-chip?

3. Channel Sounding + BLE Concurrency

Can the initiator perform channel sounding while also handling normal BLE activities (e.g., connection events, GATT, advertising)?
If supported, how is this managed internally:
- Is there a scheduler/arbitration mechanism between CS and standard BLE?
- Are there known limitations on throughput, latency, or timing?

Any pointers to relevant documentation or architectural details would be helpful.

Thanks
Vaibhav

CC2745R10-Q1: Questions about OAD dual image project

Weiting Liao — Fri, 10 Apr 2026 09:24:05 GMT

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

Hi TI support team,

I am currently working on implementing the OAD feature using the SDK example basic_ble_oad_dual_image and performing OAD via the SimpleLink Connect mobile app.

I completed the OAD process successfully using the app. After that, I checked the flash content using UniFlash.

However, I observed that the secondary slot does not contain the expected image data. Instead, the image appears to be located at flash address 0x72000, while my configured secondary slot address is 0x38000.

Flash address 0x72000

Below are my configurations:
SysConfig settings for the secondary slot

NVS settings

I have the following questions:
1.Why is the image stored at flash address 0x72000 instead of 0x38000?
2.What is the purpose of CONFIG_NVSINTERNAL1 in the NVS configuration?

Could you please provide guidance on this behavior and advise how to correctly configure and verify the OAD process?

Thank you for your support.

Best regards,
WT

CC2745R10-Q1: Dual antenna RSSI measurement WITHOUT Channel Sounding via Phone

Ra B — Thu, 09 Apr 2026 12:20:19 GMT

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

Hi Team,

We want to measure RSSI independently on two antennas
(using antenna switching / diversity) without enabling
Channel Sounding (CS) procedures via Phone

Platform details
Device: CC2745R10-Q1 (CC27xx)
SDK version:
simplelink_lowpower_f3_sdk_9_14_02_16
Toolchain: CCS / FreeRTOS
project used: car_node

configuration:

- Enabled dual antenna configuration in SysConfig
- Observed antenna not switching via GPIO
- Using normal BLE connection ( CS enabled) in my phone, where channel sounding not supported. checked Pin21 able to see waveform before connection but once its connected to the phone no waveform observed just noise
- Able to read RSSI Connect in Single antenna

. Is it possible to get per-antenna RSSI measurements
(antenna 1 vs antenna 2) without enabling Channel Sounding?

2. Does the BLE stack support antenna diversity RSSI reporting?

3. Is there any API or RF command that allows reading RSSI
for each antenna independently?

4. If not, is Channel Sounding mandatory for dual antenna usage?

LP-EM-CC2745R10-Q1: Zephyr ble mesh shell

Munan Xu — Wed, 08 Apr 2026 13:42:27 GMT

Part Number: LP-EM-CC2745R10-Q1
Other Parts Discussed in Thread: CC2745R10-Q1

Hello,

Has anyone ever tried running the bluetooth mesh shell test in zephyr? I'd like to use this to debug a ble mesh application/ friendship establishment with an existing product since it doesn't require me to rebuild the application every time I want to change a behvior, and it allows for more flexibility in configuration.

When I flash and run the test it immediately crashes before getting to any kind of print or terminal.

In the build process for this project it does warn about some configurations that are expected to be enabled but I thought you would at least get to a prompt since the bluetooth stack does not get configured until you bring it up in the shell.

warning: BT_CTLR_DUP_FILTER_LEN (defined at subsys/bluetooth/controller/Kconfig:170) was assigned
the value '0' but got the value ''. Check these unsatisfied dependencies: BT_LL_SW_SPLIT (=n),
BT_CTLR (=n). See docs.zephyrproject.org/.../kconfig.html
and/or look up BT_CTLR_DUP_FILTER_LEN in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.


warning: BT_CTLR_ADVANCED_FEATURES (defined at subsys/bluetooth/controller/Kconfig.ll_sw_split:281)
was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
BT_LL_SW_SPLIT (=n), BT_CTLR (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_ADVANCED_FEATURES in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

Also I had to add

CONFIG_BT_LONG_WQ=y

to the prj.conf since otherwise the project would not build at all.

Originally I tried this on LP_EM_CC2340R53, but had to cut down the stack sizes way down to even get the linker to make everything fit on the device. It also immediately crashes, so I thought maybe it was a stack overflow thing and moved to the LP_EM_CC2745R10-Q1 as a higher memory option but no dice apparently.

Munan

CC2640R2F: Need RED compliance certificate

jitendra rana — Wed, 08 Apr 2026 08:50:27 GMT

Part Number: CC2640R2F

Hi Guys, Please provide RED compliance certificate for

CC2640R2F

Thanks

Jitendra

Secure meters

CC2642R: Is there a way to determine whether the output values are appropriate for the parameters set in the PA table?

Bunta Horino — Wed, 08 Apr 2026 08:11:23 GMT

Part Number: CC2642R

When the IB of PA table “{5, RF_TxPowerTable_DEFAULT_PA_ENTRY(23, 0, 0, 57)}” is set to 13, 23, or 33, it has been confirmed that the device operates at the following output values
IB 13: -6 dBm
IB 23: -3 dBm
IB 33: -1.5 dBm
Is there a way to determine whether each output value is appropriate for the configured parameters?

CC2340R5: OAD update using IOS custom App

Abinesh Rajendran — Wed, 08 Apr 2026 05:38:21 GMT

Part Number: CC2340R5

Hi team

We are using the CC2340R5 and developing a custom FOTA (Firmware Over-The-Air)IOS application.

Currently, we are facing an issue. We have flashed MCUboot, basic persistent, and basic BLE OAD images onto the device.

On iOS, we successfully connect to the application layer and send 0x01 to the FFD0 service, after which the device transitions to the persistent layer. However, after reconnecting, we are still able to see only the application layer services. We are not able to find the FFC0 OAD service, which is required for uploading the firmware.

Could you please suggest how to resolve this issue?

Thanks and regards

chandra shekar

CC2340R5-Q1: How to generate a single precise low pulse using LGPTimer

hrkunied — Wed, 08 Apr 2026 04:51:37 GMT

Part Number: CC2340R5-Q1

Hello TI team,

We are using SDK 9.14. What we want to do is output a single low pulse with a strictly controlled duration. From our investigation the LGPTimer driver appears capable of this, and we implemented and tested code accordingly. However, when we call LGPTimerLPF3_open() the port level unexpectedly changes from High to Low immediately.

I will attach the code we used. Could you please advise the correct way to generate a single precise low pulse with LGPTimer and explain why the port level goes H→L when calling LGPTimerLPF3_open()? Any guidance would be greatly appreciated.

	/* Initial GPIO.output = H */



    LGPTimerLPF3_Params lp_lgpt0_params;

    // Configure LGPTimer
    LGPTimerLPF3_Params_init(&lp_lgpt0_params);
    lp_lgpt0_params.prescalerDiv = 0;

    // Configure channel 2 action (Count=0[GPIO:L] → Count=4800[GPIO:H])
    lp_lgpt0_params.channelProperty[1].action = LGPTimerLPF3_CH_CLR_ON_0_TOGGLE_ON_COMPARE_ONCE;

    // Open driver (GPIO.output = H → L)
    gh_lgpt0_handle = LGPTimerLPF3_open(CONFIG_LGPTIMER_0, &lp_lgpt0_params);

    // GPIO.output = L → H
    LGPTimerLPF3_setChannelOutputLevel(gh_lgpt0_handle, LGPTimerLPF3_CH_NO_1, LGPT_OUTCTL_SETOUT0);

    // Set channel CounterTarget (no use)
    LGPTimerLPF3_setInitialCounterTarget(gh_lgpt0_handle, 4801, false);

     // Set channel CompVal (GPIO.output "L" Time (100us)) */
    LGPTimerLPF3_setInitialChannelCompVal(gh_lgpt0_handle, LGPTimerLPF3_CH_NO_1, 4800, false);

    // Start  the LGPTimer in up once mode
    LGPTimerLPF3_start(gh_lgpt0_handle, LGPTimerLPF3_CTL_MODE_UP_ONCE);

Thank you for your help.

CC2340R5: CC2340R5: How to configure UART TX pin to a different I/O other than XDS110 UART (resource conflict)?

bai zhang — Tue, 07 Apr 2026 08:12:59 GMT

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Hi TI support team,

I am using the UART2 driver in my project (TI SimpleLink SDK) and have encountered a configuration issue regarding the TX pin assignment.

In my .syscfg file, I have the following UART2 settings:

UART Peripheral: CONFIG_UART2_1
Use Hardware: None
Enable Nonblocking Mode: Enabled
Data Direction: Send Only
Flow Control: Disabled
Interrupt Priority: 3 (Lowest)
RX Ring Buffer Size: 32
TX Ring Buffer Size: Any

Under PinMux configuration, the TX Pin dropdown shows several options, including:

DIO6/38 (MX25R8035F SPI Flash Chip Select)
DIO13/15 (LaunchPad SPI Bus)
DIO18/7 (LaunchPad SPI Bus)
DIO20/4 (XDS110 UART) ← currently selected
DIO4_X32N/27 (Device Only)
DIO17_SWDCK/12 (Device Only)

The currently selected pin DIO20/4 (XDS110 UART) shows a "Resource conflict" warning, likely because this pin is already used by the on-board XDS110 debugger for UART communication.

I would like to configure the UART TX pin to a different I/O that is not the XDS110 UART pin – for example, DIO13/15 or DIO18/7 (both marked as "LaunchPad SPI Bus"). However, I am not sure how to properly select and assign these alternative pins without causing additional conflicts or breaking the SPI bus functionality.

My questions are:

How can I change the UART TX pin to one of the other available DIOs (e.g., DIO13/15) in SysConfig?
Will selecting a pin that is also used by the LaunchPad SPI bus (e.g., DIO13/15 or DIO18/7) cause a hardware conflict if SPI is not used?
Is there a recommended way to free up the XDS110 UART pin and avoid the resource conflict while still using UART2 in send-only mode?

Thank you for your help.

CC2340R5: How to enable flash protection for MCUBoot area in CCFG

yao zhang — Tue, 07 Apr 2026 07:26:33 GMT

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I would like to enable write protection in CCFG for range 0x0 to 0x6000, the address MCUboot is programmed. This will make sure MCUboot work as root of trust.

Below is screenshot I changed in syscfg. But seems I can still programme this area by Jflash.

Please help to check it. Thanks.

CC2745P10-Q1: KeyStore Flash Address Offset error after SysConfig update

Takuya Tanigawa — Tue, 07 Apr 2026 06:43:22 GMT

Part Number: CC2745P10-Q1
Other Parts Discussed in Thread: SYSCONFIG

I'm trying to update from SDK simplelink_lowpower_f3_sdk_9_10_00_83 to simplelink_lowpower_f3_sdk_9_14_02_16.
SysConfig has also been updated from version 1.23.1 to 1.23.2, and I have confirmed that two new settings have been added to PSA Crypt + KeyStore.

When I opened SysConfig in version 1.23.2, "KeyStore Flash Address Offset" was set to 0xE6000, and building with this setting resulted in an error.
"The configured KeyStore flash region goes beyond the accessible flash addresses on the device."

I have a question about "KeyStore Flash Address Offset" setting.
If the ITS area is set to 32KB starting at 0x000E0000, and the KeyStore Flash Size is set to 10KB, where will the KeyStore area be placed in SDK 9.10?
Also, if I want to maintain the same map as 9.10 after updating to 9.14, what value should I set for "KeyStore Flash Address Offset"?