Datasheet

TMS320F28030, TMS320F28031, TMS320F28032

TMS320F28033, TMS320F28034, TMS320F28035

SPRS584J –APRIL 2009–REVISED OCTOBER 2013

www.ti.com

3.2.9.3 Peripheral Pins Used by the Bootloader

Table 3-7 shows which GPIO pins are used by each peripheral bootloader. Refer to the GPIO mux table

to see if these conflict with any of the peripherals you would like to use in your application.

Table 3-7. Peripheral Bootload Pins

BOOTLOADER PERIPHERAL LOADER PINS

SCI SCIRXDA (GPIO28)

SCITXDA (GPIO29)

Parallel Boot Data (GPIO31,30,5:0)

28x Control (AIO6)

Host Control (AIO12)

SPI SPISIMOA (GPIO16)

SPISOMIA (GPIO17)

SPICLKA (GPIO18)

SPISTEA (GPIO19)

C SDAA (GPIO32)

SCLA (GPIO33)

CAN CANRXA (GPIO30)

CANTXA (GPIO31)

3.2.10 Security

The devices support high levels of security to protect the user firmware from being reverse engineered.

The security features a 128-bit password (hardcoded for 16 wait-states), which the user programs into the

flash. One code security module (CSM) is used to protect the flash/OTP and the L0/L1 SARAM blocks.

The security feature prevents unauthorized users from examining the memory contents via the JTAG port,

executing code from external memory or trying to boot-load some undesirable software that would export

the secure memory contents. To enable access to the secure blocks, the user must write the correct 128-

bit KEY value that matches the value stored in the password locations within the Flash.

In addition to the CSM, the emulation code security logic (ECSL) has been implemented to prevent

unauthorized users from stepping through secure code. Any code or data access to CSM secure memory

while the emulator is connected will trip the ECSL and break the emulation connection. To allow emulation

of secure code, while maintaining the CSM protection against secure memory reads, the user must write

the correct value into the lower 64 bits of the KEY register, which matches the value stored in the lower 64

bits of the password locations within the flash. Note that dummy reads of all 128 bits of the password in

the flash must still be performed. If the lower 64 bits of the password locations are all ones

(unprogrammed), then the KEY value does not need to match.

When initially debugging a device with the password locations in flash programmed (that is, secured), the

CPU will start running and may execute an instruction that performs an access to a protected ECSL area.

If this happens, the ECSL will trip and cause the emulator connection to be cut.

Submit Documentation Feedback

Product Folder Links: TMS320F28030 TMS320F28031 TMS320F28032 TMS320F28033 TMS320F28034

TMS320F28035