TMS320F28001XX
The TI TMS320F28001XX are C2000 32-bit microcontrollers containing a TMS320C28x CPU.
Supported devices
Refer to the supported device list for a full list of all supported TMS320F28001XX family devices, their corresponding names and connection diagrams.
Target interfaces
| Interface | J-Link support | Flasher support |
|---|---|---|
| JTAG |  |
|
| cJTAG | |
|
Flash banks
| Flash bank | Base address | J-Link support | Flasher support | Loader | |
|---|---|---|---|---|---|
| Name | Bank size | ||||
| Flash0 | 0x00100000 (0x00080000)[1] | |
|
Default | 64 kB |
| DCSM_OTP0 | 0x000F0000 (0x00078000)[1] | |
|
Default | 2 kB |
¹ Base addresses are given as <byte oriented address> (<TMS320 word oriented word address>).
Limitations
DSCM OTP
Purpose of the DCSM OTP
The TMS320F2800132 microcontroller from Texas Instruments (TI) includes a Dual Code Security Module (DCSM) to protect application software and sensitive data against unauthorized access, copying, and reverse engineering.
The DCSM uses One-Time Programmable (OTP) memory to permanently store security-related configuration data. This includes security settings, password information, and configuration pointers for the two independent security zones (Zone 1 and Zone 2).
Each zone has its own 128-bit security password and can protect allocated Flash sectors, RAM blocks, and other secure resources.
The DCSM OTP also provides important device-level security features:
JTAGLOCK: Disables JTAG debugging access to protected device resources. Zero-Pin Boot: Prevents the use of external pin-based bootloader interfaces when configured together with Flash Boot. Dual-Zone Security: Allows memory and software resources to be assigned to separate security zones.
The main objective is to ensure that proprietary firmware and sensitive application data cannot easily be accessed or extracted by unauthorized parties.
Important Considerations When Programming the OTP
Programming the DCSM OTP requires special care because OTP memory is designed for permanent configuration.
The following points should be considered:
Irreversible programming: OTP settings cannot simply be erased or restored to their original state. Incorrect programming can permanently affect device functionality or accessibility. Password management: Security passwords must be generated, documented, and stored securely. Losing the passwords can result in permanently losing access to protected resources. Link pointer configuration: The DCSM uses zone-specific link pointers to identify the active security configuration in OTP. These pointers must be configured correctly. JTAG access: Enabling JTAGLOCK can permanently disable normal debugging access. Therefore, this feature should only be activated after successful software validation. Boot configuration: Zero-Pin Boot must be configured carefully to ensure that the intended firmware update and recovery mechanisms remain available. Testing before production: All security configurations should first be tested on dedicated development devices before being applied to production hardware.
It is strongly recommended to verify all OTP values and the complete security configuration before starting the programming process.
Conclusion
The DCSM OTP is an essential security feature of the TMS320F2800132. It provides mechanisms to protect firmware, restrict debugging access, and prevent unauthorized access to internal memory.
However, since OTP programming is permanent, incorrect configuration can lead to significant problems during development, debugging, or production.
Therefore, the DCSM OTP should only be programmed after the complete security concept has been defined, reviewed, and successfully tested.
Write size
Due to the ECC of the OTP cells, The data is written in portions of 128 Bit => 16 Byte => 8 Words and are aligned on 128 Bit boundaries.