TMS570LS0714 16- and 32-Bit RISC Flash Microcontroller
1Device Overview
1.1Features
1
• High-Performance Automotive-Grade
Microcontroller (MCU) for Safety-Critical
Applications
– Dual CPUs Running in Lockstep
– ECC on Flash and RAM Interfaces
– Built-In Self-Test (BIST) for CPU and On-chip
RAMs
– Error Signaling Module With Error Pin
– Voltage and Clock Monitoring
• ARM®Cortex®-R4F 32-Bit RISC CPU
– 1.66 DMIPS/MHz With 8-Stage Pipeline
– FPU With Single and Double Precision
– 12-Region Memory Protection Unit (MPU)
– Open Architecture With Third-Party Support
• Operating Conditions
– Up to 160-MHz System Clock
– Core Supply Voltage (VCC): 1.14 to 1.32 V
– I/O Supply Voltage (VCCIO): 3.0 to 3.6 V
• Integrated Memory
– 768KB of Flash With ECC
– 128KB of RAM With ECC
– 64KB of Flash for Emulated EEPROM With
ECC
• Common Platform Architecture
– Consistent Memory Map Across Family
– Real-Time Interrupt Timer (RTI) OS Timer
– 128-Channel Vectored Interrupt Module (VIM)
– 2-Channel Cyclic Redundancy Checker (CRC)
• Direct Memory Access (DMA) Controller
– 16 Channels and 32 Peripheral Requests
– Parity for Control Packet RAM
– DMA Accesses Protected by Dedicated MPU
• Frequency-Modulated Phase-Locked Loop
(FMPLL) With Built-In Slip Detector
• IEEE 1149.1 JTAG, Boundary Scan and ARM
CoreSight™ Components
• Advanced JTAG Security Module (AJSM)
• Up to 64 General-Purpose I/O (GIO) Pins
– Up to 16 GIO Pins With Interrupt Generation
An IMPORTANT NOTICE at the end of this data sheet addresses availability, warranty, changes, use in safety-critical applications,
intellectual property matters and other important disclaimers. PRODUCTION DATA.
The TMS570LS0714 device is part of the Hercules TMS570 series of high-performance automotive-grade
ARM® Cortex®-R-based MCUs. Comprehensive documentation, tools, and software are available to
assist in the development of ISO 26262 and IEC 61508 functional safety applications. Start evaluating
today with the Hercules TMS570 LaunchPad Development Kit. The TMS570LS0714 device has on-chip
diagnostic features including: dual CPUs in lockstep; CPU and memory Built-In Self-Test (BIST) logic;
ECC on both the flash and the SRAM; parity on peripheral memories; and loopback capability on most
peripheral I/Os.
The TMS570LS0714 device integrates the ARM Cortex-R4F floating-point CPU which offers an efficient
1.66 DMIPS/MHz, and has configurations which can run up to 160 MHz providing up to 265 DMIPS. The
TMS570 device supports the word invariant big-endian [BE32] format.
The TMS570LS0714 device has 768KB of integrated flash and 128KB of RAM configurations with singlebit error correction and double-bit error detection. The flash memory on this device is nonvolatile,
electrically erasable and programmable, and is implemented with a 64-bit-wide data bus interface. The
flash operates on a 3.3-V supply input (same level as the I/O supply) for all read, program, and erase
operations. The SRAM supports single-cycle read and write accesses in byte, halfword, word, and
doubleword modes throughout the supported frequency range.
The TMS570LS0714 device features peripherals for real-time control-based applications, including two
Next-Generation High-End Timer (N2HET) timing coprocessors with up to 44 total I/O terminals, seven
Enhanced PWM (ePWM) modules with up to 14 outputs, six Enhanced Capture (eCAP) modules, two
Enhanced Quadrature Encoder Pulse (eQEP) modules, and two 12-bit Analog-to-Digital Converters
(ADCs) supporting up to 24 inputs.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
The N2HET is an advanced intelligent timer that provides sophisticated timing functions for real-time
applications. The timer is software-controlled, using a reduced instruction set, with a specialized timer
micromachine and an attached I/O port. The N2HET can be used for pulse-width-modulated outputs,
capture or compare inputs, or general-purpose I/O (GIO). The N2HET is especially well suited for
applications requiring multiple sensor information and drive actuators with complex and accurate time
pulses. A High-End Timer Transfer Unit (HTU) can transfer N2HET data to or from main memory. A
Memory Protection Unit (MPU) is built into the HTU.
The ePWM module can generate complex pulse width waveforms with minimal CPU overhead or
intervention. The ePWM is easy to use and supports complementary PWMs and deadband generation.
With integrated trip zone protection and synchronization with the on-chip MibADC, the ePWM is ideal for
digital motor control applications.
The eCAP module is essential in systems where the accurately timed capture of external events is
important. The eCAP can also be used to monitor the ePWM outputs or to generate simple PWM when
not needed for capture applications.
The eQEP module is used for direct interface with a linear or rotary incremental encoder to get position,
direction, and speed information from a rotating machine as used in high-performance motion and
position-control systems.
The device has two 12-bit-resolution MibADCs with 24 total inputs and 64 words of parity-protected buffer
RAM each. The MibADC channels can be converted individually or can be grouped by software for
sequential conversion sequences. Sixteen inputs are shared between the two MibADCs. There are three
separate groups. Each group can be converted once when triggered or configured for continuous
conversion mode. The MibADC has a 10-bit mode for use when compatibility with older devices or faster
conversion time is desired.
The device has multiple communication interfaces: three MibSPIs; two SPIs; two SCIs, one of which can
be used as LIN; up to three DCANs; and one I2C module. The SPI provides a convenient method of serial
interaction for high-speed communications between similar shift-register type devices. The LIN supports
the Local Interconnect standard 2.0 and can be used as a UART in full-duplex mode using the standard
Non-Return-to-Zero (NRZ) format. The DCAN supports the CAN 2.0B protocol standard and uses a serial,
multimaster communication protocol that efficiently supports distributed real-time control with robust
communication rates of up to 1 Mbps. The DCAN is ideal for applications operating in noisy and harsh
environments (for example, automotive and industrial fields) that require reliable serial communication or
multiplexed wiring.
The I2C module is a multimaster communication module providing an interface between the
microcontroller and an I2C-compatible device through the I2C serial bus. The I2C module supports speeds
of 100 and 400 kbps.
A Frequency-Modulated Phase-Locked Loop (FMPLL) clock module is used to multiply the external
frequency reference to a higher frequency for internal use. The FMPLL provides one of the six possible
clock source inputs to the Global Clock Module (GCM). The GCM manages the mapping between the
available clock sources and the device clock domains.
The device also has an external clock prescaler (ECP) circuit that when enabled, outputs a continuous
external clock on the ECLK terminal. The ECLK frequency is a user-programmable ratio of the peripheral
interface clock (VCLK) frequency. This low-frequency output can be monitored externally as an indicator of
the device operating frequency.
www.ti.com
The Direct Memory Access (DMA) controller has 16 channels, 32 peripheral requests,
and parity protection on its memory. An MPU is built into the DMA to protect memory against erroneous
transfers.
The Error Signaling Module (ESM) monitors device errors and determines whether an interrupt or external
error signal (nERROR) is asserted when a fault is detected. The nERROR terminal can be monitored
externally as an indicator of a fault condition in the microcontroller.
With integrated functional safety features and a wide choice of communication and control peripherals, the
TMS570LS0714 device is an ideal solution for high-performance, real-time control applications with safetycritical requirements.
Device Information
PART NUMBERPACKAGEBODY SIZE
TMS570LS0714PGELQFP (144)20.0 mm × 20.0 mm
TMS570LS0714PZLQFP (100)14.0 mm × 14.0 mm
(1) For more information, see Section 10, Mechanical Packaging and Orderable Information.
Figure 1-1 shows the functional block diagram of the device.
NOTE: The block diagram reflects the 144PGE package. Some functions are multiplexed or not available
in other packages. For details, see the respective terminal functions table in Section 4.2, TerminalFunctions.
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
This data manual revision history highlights the technical changes made to the SPNS226D device-specific
data manual to make it an SPNS226E revision.
Scope: Applicable updates to the TMS570LS0714 device family, specifically relating to the
TMS570LS0714 devices (Silicon Revision A), which are now in the production data (PD) stage of
development have been incorporated.
Changes from September 15, 2015 to November 1, 2016 (from D Revision (September 2015) to E Revision)Page
•GLOBAL: PZ package is now fully qualified ...................................................................................... 1
•Section 1.1 (Features): Updated/Changed the GIO pin count in GIO bullet.................................................. 1
•Section 1.1: Updated/Changed the SPI features bullet.......................................................................... 1
•Section 3.1 (Related Products): Added new section. ............................................................................ 8
Temperature
Core Supply (V)1.14 V – 1.32 V1.14 V – 1.32 V1.14 V – 1.32 V1.14 V – 1.32 V1.14 V – 1.32 V1.14 V – 1.32 V
I/O Supply (V)3.0 V – 3.6 V3.0 V – 3.6 V3.0 V – 3.6 V3.0 V – 3.6 V3.0 V – 3.6 V3.0 V – 3.6 V
120 (with 16 interrupt
-40ºC to 125ºC-40ºC to 125ºC-40ºC to 125ºC-40ºC to 125ºC-40ºC to 125ºC-40ºC to 125ºC
(1)
646464646416
2 x (24ch)2 x (24ch)2 x (24ch)2 x (24ch)2 x (16ch)1 x (16ch)
capable)
101 (with 16 interrupt
1227ZWT
capable)
(1)
64 (with 10 interrupt
0914PGE
capable)
(1)
0714PGE0714PZ0432PZ
64 (with 10 interrupt
capable)
45 (with 9 interrupt
capable)
45 (with 8 interrupt
capable)
(1) Bolding denotes a superset device. For additional device variants, see www.ti.com/tms570
3.1Related Products
For information about other devices in this family of products or related products, see the following links.
Products for TMS570 16-Bit and 32-Bit MCUs
An expansive portfolio of software and pin-compatible high-performance ARM®Cortex®-R-based MCU
products from 80 MHz up to 300 MHz with on-chip features that prove a high level of diagnostic coverage,
as well as provide scalability to address a wide range of applications.
Companion Products for TMS570LS0714
Review products that are frequently purchased or used with this product.
The signal descriptions section shows pin information in module function order per package.
Section 4.2.1 and Section 4.2.2 identify the external signal names, the associated pin or ball numbers
along with the mechanical package designator, the pin or ball type (Input, Output, I/O, Power, or Ground),
whether the pin or ball has any internal pullup/pulldown, whether the pin or ball can be configured as a
GIO, and a functional pin or ball description. The first signal name listed is the primary function for that
terminal (pin or ball). The signal name in Bold is the function being described. For information on how to
select between different multiplexed functions, see Section 4.3, Pin Multiplexing or see the I/O Multiplexing
and Control Module (IOMM) chapter of the TMS570LS09x/07x 16/32-Bit RISC Flash MicrocontrollerTechnical Reference Manual (SPNU607).
All I/O signals except nRST are configured as inputs while nPORRST is low and immediately
after nPORRST goes high.
All output-only signals are configured as high impedance while nPORRST is low, and are
configured as outputs immediately after nPORRST goes high.
While nPORRST is low, the input buffers are disabled, and the output buffers are high
impedance.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
NOTE
In the Terminal Functions tables of Section 4.2.1 and Section 4.2.2, the RESET PULL
STATE is the state of the pullup or pulldown while nPORRST is low and immediately after
nPORRST goes high. The default pull direction may change when software configures the
pin for an alternate function. The PULL TYPE is the type of pull asserted when the signal
name in bold is enabled for the given terminal.
N2HET1[0]/SPI4CLK/EPWM2B25Enhanced PWM2 Output B
N2HET1[02]/SPI4SIMO[0]/EPWM3A30Enhanced PWM3 Output A
N2HET1[05]/SPI4SOMI[0]/N2HET2[12]/EPWM3B31Enhanced PWM3 Output B
MIBSPI5NCS[0]/EPWM4A32OutputPullup–Enhanced PWM4 Output A
N2HET1[04]/EPWM4B36
N2HET1[06]/SCIRX/EPWM5A38Enhanced PWM5 Output A
N2HET1[13]/SCITX/EPWM5B39Enhanced PWM5 Output B
N2HET1[18]/EPWM6A140Enhanced PWM6 Output A
N2HET1[20]/EPWM6B141Enhanced PWM6 Output B
N2HET1[09]/N2HET2[16]/EPWM7A35Enhanced PWM7 Output A
N2HET1[07]/N2HET2[14]/EPWM7B33Enhanced PWM7 Output B
MIBSPI3NCS[3]/I2CSCL/N2HET1[29]/nTZ13
MIBSPI3NCS[2]/I2CSDA/N2HET1[27]/nTZ24
N2HET1[10]/nTZ3118Pulldown
SIGNAL
144
PGE
TYPE
OutputPulldown–
OutputPulldown–
OutputPulldown–
Input
RESET
PULL
STATE
Pullup
PULL TYPEDESCRIPTION
Enhanced PWM1 Output A
External ePWM Sync Pulse
Output
External ePWM Sync Pulse
Output
Enhanced PWM2 Output A
Enhanced PWM4 Output B
Trip Zone Inputs 1, 2 and 3.
These signals are either
connected asynchronously to
the ePWMx trip zone inputs,
Fixed, 20 µA
or double-synchronized with
VCLK4, or doublesynchronized and then filtered
with a 6-cycle VCLK4-based
counter before connecting to
the ePWMx trip zone inputs.
(1) GIOB[2] cannot output a level on to pin 55. Only the input functionality is supported so that the application can generate an interrupt
whenever the N2HET2_PIN_nDIS is asserted (driven low). Also, a pullup is enabled on the input. This is not programmable using the
GIO module control registers.
Signal
(1)
Type
I/O
Reset Pull
State
Pulldown
Pullup
Pull TypeDescription
General-purpose I/O.
Programmable,
20 µA
All GIO terminals are
capable of generating
interrupts to the CPU
on rising / falling /
both edges.
4.2.1.7Controller Area Network Controllers (DCAN)
Table 4-7. PGE Controller Area Network Controllers (DCAN)
TerminalSignal
Signal Name144
PGE
CAN1RX90I/OPullupProgrammable,
CAN1TX89CAN1 transmit, or GIO
CAN2RX129CAN2 receive, or GIO
CAN2TX128CAN2 transmit, or GIO
CAN3RX12CAN3 receive, or GIO
CAN3TX13CAN3 transmit, or GIO
Power-on reset, cold reset
External power supply monitor
circuitry must drive nPORRST
low when any of the supplies
to the microcontroller fall out
of the specified range. This
terminal has a glitch filter.
See Section 6.8.
System reset, warm reset,
bidirectional.
The internal circuitry indicates
any reset condition by driving
nRST low.
The external circuitry can
assert a system reset by
driving nRST low. To ensure
that an external reset is not
arbitrarily generated, TI
recommends that an external
pullup resistor is connected to
this terminal.
This terminal has a glitch
filter. See Section 6.8.
ESM Error Signal
Indicates error of high
severity. See Section 6.8.
4.2.1.14 Clock Inputs and Outputs
Table 4-14. PGE Clock Inputs and Outputs
TerminalSignal
Signal Name144
Type
PGE
OSCIN18Input–NoneFrom external
KELVIN_GND19InputKelvin ground for oscillator
OSCOUT20OutputTo external
TEST34InputPulldownFixed, 100 µATest enable. This terminal
nTRST109InputJTAG test hardware reset
RTCK113Output-NoneJTAG return test clock
TCK112InputPulldownFixed, 100 µAJTAG test clock
TDI110InputPullupJTAG test data in
TDO111OutputPulldownJTAG test data out
TMS108InputPullupJTAG test select
Type
Reset Pull
State
Pull TypeDescription
must be connected to
ground directly or via a
pulldown resistor.
4.2.1.16 Flash Supply and Test Pads
Table 4-16. PGE Flash Supply and Test Pads
TerminalSignal
Signal Name144
PGE
VCCP1343.3-V
FLTP17––NoneFlash test pads. These
FLTP28
Type
Power
Reset Pull
State
–NoneFlash pump supply
Pull TypeDescription
terminals are reserved for
TI use only. For proper
operation these terminals
must connect only to a
test pad or not be
connected at all [no
connect (NC)].
4.2.1.17 Supply for Core Logic: 1.2V nominal
Table 4-17. PGE Supply for Core Logic: 1.2V nominal
4.2.2.7Standard Serial Peripheral Interfaces (SPI2 and SPI4)
Table 4-26. PZ Standard Serial Peripheral Interfaces (SPI2 and SPI4)
TerminalSignal Type Reset Pull
Signal Name100 PZ
SPI2CLK71I/OPullupProgrammable, 20 µA SPI2 Serial Clock, or GPIO
SPI2nCS[0]23SPI2 Chip Select, or GPIO
SPI2SIMO70SPI2 Slave-In-Master-Out, or GPIO
SPI2SOMI69SPI2 Slave-Out-Master-In, or GPIO
The drive strengths for the SPI2CLK, SPI2SIMO and SPI2SOMI signals are selected individually by configuring the respective SRS bits of the SPIPC9 register
fo SPI2.
SRS = 0 for 8mA drive (fast). This is the default mode as the SRS bits in the SPIPC9 register default to 0.
SRS = 1 for 2mA drive (slow)
N2HET1[0] / SPI4CLK / EPWM2B19I/OPulldownProgrammable, 20 µA SPI2 Serial Clock, or GPIO
N2HET1[2] / SPI4SIMO / EPWM3A22SPI2 Slave-In-Master-Out, or GPIO
State
Pull TypeDescription
SPI2
SPI4
4.2.2.8Multibuffered Serial Peripheral Interface (MibSPI1 and MibSPI3)
Table 4-27. PZ Multibuffered Serial Peripheral Interface (MibSPI1 and MibSPI3)
TerminalSignal
Signal Name100 PZ
MIBSPI1CLK67I/OPullupProgrammable, 20 µA MibSPI1 Serial Clock, or GPIO
MIBSPI1nCS[0]/MIBSPI1SOMI[1]/
Power-on reset, cold reset External power supply
monitor circuitry must drive nPORRST low when any of
the supplies to the microcontroller fall out of the
specified range. This terminal has a glitch filter. See
Section 6.8.
The external circuitry can assert a system reset by
driving nRST low. To ensure that an external reset is not
arbitrarily generated, TI recommends that an external
pullup resistor is connected to this terminal. This
terminal has a glitch filter. See Section 6.8.
ESM Error Signal. Indicates error of high severity. See
Section 6.8.
4.2.2.12 Clock Inputs and Outputs
Table 4-31. PZ Clock Inputs and Outputs
TERMINAL
SIGNAL NAME100 PZ
OSCIN14Input––From external crystal/resonator, or external clock input
KELVIN_GND15Input––Dedicated ground for oscillator
OSCOUT16Output––To external crystal/resonator
ECLK84I/OPulldownProgrammable, 20 µA External prescaled clock output, or GIO.
nTRST76InputPulldownFixed, 100 µAJTAG test hardware reset
RTCK80Output––JTAG return test clock
TCK79InputPulldownFixed, 100 µAJTAG test clock
TDI77I/OPullupFixed, 100 µAJTAG test data in
TDO78I/OPulldownFixed, 100 µAJTAG test data out
TMS75I/OPullupFixed, 100 µAJTAG test select
TEST24I/OPulldownFixed, 100 µA
SIGNAL
TYPE
RESET
PULL
STATE
PULL TYPEDESCRIPTION
Test enable. This terminal must be connected to ground
directly or via a pulldown resistor.
4.2.2.14 Flash Supply and Test Pads
Table 4-33. PZ Flash Supply and Test Pads
www.ti.com
TerminalSignal
Signal Name100
Type
Reset Pull
State
Pull TypeDescription
PZ
VCCP963.3-V
Power
––Flash external pump voltage (3.3 V). This
terminal is required for both Flash read and Flash
program and erase operations.
FLTP13Input––Flash Test Pins. For proper operation this
FLTP24Input––
terminal must connect only to a test pad or not be
connected at all [no connect (NC)].
The test pad must not be exposed in the final
product where it might be subjected to an ESD
event.
4.2.2.15 Supply for Core Logic: 1.2-V Nominal
Table 4-34. PZ Supply for Core Logic: 1.2-V Nominal
TerminalSignal
Signal Name100
Type
PZ
VCC131.2-V
VCC21
Power
VCC30
VCC32
VCC61
VCC88
VCC99
Reset Pull
Pull TypeDescription
State
––Digital logic and RAM supply
4.2.2.16 Supply for I/O Cells: 3.3-V Nominal
Table 4-35. PZ Supply for I/O Cells: 3.3-V Nominal
4.2.2.17 Ground Reference for All Supplies Except VCCAD
Table 4-36. PZ Ground Reference for All Supplies Except VCCAD
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
TerminalSignal
Signal Name100
PZ
VSS7Ground––Device Ground Reference. This is a single
VSS17
VSS20
VSS29
VSS33
VSS59
VSS72
VSS86
VSS87
VSS100
Type
Reset Pull
State
Pull TypeDescription
ground reference for all supplies except for the
ADC Supply.
4.3Pin Multiplexing
This microcontroller has several interfaces and uses extensive multiplexing to bring out the functions as
required by the target application. The multiplexing is mostly on the output signals. A few inputs are also
multiplexed to allow the same input signal to be driven in from a selected terminal.
4.3.1Output Multiplexing
Table 4-37 and Table 4-38 show the pin multiplexing control x register (PINMMRx) and the associated bit
(1) The CTRLx columns contain a value of type x[y], which indicates the pin multiplexing control x register (PINMMRx) and the associated bit field [y].
(1) The CTRLx columns contain a value of type x[y], which indicates the pin multiplexing control x register (PINMMRx) and the associated bit field [y].
Table 4-38. Multiplexing for Outputs on 100-Pin PZ Package
Some signals are connected to more than one terminal, the inputs for these signals can come from any of
the terminals. A multiplexor is implemented to let the application choose the terminal that will be used,
providing the input signal is from among the available options.
Table 4-39. Input Multiplexing and Control for All Packages [144-Pin PGE, and 100-Pin PZ](1)
SIGNAL
NAME
DEDICATED INPUTSMULTIPLEXED INPUTS
INPUT MULTIPLEXOR
CONTROL
INPUT PATH SELECTED
144 PGE100 PZ144 PGE100 PZBIT1BIT2DEDICATED, IFMUXED, IF
GIOB[2]142–5538PINMUX29[16]PINMUX29[16]BIT1 = 0(3)BIT1 = 1(3)
N2HET1[17]––13093PINMUX20[17]PINMUX24[16]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[19]––4027PINMUX8[9]PINMUX24[24]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[21]––––PINMUX9[25]PINMUX25[0]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[23]––9668PINMUX12[17]PINMUX25[8]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[25]––37–PINMUX7[9]PINMUX25[16]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[27]––4–PINMUX0[26]PINMUX25[24]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[29]––3–PINMUX0[18]PINMUX26[0]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
N2HET1[31]––5437PINMUX9[10]PINMUX26[8]not(BIT1) or (BIT1 and BIT2) = 1BIT1 and not(BIT2) = 1
(1) The default inputs to the modules are from the dedicated input terminals. The application must configure the PINMUX registers as shown in order to select the multiplexed input path, if
required.
(2) The SPI4CLK, SPI4SIMO, SPI4SOMI, SPI4nENA and SPI4nCS[0] signals do not have a dedicated signal pad on this device. Therefore, the input multiplexors on these inputs are not
required. The control registers are still available to maintain compatibility to the emulation device.
(3) When the muxed input is selected for GIOB[2], the PINMUX9[16] and PINMUX9[17] must be cleared. These bits affect the control over the PULDIS (pull disable) and PSEL (pull select).
When the multiplexed input path is selected for GIOB[2], the PULDIS is tied to 0 (pull is enabled, cannot be disabled) and the PULSEL is tied to 1 (pull up selected, not programmable).
All input pins, with exception of ADC pins–0.34.6
ADC input pins–0.36.25
, V
(2)
CCP
(2)
Output voltageAll output pins–0.34.6V
IIK(VI< 0 or VI> V
All pins, except AD1IN[23:0] or AD2IN[15:0]
Input clamp current
AD1IN[23:0] or AD2IN[15:0]
CCIO
CCAD
)
)
Total–4040
Output clamp current
IOK(VO< 0 or VO> V
All pins, except AWM1_EXT_x
CCIO
)
Total–4040
Operating free-air
temperature (TA)
Operating junction
temperature (TJ)
Storage temperature (T
)–65150°C
stg
(1) Stresses beyond those listed under Absolute Maximum Ratings may cause permanent damage to the device. These are stress ratings
only, and functional operation of the device at these or any other conditions beyond those indicated under Recommended OperatingConditions is not implied. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.
(2) Maximum-rated conditions for extended periods may affect device reliability. All voltage values are with respect to their associated
over operating free-air temperature range (unless otherwise noted)
TEST CONDITIONSMINNOMMAX UNIT
V
CC
V
CCIO
V
CCAD
V
CCP
V
SS
V
SSAD
V
ADREFHI
V
ADREFLO
V
SLEW
V
hys
V
IL
V
IH
T
A
T
J
(1) All voltages are with respect to VSS, except V
(2) Reliability data is based upon a temperature profile that is equivalent to 100,000 power-on hours at 105°C junction temperature.
Digital logic supply voltage (Core)1.141.21.32V
Digital logic supply voltage (I/O)33.33.6V
MibADC supply voltage35.25V
Flash pump supply voltage33.33.6V
Digital logic supply ground0V
MibADC supply ground–0.10.1V
Analog-to-digital high-voltage reference sourceV
Analog-to-digital low-voltage reference sourceV
Maximum positive slew rate for V
Table 5-1 shows the thermal resistance characteristics for the QFP - PGE mechanical package.
Table 5-2 shows the thermal resistance characteristics for the QFP - PZ mechanical package.
As shown in Figure 5-1 and Figure 5-2, the TCM RAM can support program and data fetches at full CPU
speed without any address or data wait states required.
The TCM flash can support zero address and data wait states up to a CPU speed of 50 MHz in
nonpipelined mode. The flash supports a maximum CPU clock speed of 160 MHz in pipelined mode for
the PGE Package, and 100 MHz for the PZ package.
The flash wrapper defaults to nonpipelined mode with zero address wait state and one random-read data
wait state.
The device core logic is split up into multiple power domains to optimize the power for a given application
use case. There are five core power domains: PD1, PD2, PD3, PD5, and RAM_PD1. See Section 1.4 for
more information.
PD1 is an "always-ON" power domain, which cannot be turned off. Each of the other core power domains
can be turned ON/OFF one time during device initialization as per the application requirement. Refer to
the Power Management Module (PMM) chapter of the device technical reference manual for more details.
NOTE
The clocks to a module must be turned off before powering down the core domain that
contains the module.
6.2Voltage Monitor Characteristics
A voltage monitor is implemented on this device. The purpose of this voltage monitor is to eliminate the
requirement for a specific sequence when powering up the core and I/O voltage supplies.
6.2.1Important Considerations
•The voltage monitor does not eliminate the need of a voltage supervisor circuit to ensure that the device is held in
reset when the voltage supplies are out of range.
•The voltage monitor only monitors the core supply (VCC) and the I/O supply (VCCIO). The other supplies are not
monitored by the VMON. For example, if the VCCAD or VCCP are supplied from a source different from that for
VCCIO, then there is no internal voltage monitor for the VCCAD and VCCP supplies.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
6.2.2Voltage Monitor Operation
The voltage monitor generates the Power Good MCU signal (PGMCU) as well as the I/Os Power Good IO
signal (PGIO) on the device. During power-up or power-down, the PGMCU and PGIO are driven low when
the core or I/O supplies are lower than the specified minimum monitoring thresholds. The PGIO and
PGMCU signals being low isolates the core logic as well as the I/O controls during power up or power
down of the supplies. This allows the core and I/O supplies to be powered up or down in any order.
When the voltage monitor detects a low voltage on the I/O supply, it will assert a power-on reset. When
the voltage monitor detects an out-of-range voltage on the core supply, it asynchronously makes all output
pins high impedance, and asserts a power-on reset. The voltage monitor is disabled when the device
enters a low power mode.
The VMON also incorporates a glitch filter for the nPORRST input. Refer to Section 6.3.3.1 for the timing
information on this glitch filter.
Table 6-1. Voltage Monitoring Specifications
PARAMETERMINTYPMAXUNIT
VCC low - VCC level below this
threshold is detected as too low.
V
MON
Voltage monitoring
thresholds
VCC high - VCC level above this
threshold is detected as too high.
VCCIO low - VCCIO level below this
threshold is detected as too low.
The VMON has the capability to filter glitches on the VCC and VCCIO supplies.
The following table shows the characteristics of the supply filtering. Glitches in the supply larger than the
Width of glitch on VCC that can be filtered2501000ns
Width of glitch on VCCIO that can be filtered2501000ns
6.3Power Sequencing and Power-On Reset
6.3.1Power-Up Sequence
There is no timing dependency between the ramp of the VCCIO and the VCC supply voltage. The powerup sequence starts with the I/O voltage rising above the minimum I/O supply threshold, (see Table 6-4 for
more details), core voltage rising above the minimum core supply threshold and the release of power-on
reset. The high-frequency oscillator will start up first and its amplitude will grow to an acceptable level. The
oscillator start-up time is dependent on the type of oscillator and is provided by the oscillator vendor. The
different supplies to the device can be powered up in any order.
www.ti.com
The device goes through the following sequential phases during power up.
Oscillator start-up and validity check1032 oscillator cycles
eFuse autoload1160 oscillator cycles
Flash pump power-up688 oscillator cycles
Flash bank power-up617 oscillator cycles
Total3497 oscillator cycles
The CPU reset is released at the end of the above sequence and fetches the first instruction from address
0x00000000.
6.3.2Power-Down Sequence
The different supplies to the device can be powered down in any order.
This is the power-on reset. This reset must be asserted by an external circuitry whenever any power
supply is outside the specified recommended range. This signal has a glitch filter on it. It also has an
internal pulldown.
6.3.3.1nPORRST Electrical and Timing Requirements
Table 6-4. Electrical Requirements for nPORRST
NO.MINMAXUNIT
3t
6t
7t
8t
9t
V
CCPORL
V
CCPORH
V
CCIOPORL
V
CCIOPORH
V
IL(PORRST)
su(PORRST)
h(PORRST)
su(PORRST)
h(PORRST)
h(PORRST)
VCClow supply level when nPORRST must be active during power up0.5V
VCChigh supply level when nPORRST must remain active during power
up and become active during power down
V
/ V
CCIO
power up
V
CCIO
during power up and become active during power down
Low-level input voltage of nPORRST V
Low-level input voltage of nPORRST V
Setup time, nPORRST active before V
power up
Hold time, nPORRST active after VCC> V
Setup time, nPORRST active before VCC< V
Hold time, nPORRST active after V
Hold time, nPORRST active after VCC< V
low supply level when nPORRST must be active during
CCP
/ V
high supply level when nPORRST must remain active
CCP
> 2.5 V0.2 * V
CCIO
< 2.5 V0.5V
CCIO
and V
CCIO
CCIO
and V
CCPORH
CCPORH
CCP
CCPORL
CCP
> V
> V
CCIOPORL
during
during power down2µs
CCIOPORH
1.14V
1.1V
3.0V
CCIO
0ms
1ms
1ms
0ms
V
t
f(nPORRST)
FiltertimenPORRSTpin;
pulses less than MIN will be filtered out, pulses greater than MAX will
generate a reset.
A. Figure 6-1 shows that there is no timing dependency between the ramp of the V
This is a bidirectional reset signal. The internal circuitry drives the signal low on detecting any device reset
condition. An external circuit can assert a device reset by forcing the signal low. On this terminal, the
output buffer is implemented as an open drain (drives low only). To ensure an external reset is not
arbitrarily generated, TI recommends that an external pullup resistor is connected to this terminal.
This terminal has a glitch filter. It also has an internal pullup
6.4.1Causes of Warm Reset
Table 6-5. Causes of Warm Reset
DEVICE EVENTSYSTEM STATUS FLAG
Power-Up ResetException Status Register, bit 15
Oscillator failGlobal Status Register, bit 0
PLL slipGlobal Status Register, bits 8 and 9
Watchdog exception / Debugger resetException Status Register, bit 13
CPU Reset (driven by the CPU STC)Exception Status Register, bit 5
Software ResetException Status Register, bit 4
External ResetException Status Register, bit 3
6.4.2nRST Timing Requirements
Table 6-6. nRST Timing Requirements
Valid time, nRST active after nPORRST inactive2256t
t
v(RST)
t
f(nRST)
(1) Specified values do not include rise/fall times. For rise and fall timings, see Table 7-2.
Valid time, nRST active (all other System reset
conditions)
FiltertimenRSTpin;
pulses less than MIN will be filtered out, pulses greater
than MAX will generate a reset
•An integer unit with integral EmbeddedICE-RT logic.
•High-speed Advanced Microprocessor Bus Architecture (AMBA) Advanced eXtensible Interfaces (AXI)
for Level two (L2) master and slave interfaces.
•Floating-Point Coprocessor
•Dynamic branch prediction with a global history buffer, and a 4-entry return stack
•Low interrupt latency.
•Nonmaskable interrupt.
•A Harvard Level one (L1) memory system with:
– Tightly-Coupled Memory (TCM) interfaces with support for error correction or parity checking
memories
– ARMv7-R architecture Memory Protection Unit (MPU) with 12 regions
•Dual core logic for fault detection in safety-critical applications.
•An L2 memory interface:
– Single 64-bit master AXI interface
– 64-bit slave AXI interface to TCM RAM blocks
•A debug interface to a CoreSight Debug Access Port (DAP).
•Six Hardware Breakpoints
•Two Watchpoints
•A Performance Monitoring Unit (PMU).
•A Vectored Interrupt Controller (VIC) port.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
For more information on the ARM Cortex-R4F CPU, see www.arm.com.
6.5.2ARM Cortex-R4F CPU Features Enabled by Software
The following CPU features are disabled on reset and must be enabled by the application if required.
•ECC On Tightly-Coupled Memory (TCM) Accesses
•Hardware Vectored Interrupt (VIC) Port
•Floating-Point Coprocessor
•Memory Protection Unit (MPU)
6.5.3Dual Core Implementation
The device has two Cortex-R4F cores, where the output signals of both CPUs are compared in the CCMR4 unit. To avoid common mode impacts the signals of the CPUs to be compared are delayed by two
clock cycles as shown in Figure 6-2.
The CPUs have a diverse CPU placement given by following requirements:
•different orientation; for example, CPU1 = "north" orientation, CPU2 = "flip west" orientation
•dedicated guard ring for each CPU
Figure 6-3. Dual-CPU Orientation
6.5.4Duplicate Clock Tree After GCLK
The CPU clock domain is split into two clock trees, one for each CPU, with the clock of the second CPU
running at the same frequency and in phase to the clock of CPU1. See Figure 6-2.
6.5.5ARM Cortex-R4F CPU Compare Module (CCM) for Safety
This device has two ARM Cortex-R4F CPU cores, where the output signals of both CPUs are compared in
the CCM-R4 unit. To avoid common mode impacts the signals of the CPUs to be compared are delayed in
a different way as shown in Figure 6-2.
To avoid an erroneous CCM-R4 compare error, the application software must initialize the registers of
both CPUs before the registers are used, including function calls where the register values are pushed
onto the stack.
The CPU STC (Self-Test Controller) is used to test the two Cortex-R4F CPU Cores using the
Deterministic Logic BIST Controller as the test engine.
The main features of the self-test controller are:
•Ability to divide the complete test run into independent test intervals
•Capable of running the complete test as well as running few intervals at a time
•Ability to continue from the last executed interval (test set) as well as ability to restart from the
beginning (First test set)
•Complete isolation of the self-tested CPU core from rest of the system during the self-test run
•Ability to capture the Failure interval number
•Time-out counter for the CPU self-test run as a fail-safe feature
6.5.6.1Application Sequence for CPU Self-Test
1. Configure clock domain frequencies.
2. Select number of test intervals to be run.
3. Configure the time-out period for the self-test run.
4. Enable self-test.
5. Wait for CPU reset.
6. In the reset handler, read CPU self-test status to identify any failures.
7. Retrieve CPU state if required.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
For more information see the device Technical Reference Manual.
6.5.6.2CPU Self-Test Clock Configuration
The maximum clock rate for the self-test is HCLKmax/2. The STCCLK is divided down from the CPU
clock. This divider is configured by the STCCLKDIV register at address 0xFFFFE108.
For more information see the device-specific Technical Reference Manual.
6.5.6.3CPU Self-Test Coverage
Table 6-7 lists the CPU self-test coverage achieved for each self-test interval. It also lists the cumulative
test cycles. The test time can be calculated by multiplying the number of test cycles with the STC clock
period.
Table 6-8 lists the available clock sources on the device. Each clock source can be enabled or disabled
using the CSDISx registers in the system module. The clock source number in the table corresponds to
the control bit in the CSDISx register for that clock source.
Table 6-8 also shows the default state of each clock source.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
Table 6-8. Available Clock Sources
CLOCK
SOURCE NO.
0OSCINMain oscillatorEnabled
1PLL1Output from PLL1Disabled
2ReservedReservedDisabled
3EXTCLKIN1External clock input 1Disabled
4LFLPOLow-frequency output of internal reference oscillatorEnabled
5HFLPO
6ReservedReservedDisabled
7EXTCLKIN2External clock input 2Disabled
6.6.1.1Main Oscillator
The oscillator is enabled by connecting the appropriate fundamental resonator/crystal and load capacitors
across the external OSCIN and OSCOUT pins as shown in Figure 6-4. The oscillator is a single-stage
inverter held in bias by an integrated bias resistor. This resistor is disabled during leakage test
measurement and low power modes.
TI strongly encourages each customer to submit samples of the device to the
resonator/crystal vendors for validation. The vendors are equipped to determine which load
capacitors will best tune their resonator/crystal to the microcontroller device for optimum
start-up and operation over temperature and voltage extremes.
NAMEDESCRIPTIONDEFAULT STATE
High-frequency output of internal reference
oscillator
Enabled
NOTE
An external oscillator source can be used by connecting a 3.3-V clock signal to the OSCIN pin and leaving
the OSCOUT pin unconnected (open) as shown in Figure 6-4.
The platform architecture defines a special mode that allows various clock signals to be selected and
output on the ECLK pin and N2HET1[12] device outputs. This special mode, Clock Test Mode, is very
useful for debugging purposes and can be configured through the CLKTEST register in the system
module. See Table 6-14 for the CLKTEST bits value and signal selection.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
Table 6-14. Clock Test Mode Options
SEL_ECP_PIN
=
CLKTEST[4-0]
00000Oscillator0000Oscillator Valid Status
00001Main PLL free-running clock output0001Main PLL Valid status
00010Reserved0010Reserved
00011EXTCLKIN10011Reserved
00100LFLPO0100Reserved
00101HFLPO0101HFLPO Valid status
00110Reserved0110Reserved
00111EXTCLKIN20111Reserved
01000GCLK1000LFLPO
01001RTI Base1001Oscillator Valid status
01010Reserved1010Oscillator Valid status
01011VCLKA11011Oscillator Valid status
01100VCLKA21100Oscillator Valid status
01101Reserved1101Reserved
01110Reserved1110Reserved
01111Reserved1111Oscillator Valid status
10000Reserved
10001HCLK
10010VCLK
10011VCLK2
10100Reserved
10101VCLK4
10110Reserved
10111Reserved
11000Reserved
The LPO Clock Detect (LPOCLKDET) module consists of a clock monitor (CLKDET) and an internal LPO.
The LPO provides two different clock sources – a low frequency (LFLPO) and a high frequency (HFLPO).
The CLKDET is a supervisor circuit for an externally supplied clock signal (OSCIN). In case the OSCIN
frequency falls out of a frequency window, the CLKDET flags this condition in the global status register
(GLBSTAT bit 0: OSC FAIL) and switches all clock domains sourced by OSCIN to the HFLPO clock (limp
mode clock).
www.ti.com
The valid OSCIN frequency range is defined as: f
HFLPO
6.7.1Clock Monitor Timings
For more information on LPO and Clock detection, see Table 6-10.
Figure 6-8. LPO and Clock Detection, Untrimmed HFLPO
6.7.2External Clock (ECLK) Output Functionality
The ECLK pin can be configured to output a prescaled clock signal indicative of an internal device clock.
This output can be externally monitored as a safety diagnostic.
6.7.3Dual Clock Comparators
The Dual Clock Comparator (DCC) module determines the accuracy of selectable clock sources by
counting the pulses of two independent clock sources (counter 0 and counter 1). If one clock is out of
spec, an error signal is generated. For example, the DCC1 can be configured to use HFLPO as the
reference clock (for counter 0) and VCLK as the "clock under test" (for counter 1). This configuration
allows the DCC1 to monitor the PLL output clock when VCLK is using the PLL output as its source.
/ 4 < f
OSCIN
< f
HFLPO
* 4.
An additional use of this module is to measure the frequency of a selectable clock source, using the input
clock as a reference, by counting the pulses of two independent clock sources. Counter 0 generates a
fixed-width counting window after a preprogrammed number of pulses. Counter 1 generates a fixed-width
pulse (1 cycle) after a preprogrammed number of pulses. This pulse sets as an error signal if counter 1
does not reach 0 within the counting window generated by counter 0.
6.7.3.1Features
•Takes two different clock sources as input to two independent counter blocks.
•One of the clock sources is the known-good, or reference clock; the second clock source is the "clock under test."
•Each counter block is programmable with initial, or seed values.
•The counter blocks start counting down from their seed values at the same time; a mismatch from the expected
CoreSight Debug ROMCSCS00xFFA0_00000xFFA0_0FFF4KB4KBReads return zeros, writes have no effect
Cortex-R4F DebugCSCS10xFFA0_10000xFFA0_1FFF4KB4KBReads return zeros, writes have no effect
HTU1PS[22]0xFFF7_A4000xFFF7_A4FF256B256BReads return zeros, writes have no effect
HTU2PS[22]0xFFF7_A5000xFFF7_A5FF256B256BReads return zeros, writes have no effect
N2HET1PS[17]0xFFF7_B8000xFFF7_B8FF256B256BReads return zeros, writes have no effect
N2HET2PS[17]0xFFF7_B9000xFFF7_B9FF256B256BReads return zeros, writes have no effect
GIOPS[16]0xFFF7_BC000xFFF7_BDFF512B256BReads return zeros, writes have no effect
MIBADC1PS[15]0xFFF7_C0000xFFF7_C1FF512B512BReads return zeros, writes have no effect
MIBADC2PS[15]0xFFF7_C2000xFFF7_C3FF512B512BReads return zeros, writes have no effect
I2CPS[10]0xFFF7_D4000xFFF7_D4FF256B256BReads return zeros, writes have no effect
DCAN1PS[8]0xFFF7_DC000xFFF7_DDFF512B512BReads return zeros, writes have no effect
DCAN2PS[8]0xFFF7_DE000xFFF7_DFFF512B512BReads return zeros, writes have no effect
DCAN3PS[7]0xFFF7_E0000xFFF7_E1FF512B512BReads return zeros, writes have no effect
LINPS[6]0xFFF7_E4000xFFF7_E4FF256B256BReads return zeros, writes have no effect
SCIPS[6]0xFFF7_E5000xFFF7_E5FF256B256BReads return zeros, writes have no effect
MibSPI1PS[2]0xFFF7_F4000xFFF7_F5FF512B512BReads return zeros, writes have no effect
SPI2PS[2]0xFFF7_F6000xFFF7_F7FF512B512BReads return zeros, writes have no effect
MibSPI3PS[1]0xFFF7_F8000xFFF7_F9FF512B512BReads return zeros, writes have no effect
SPI4PS[1]0xFFF7_FA000xFFF7_FBFF512B512BReads return zeros, writes have no effect
MibSPI5PS[0]0xFFF7_FC000xFFF7_FDFF512B512BReads return zeros, writes have no effect
FRAME CHIP
SELECT
PCS[29]0xFF3A_00000xFF3B_FFFF128KB
PCS[31]0xFF3E_00000xFF3F_FFFF128KB
FRAME ADDRESS RANGE
STARTEND
Debug Components
Peripheral Control Registers
FRAME
SIZE
ACTUAL
SIZE
8KB
384B
8KB
384B
RESPONSE FOR ACCESS TO
UNIMPLEMENTED LOCATIONS IN
FRAME
Wrap around for accesses to
unimplemented address offsets lower
than 0x7FF. Abort generated for
accesses beyond offset 0x800.
Wrap around for accesses to
unimplemented address offsets lower
than 0x7FF. Abort generated for
accesses beyond offset 0x800.
Wrap around for accesses to
unimplemented address offsets lower
than 0x1FFF. Abort generated for
accesses beyond 0x1FFF.
Look-Up Table for ADC2 wrapper. Starts
at address offset 0x2000 and ends at
address offset 0x217F. Wrap around for
accesses between offsets 0x0180 and
0x3FFF. Abort generated for accesses
beyond offset 0x4000.
Wrap around for accesses to
unimplemented address offsets lower
than 0x1FFF. Abort generated for
accesses beyond 0x1FFF.
Look-Up Table for ADC1 wrapper. Starts
at address offset 0x2000 and ends at
address offset 0x217F. Wrap around for
accesses between offsets 0x0180 and
0x3FFF. Abort generated for accesses
PCR registersPPS00xFFFF_E0000xFFFF_E0FF256B256BReads return zeros, writes have no effect
System Module -
Frame 2
(see device TRM)
PBISTPPS10xFFFF_E4000xFFFF_E5FF512B512BReads return zeros, writes have no effect
STCPPS10xFFFF_E6000xFFFF_E6FF256B256B
IOMM Multiplexing
Control Module
DCC1PPS30xFFFF_EC000xFFFF_ECFF256B256BReads return zeros, writes have no effect
DMAPPS40xFFFF_F0000xFFFF_F3FF1KB1KBReads return zeros, writes have no effect
DCC2PPS50xFFFF_F4000xFFFF_F4FF256B256BReads return zeros, writes have no effect
ESMPPS50xFFFF_F5000xFFFF_F5FF256B256BReads return zeros, writes have no effect
CCMR4PPS50xFFFF_F6000xFFFF_F6FF256B256BReads return zeros, writes have no effect
RAM ECC evenPPS60xFFFF_F8000xFFFF_F8FF256B256BReads return zeros, writes have no effect
RAM ECC oddPPS60xFFFF_F9000xFFFF_F9FF256B256BReads return zeros, writes have no effect
RTI + DWWDPPS70xFFFF_FC000xFFFF_FCFF256B256BReads return zeros, writes have no effect
VIM ParityPPS70xFFFF_FD000xFFFF_FDFF256B256BReads return zeros, writes have no effect
VIMPPS70xFFFF_FE000xFFFF_FEFF256B256BReads return zeros, writes have no effect
System Module -
Frame 1
(see device TRM)
FRAME CHIP
SELECT
PPSE00xFFFF_00000xFFFF_01FF512B512BAbort
PPS00xFFFF_E1000xFFFF_E1FF256B256BReads return zeros, writes have no effect
PPS20xFFFF_EA000xFFFF_EBFF512B512BReads return zeros, writes have no effect
PPS70xFFFF_FF000xFFFF_FFFF256B256BReads return zeros, writes have no effect
FRAME ADDRESS RANGE
STARTEND
System Modules Control Registers and Memories
FRAME
SIZE
ACTUAL
SIZE
RESPONSE FOR ACCESS TO
UNIMPLEMENTED LOCATIONS IN
FRAME
Wrap around for accesses to
unimplemented address offsets between
1KB and 4KB.
Generates address error interrupt, if
enabled
6.9.3Special Consideration for CPU Access Errors Resulting in Imprecise Aborts
Any CPU write access to a Normal or Device type memory, which generates a fault, will generate an
imprecise abort. The imprecise abort exception is disabled by default and must be enabled for the CPU to
handle this exception. The imprecise abort handling is enabled by clearing the "A" bit in the CPU program
status register (CPSR).
Table 6-21 lists the access permissions for each bus master on the device. A bus master is a module that
can initiate a read or a write transaction on the device.
Each slave module on the main interconnect is listed in the table. Yes indicates that the module listed in
Write accesses to the Power Domain Management Module (PMM) control registers are limited to the CPU
(master id = 1). The other masters can only read from these registers.
A debugger can also write to the PMM registers. The master-id check is disabled in debug mode.
The device contains dedicated logic to generate a bus error response on any access to a module that is in
Flash Bank: A separate block of logic consisting of 1 to 16 sectors. Each flash bank normally has a
customer-OTP and a TI-OTP area. These flash sectors share input/output buffers, data paths, sense
amplifiers, and control logic.
Flash Sector: A contiguous region of flash memory which must be erased simultaneously due to physical
construction constraints.
Flash Pump: A charge pump which generates all the voltages required for reading, programming, or
erasing the flash banks.
Flash Module: Interface circuitry required between the host CPU and the flash banks and pump module.
Table 6-22. Flash Memory Banks and Sectors
www.ti.com
MEMORY ARRAYS (OR BANKS)
BANK0 (768KB)
BANK7 (64KB) for EEPROM emulation
(1) Flash bank0 is a 144-bit-wide bank with ECC support.
(2) Flash bank7 is a 72-bit-wide bank with ECC support.
(3) The flash bank7 can be programmed while executing code from flash bank0.
(4) Code execution is not allowed from flash bank7.
•Support for multiple flash banks for program and/or data storage
•Simultaneous read access on a bank while performing program or erase operation on any other bank
•Integrated state machines to automate flash erase and program operations
•Pipelined mode operation to improve instruction access interface bandwidth
•Support for Single Error Correction Double Error Detection (SECDED) block inside Cortex-R4F CPU
– Error address is captured for host system debugging
•Support for a rich set of diagnostic features
6.10.3 ECC Protection for Flash Accesses
All accesses to the program flash memory are protected by SECDED logic embedded inside the CPU.
The flash module provides 8 bits of ECC code for 64 bits of instructions or data fetched from the flash
memory. The CPU calculates the expected ECC code based on the 64 bits received and compares it with
the ECC code returned by the flash module. A single-bit error is corrected and flagged by the CPU, while
a multibit error is only flagged. The CPU signals an ECC error through its Event bus. This signaling
mechanism is not enabled by default and must be enabled by setting the "X" bit of the Performance
Monitor Control Register, c9.
MRC p15,#0,r1,c9,c12,#0;Enabling Event monitor states
ORR r1, r1, #0x00000010
MCR p15,#0,r1,c9,c12,#0;Set 4th bit (‘X’) of PMNC register
MRC p15,#0,r1,c9,c12,#0
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
The application must also explicitly enable the ECC checking of the CPU for accesses on the CPU ATCM
and BTCM interfaces. These are connected to the program flash and data RAM, respectively. ECC
checking for these interfaces can be done by setting the B1TCMPCEN, B0TCMPCEN, and ATCMPCEN
bits of the System Control Coprocessor Auxiliary Control Register, c1.
Figure 6-10 shows the connection of the Tightly Coupled RAM (TCRAM) to the Cortex-R4F™ CPU.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
6.11.1 Features
The features of the Tightly Coupled RAM (TCRAM) Module are:
•Acts as slave to the BTCM interface of the Cortex-R4F CPU
•Supports CPU internal ECC scheme by providing 64-bit data and 8-bit ECC code
•Monitors CPU Event Bus and generates single-bit or multibit error interrupts
•Stores addresses for single-bit and multibit errors
•Supports RAM trace module
•Provides CPU address bus integrity checking by supporting parity checking on the address bus
•Performs redundant address decoding for the RAM bank chip select and ECC select generation logic
•Provides enhanced safety for the RAM addressing by implementing two 36-bit-wide byte-interleaved RAM banks
and generating independent RAM access control signals to the two banks
•Supports auto-initialization of the RAM banks along with the ECC bits
6.11.2 TCRAMW ECC Support
The TCRAMW passes on the ECC code for each data read by the Cortex-R4F CPU from the RAM. The
TCRAMW also stores the ECC port contents of the CPU in the ECC RAM when the CPU does a write to
the RAM. The TCRAMW monitors the CPU event bus and provides registers for indicating single-bit or
multibit errors and also for identifying the address that caused the single or multi-bit error. The event
signaling and the ECC checking for the RAM accesses must be enabled inside the CPU.
For more information, see the device-specific Technical Reference Manual.
6.12Parity Protection for Accesses to Peripheral RAMs
Accesses to some peripheral RAMs are protected by odd/even parity checking. During a read access the
parity is calculated based on the data read from the peripheral RAM and compared with the good parity
value stored in the parity RAM for that peripheral. If any word fails the parity check, the module generates
a parity error signal that is mapped to the Error Signaling Module. The module also captures the
peripheral RAM address that caused the parity error.
The parity protection for peripheral RAMs is not enabled by default and must be enabled by the
application. Each individual peripheral contains control registers to enable the parity protection for
accesses to its RAM.
The CPU read access gets the actual data from the peripheral. The application can choose
to generate an interrupt whenever a peripheral RAM parity error is detected.
The PBIST ROM clock frequency is limited to 100 MHz, if 100 MHz < HCLK <= HCLKmax, or HCLK, if
HCLK <= 100 MHz.
The PBIST ROM clock is divided down from HCLK. The divider is selected by programming the ROM_DIV
field of the Memory Self-Test Global Control Register (MSTGCR) at address 0xFFFFFF58.
This microcontroller allows some of the on-chip memories to be initialized through the Memory Hardware
Initialization mechanism in the system module. This hardware mechanism allows an application to
program the memory arrays with error detection capability to a known state based on their error detection
scheme (odd/even parity or ECC).
The MINITGCR register enables the memory initialization sequence, and the MSINENA register selects
the memories that are to be initialized.
For more information on these registers, see the device-specific Technical Reference Manual.
The mapping of the different on-chip memories to the specific bits of the MSINENA registers is shown in
N2HET1 RAM0xFF4600000xFF47FFFF3
HET TU2 RAM0xFF4C00000xFF4DFFFF16
HET TU1 RAM0xFF4E00000xFF4FFFFF4
DMA RAM0xFFF800000xFFF80FFF1
VIM RAM0xFFF820000xFFF82FFF2
(1) The TCM RAM wrapper has separate control bits to select the RAM power domain that is to be auto-initialized.
(2) The MibSPIx modules perform an initialization of the transmit and receive RAMs as soon as the module is released from its local reset.
This is independent of whether the application chooses to initialize the MibSPIx RAMs using the system module auto-initialization
method. The MibSPIx module must be first brought out of its local reset to use the system module auto-initialization method.
The vectored interrupt manager (VIM) provides hardware assistance for prioritizing and controlling the
many interrupt sources present on this device. Interrupts are caused by events outside of the normal flow
of program execution. Normally, these events require a timely response from the CPU; therefore, when an
interrupt occurs, the CPU switches execution from the normal program flow to an interrupt service routine
(ISR).
6.14.1 VIM Features
The VIM module has the following features:
•Supports 128 interrupt channels.
– Provides programmable priority and enable for interrupt request lines.
•Provides a direct hardware dispatch mechanism for fastest IRQ dispatch.
•Provides two software dispatch mechanisms when the CPU VIC port is not used.
– Index interrupt
– Register vectored interrupt
•Parity protected vector interrupt table against soft errors.
Address location 0x00000000 in the VIM RAM is reserved for the phantom interrupt ISR
entry; therefore only request channels 0..126 can be used and are offset by one address in
the VIM RAM.
The lower-order interrupt channels are higher priority channels than the higher-order interrupt
channels.
The application can change the mapping of interrupt sources to the interrupt channels
through the interrupt channel control registers (CHANCTRLx) inside the VIM module.
The DMA controller is used to transfer data between two locations in the memory map in the background
of CPU operations. Typically, the DMA is used to:
•Transfer blocks of data between external and internal data memories
•Restructure portions of internal data memory
•Continually service a peripheral
6.15.1 DMA Features
•CPU independent data transfer
•One 64-bit master port that interfaces to the TMS570 Memory System.
•FIFO buffer (four entries deep and each 64 bits wide)
•Channel control information is stored in RAM protected by parity
•16 channels with individual enable
•Channel chaining capability
•32 peripheral DMA requests
•Hardware and software DMA requests
•8-, 16-, 32- or 64-bit transactions supported
•Multiple addressing modes for source/destination (fixed, increment, offset)
•Auto-initiation
•Power-management mode
•Memory Protection with four configurable memory regions
The DMA module on this microcontroller has 16 channels and up to 32 hardware DMA requests. The
module contains DREQASIx registers which are used to map the DMA requests to the DMA channels. By
default, channel 0 is mapped to request 0, channel 1 to request 1, and so on.
Some DMA requests have multiple sources, as shown in Table 6-28. The application must ensure that
only one of these DMA request sources is enabled at any time.
The real-time interrupt (RTI) module provides timer functionality for operating systems and for
benchmarking code. The RTI module can incorporate several counters that define the time bases needed
for scheduling an operating system.
The timers also let you benchmark certain areas of code by reading the values of the counters at the
beginning and the end of the desired code range and calculating the difference between the values.
6.16.1 Features
The RTI module has the following features:
•Two independent 64-bit counter blocks
•Four configurable compares for generating operating system ticks or DMA requests. Each event can
be driven by either counter block 0 or counter block 1.
•Fast enabling/disabling of events
•Two timestamp (capture) functions for system or peripheral interrupts, one for each counter block
6.16.2 Block Diagrams
Figure 6-11 shows a high-level block diagram for one of the two 64-bit counter blocks inside the RTI
module. Both the counter blocks are identical except the Network Time Unit (NTUx) inputs are only
available as time-base inputs for the counter block 0. Figure 6-12 shows the compare unit block diagram
of the RTI module.
The RTI module uses the RTI1CLK clock domain for generating the RTI time bases.
The application can select the clock source for the RTI1CLK by configuring the RCLKSRC register in the
system module at address 0xFFFFFF50. The default source for RTI1CLK is VCLK.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
Figure 6-12. Compare Block Diagram
For more information on clock sources, see Table 6-8 and Table 6-13.
6.16.4 Network Time Synchronization Inputs
The RTI module supports four Network Time Unit (NTU) inputs that signal internal system events, and
which can be used to synchronize the time base used by the RTI module. On this device, these NTU
inputs are connected as shown in Table 6-29.
The Error Signaling Module (ESM) manages the various error conditions on the TMS570 microcontroller.
The error condition is handled based on a fixed severity level assigned to it. Any severe error condition
can be configured to drive a low level on a dedicated device terminal called nERROR. The nERROR can
be used as an indicator to an external monitor circuit to put the system into a safe state.
6.17.1 ESM Features
The features of the ESM are:
•128 interrupt/error channels are supported, divided into three groups
– 64 channels with maskable interrupt and configurable error pin behavior
– 32 error channels with nonmaskable interrupt and predefined error pin behavior
– 32 channels with predefined error pin behavior only
•Error pin to signal severe device failure
•Configurable time base for error signal
•Error forcing capability
6.17.2 ESM Channel Assignments
The ESM integrates all the device error conditions and groups them in the order of severity. Group1 is
used for errors of the lowest severity while Group3 is used for errors of the highest severity. The device
response to each error is determined by the severity group it is connected to. Table 6-31 lists the channel
assignment for each group.
www.ti.com
Table 6-30. ESM Groups
ERROR GROUPINTERRUPT CHARACTERISTICS
Group1Maskable, low or high priorityConfigurable
Group2Nonmaskable, high priorityFixed
Group3No interrupt generatedFixed
detected in unprivileged mode
Power domain controller compare errorGroup138
Power domain controller self-test errorGroup139
eFuse Controller Error – this error signal is generated when any bit in the eFuse
controller error status register is set. The application can choose to generate an
interrupt whenever this bit is set to service any eFuse controller error conditions.
eFuse Controller - Self-Test Error. This error signal is generated only when a selftest on the eFuse controller generates an error condition. When an ECC self-test
error is detected, group 1 channel 40 error signal will also be set.
eFuse Controller Autoload errorUser/PrivilegeESM => nERROR3.1
eFuse Controller - Any bit set in the error status registerUser/PrivilegeESM1.40
eFuse Controller self-test errorUser/PrivilegeESM1.41
This device includes a Digital Windowed Watchdog (DWWD) module that protects against runaway code
execution (see Figure 6-13).
The DWWD module allows the application to configure the time window within which the DWWD module
expects the application to service the watchdog. A watchdog violation occurs if the application services the
watchdog outside of this window, or fails to service the watchdog at all. The application can choose to
generate a system reset or an ESM group2 error signal in case of a watchdog violation.
The watchdog is disabled by default and must be enabled by the application. Once enabled, the watchdog
can only be disabled upon a system reset.
The device contains an ICEPICK module (version C) to allow JTAG access to the scan chains (see
Figure 6-14).
www.ti.com
Figure 6-14. Debug Subsystem Block Diagram
6.20.2 Debug Components Memory Map
CoreSight Debug ROMCSCS00xFFA0_00000xFFA0_0FFF4KB4KBReads return zeros, writes have no effect
Cortex-R4F DebugCSCS10xFFA0_10000xFFA0_1FFF4KB4KBReads return zeros, writes have no effect
MODULE
NAME
Table 6-33. Debug Components Memory Map
FRAME CHIP
SELECT
6.20.3 JTAG Identification Code
The JTAG ID code for this device is the same as the device ICEPick Identification Code. For the JTAG ID
Code per silicon revision, see Table 6-34.
fRTCKRTCK frequency (at TCKmax and HCLKmax)10MHz
1td(TCK -RTCK)Delay time, TCK to RTCK24ns
2tsu(TDI/TMS - RTCKr)Setup time, TDI, TMS before RTCK rise (RTCKr)26ns
3th(RTCKr -TDI/TMS)Hold time, TDI, TMS after RTCKr0ns
4th(RTCKr -TDO)Hold time, TDO after RTCKf0ns
5td(TCKf -TDO)Delay time, TDO valid after RTCK fall (RTCKf)12ns
(1) Timings for TDO are specified for a maximum of 50-pF load on TDO.
This device includes a an Advanced JTAG Security Module (AJSM) module. The AJSM provides
maximum security to the memory content of the device by letting users secure the device after
programming.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
The device is unsecure by default by virtue of a 128-bit visible unlock code programmed in the OTP
address 0xF0000000. The OTP contents are XOR-ed with the contents of the "Unlock By Scan" register.
The outputs of these XOR gates are again combined with a set of secret internal tie-offs. The output of
this combinational logic is compared against a secret hard-wired 128-bit value. A match results in the
UNLOCK signal being asserted, so that the device is now unsecure.
A user can secure the device by changing at least 1 bit in the visible unlock code from 1 to 0. Changing a
0 to 1 is not possible because the visible unlock code is stored in the One Time Programmable (OTP)
flash region. Also, changing all 128 bits to zeros is not a valid condition and will permanently secure the
device.
Once secured, a user can unsecure the device by scanning an appropriate value into the "Unlock By
Scan" register of the AJSM module. This register is accessible by configuring an IR value of 0b1011 on
the AJSM TAP. The value to be scanned is such that the XOR of the OTP contents and the Unlock-ByScan register contents results in the original visible unlock code.
The Unlock-By-Scan register is reset only upon asserting power-on reset (nPORRST).
A secure device only permits JTAG accesses to the AJSM scan chain through the Secondary Tap 2 of the
ICEPick module. All other secondary taps, test taps, and the boundary scan interface are not accessible in
this state.
The device supports BSDL-compliant boundary scan for testing pin-to-pin compatibility. The boundary
scan chain is connected to the Boundary Scan Interface of the ICEPICK module (see Figure 6-17).
(1) This specification does not account for any output buffer drive strength differences or any external capacitive loading differences. Check
Table 4-40 for output buffer drive strength information on each signal.
Delay between low-to-high, or high-to-low transition of general-purpose output
signals that can be configured by an application in parallel, for example, all signals in
a GIOA port, or all N2HET1 signals, and so forth
The low-EMI output buffer has been designed explicitly to address the issue of decoupling sources of
emissions from the pins which they drive. This is accomplished by adaptively controlling the output buffer
impedance, and is particularly effective with capacitive loads.
This is not the default mode of operation of the low-EMI output buffers and must be enabled by setting the
system module GPCR1 register for the desired module or signal, as shown in Table 7-4. The adaptive
impedance control circuit monitors the DC bias point of the output signal. The buffer internally generates
two reference levels, VREFLOW and VREFHIGH, which are set to approximately 10% and 90% of
VCCIO, respectively.
Once the output buffer has driven the output to a low level, if the output voltage is below VREFLOW, then
the impedance of the output buffer will increase to Hi-Z. A high degree of decoupling between the internal
ground bus and the output pin will occur with capacitive loads, or any load in which no current is flowing,
for example, the buffer is driving low on a resistive path to ground. Current loads on the buffer which try to
pull the output voltage above VREFLOW will be opposed by the impedance of the output buffer so as to
maintain the output voltage at or below VREFLOW.
Conversely, once the output buffer has driven the output to a high level, if the output voltage is above
VREFHIGH then the output buffer impedance will again increase to Hi-Z. A high degree of decoupling
between internal power bus ad output pin will occur with capacitive loads or any loads in which no current
is flowing, for example, buffer is driving high on a resistive path to VCCIO. Current loads on the buffer
which try to pull the output voltage below VREFHIGH will be opposed by the output buffer impedance so
as to maintain the output voltage at or above VREFHIGH.
TMS570LS0714
SPNS226E –JUNE 2013–REVISED NOVEMBER 2016
The bandwidth of the control circuitry is relatively low, so that the output buffer in adaptive impedance
control mode cannot respond to high-frequency noise coupling into the power buses of the buffer. In this
manner, internal bus noise approaching 20% peak-to-peak of VCCIO can be rejected.
Unlike standard output buffers which clamp to the rails, an output buffer in impedance control mode will
allow a positive current load to pull the output voltage up to VCCIO + 0.6V without opposition. Also, a
negative current load will pull the output voltage down to VSSIO – 0.6V without opposition. This is not an
issue because the actual clamp current capability is always greater than the IOH / IOL specifications.
The low-EMI output buffers are automatically configured to be in the standard buffer mode when the
device enters a low-power mode.
Each ePWM module has a clock enable (EPWMxENCLK). When SYS_nRST is active-low, the clock
enables are ignored and the ePWM logic is clocked so that it can reset to a proper state. When
SYS_nRST goes in-active high, the state of clock enable is respected.
The default value of the control registers to enable the clocks to the ePWMx modules is 1. This means
that the VCLK4 clock connections to the ePWMx modules are enabled by default. The application can
choose to gate off the VCLK4 clock to any ePWMx module individually by clearing the respective control
register bit.
7.2.2Synchronization of ePWMx Time-Base Counters
A time-base synchronization scheme connects all of the ePWM modules on a device. Each ePWM
module has a synchronization input (EPWMxSYNCI) and a synchronization output (EPWMxSYNCO). The
input synchronization for the first instance (ePWM1) comes from an external pin. Figure 7-3 shows the
synchronization connections for all the ePWMx modules. Each ePWM module can be configured to use or
ignore the synchronization input. For more information, see the ePWM chapter in the device-specific
Technical Reference Manual (TRM).
7.2.3Synchronizing all ePWM Modules to the N2HET1 Module Time Base
DEFAULT VALUE
The connection between the N2HET1_LOOP_SYNC and SYNCI input of ePWM1 module is implemented
as shown in Figure 7-5.
Submit Documentation Feedback
Product Folder Links: TMS570LS0714
98
Figure 7-5. Synchronizing Time Bases Between N2HET1, N2HET2 and ePWMx Modules
7.2.4Phase-Locking the Time-Base Clocks of Multiple ePWM Modules
The TBCLKSYNC bit can be used to globally synchronize the time-base clocks of all enabled ePWM
modules on a device. This bit is implemented as PINMMR37 register bit 1.
When TBCLKSYNC = 0, the time-base clock of all ePWM modules is stopped. This is the default
condition.
When TBCLKSYNC = 1, all ePWM time-base clocks are started with the rising edge of TBCLK aligned.
For perfectly synchronized TBCLKs, the prescaler bits in the TBCTL register of each ePWM module must
be set identically. The proper procedure for enabling the ePWM clocks is as follows:
1. Enable the individual ePWM module clocks (if disable) using the control registers shown in Table 7-5.
2. Configure TBCLKSYNC = 0. This will stop the time-base clock within any enabled ePWM module.
3. Configure the prescaler values and desired ePWM modes.
4. Configure TBCLKSYNC = 1.
7.2.5ePWM Synchronization with External Devices
The output sync from the ePWM1 module is also exported to a device output terminal so that multiple
devices can be synchronized together. The signal pulse is stretched by eight VCLK4 cycles before being
exported on the terminal as the EPWM1SYNCO signal.
TMS570LS0714
7.2.6ePWM Trip Zones
7.2.6.1Trip Zones TZ1n, TZ2n, TZ3n
These three trip zone inputs are driven by external circuits and are connected to device-level inputs.
These signals are either connected asynchronously to the ePWMx trip zone inputs, or doublesynchronized with VCLK4, or double-synchronized and then filtered with a 6-cycle VCLK4-based counter
before connecting to the ePWMx (see Figure 7-4). By default, the trip zone inputs are asynchronously
connected to the ePWMx modules.
Table 7-6. Connection to ePWMx Modules for Device-Level Trip Zone Inputs
This trip zone input is dedicated to eQEPx error indications. There are two eQEP modules on this device.
Each eQEP module indicates a phase error by driving its EQEPxERR output High. The following control
registers allow the application to configure the trip zone input (TZ4n) to each ePWMx module based on
the requirements of the application.
This trip zone input is dedicated to a clock failure on the device. That is, this trip zone input is asserted
whenever an oscillator failure or a PLL slip is detected on the device. The application can use this trip
zone input for each ePWMx module to prevent the external system from going out of control when the
device clocks are not within expected range (system running at limp clock).
The oscillator failure and PLL slip signals used for this trip zone input are taken from the status flags in the
system module. These level signals are set until cleared by the application.
7.2.6.4Trip Zone TZ6n
This trip zone input to the ePWMx modules is dedicated to a debug mode entry of the CPU. If enabled,
the user can force the PWM outputs to a known state when the emulator stops the CPU. This prevents the
external system from going out of control when the CPU is stopped.
7.2.7Triggering of ADC Start of Conversion Using ePWMx SOCA and SOCB Outputs
A special scheme is implemented to select the actual signal used for triggering the start of conversion on
the two ADCs on this device. This scheme is defined in Section 7.5.2.3.