TI CC2745

Flash Banks

The TI CC2745 series does not provide a sector erase command but a chip erase command which affects the program flash, HSM flash, CCFG flash and SCFG flash. Unfortunately, the debug interface is not open in case of an invalid CCFG block is detected which is the case after erasing it. For that reasons, it's mandatory to always program the application + a valid CCFG block when updating the target application. The flash interface provides an option called retainSelMainSectors which can be used to prevent specific sectors from being affected by the erase chip command. This can be really useful when working with a HSM firmware which is located in the program flash. The retainSelMainSectors sectors is enabled by default.

CC2745R10 PG2.0

Flash Bank	Base address	J-Link Support	Loader
			Name	Size
Program flash	0x00000000		Default	928 KB
HSM flash	0x000E8000		Default	96 KB
CCFG flash	0x00000000		Default	2 KB
SCFG flash	0x00000000		Default	1 KB

CC2745R7 PG2.0

Flash Bank	Base address	J-Link Support	Loader
			Name	Size
Program flash	0x00000000		Default	768 KB
HSM flash	0x000E8000		Default	96 KB
CCFG flash	0x00000000		Default	2 KB
SCFG flash	0x00000000		Default	1 KB

Debug Authentication

The TI CC274x device family implements a secure Debug Authentication mechanism designed to prevent unauthorized access to the device’s debug interface. This mechanism is part of Texas Instruments’ security architecture and ensures that only authenticated tools or users can gain debug privileges. Debug access on CC274x devices is protected by a challenge–response–based authentication flow. When debug authentication is initiated, the device generates a challenge vector that must be signed externally. The signed response is then submitted back to the device to unlock the debug interface.

SEGGER’s tools support this authentication workflow through the Device Provisioner infrastructure and dedicated J-Link functionality.

Debug Authentication via SEGGER Device Provisioner

SEGGER provides support for CC274x Debug Authentication through the SEGGER Device Provisioner. This includes:

• Starting the Debug Authentication process
• Retrieving the challenge vector
• Submitting the signed response
• Handling all communication required by the CC274x authentication protocol

However, the Debug Authentication functionality for the TI CC274x is not included by default.

Availability

The CC274x Debug Authentication features are available only upon request. Customers requiring access must contact SEGGER to have this feature enabled.

The corresponding script file is provided for a fee. Pricing is available upon request.

For more information, please contact us via the following link: https://www.segger.com/about-us/contact-us/

Usage with J-Link

J-Link provides command-line and script-based support for CC274x Debug Authentication, including:

• Debug authentication for all three security levels: SECURE, NON-SECURE, and NON-INVASIVE
• Support for all encryption mechanisms, as signing must be performed by an external tool (for example: openssl)
• No private keys need to be embedded into SEGGER tools for the process
• Full automation support, allowing integration into development and production workflows

More detailed documentation and examples will be provided upon request.

Device Specific Handling

Connect

A device specific connect sequence is executed which supports:

• Connecting to a device with invalid configuration (e.g. CCFG, SCFG or program flash empty). In this case, a default configuration will be programmed as part of the connect.
• Connecting to a device with valid configuration (CCFG, SCFG and program flash are flash).

As part of the connect sequence, the J-Link determines the silicon revision

Reset

The device uses custom reset which performs a reset via the SACI interface:

• In case of a valid application is programmed, the MCU will be halted on the reset vector (application entry point).
• In case of no valid application is programmed, the MCU will be halted in a so called debug loop

Limitations

Attach

Attach is supported by the J-Link if not excluded by the current CCFG (e.g. debug disabled after POR / authentication enabled).

Flash Breakpoints

Not supported because re-programming specific sectors is not possible (technical limitation of the device)