Datasheet

194

TMS320F28379S

TMS320F28377S

TMS320F28376S, TMS320F28375S, TMS320F28374S

SPRS881C –AUGUST 2014–REVISED MAY 2016

www.ti.com

Submit Documentation Feedback

Product Folder Links: TMS320F28379S TMS320F28377S TMS320F28376S TMS320F28375S TMS320F28374S

6.9.1 EMU Boot or Emulation Boot

The CPU enters this boot when it detects that TRST is HIGH (in other words, when an emulator/debugger

is connected). In this mode, the user can program the EMUBOOTCTRL register (at location 0xD00) to

instruct the device on how to boot. If the contents of the EMUBOOTCTRL locations are invalid, then the

device would default into WAIT Boot mode. The emulation boot allows users to verify the device boot

before programming the boot mode into OTP.

6.9.2 WAIT Boot Mode

The device in this boot mode loops in the boot ROM. This mode is useful if users want to connect a

debugger on a secure device or if users do not want the device to execute an application in flash yet.

6.9.3 Get Mode

The default behavior of Get mode is boot-to-flash. This behavior can be changed by programming the Zx-

OTPBOOTCTRL locations in user configurable DCSM OTP. The user configurable DCSM OTP on this

device is divided in to two secure zones: Z1 and Z2. The Get mode function in boot ROM first checks if a

valid OTPBOOTCTRL value is programmed in Z1. If the answer is yes, then the device boots as per the

Z1-OTPBOOTCTRL location. The Z2-OTPBOOTCTRL location is read and decodes only if Z1-

OTPBOOTCTRL is invalid or not programmed. If either Zx-OTPBOOTCTRL location is not programmed,

then the device defaults to factory default operation, which is to use factory default boot mode pins to boot

to flash if the boot mode pins are set to GET MODE. Users can choose the device through which to

boot—SPI, I2C, CAN, and USB—by programming proper values into the user configurable DCSM OTP.

More details on this can be found in the TMS320F2837xS Delfino Microcontrollers Technical Reference

Manual.