Check for Samples: TMS320F28030, TMS320F28031, TMS320F28032, TMS320F28033, TMS320F28034, TMS320F28035
1TMS320F2803x ( Piccolo™) MCUs
1.1Features
123
• Highlights
– High-Efficiency 32-Bit CPU ( TMS320C28x™)
– 60-MHz Device
– Single 3.3-V Supply
– Integrated Power-on and Brown-out Resets
– Two Internal Zero-pin Oscillators
– Up to 45 Multiplexed GPIO Pins
– Three 32-Bit CPU Timers
– On-Chip Flash, SARAM, OTP Memory
– Code-Security Module
– Serial Port Peripherals
(SCI/SPI/I2C/LIN/eCAN)
– Enhanced Control Peripherals
•Enhanced Pulse Width Modulator (ePWM)
•High-Resolution PWM (HRPWM)
•Enhanced Capture (eCAP)
•Enhanced Quadrature Encoder Pulse
(eQEP)
•Analog-to-Digital Converter (ADC)
•On-Chip Temperature Sensor
•Comparator
– 64-Pin and 80-Pin Packages
• High-Efficiency 32-Bit CPU ( TMS320C28x™)
– 60 MHz (16.67-ns Cycle Time)
– 16 x 16 and 32 x 32 MAC Operations
– 16 x 16 Dual MAC
– Harvard Bus Architecture
– Atomic Operations
– Fast Interrupt Response and Processing
– Unified Memory Programming Model
– Code-Efficient (in C/C++ and Assembly)
• Programmable Control Law Accelerator (CLA)
– 32-Bit Floating-Point Math Accelerator
– Executes Code Independently of the Main
CPU
• Low Device and System Cost:
– Single 3.3-V Supply
– No Power Sequencing Requirement
– Integrated Power-on Reset and Brown-out
• Serial Port Peripherals
– One SCI (UART) Module
– Two SPI Modules
– One Inter-Integrated-Circuit (I2C) Bus
– One Local Interconnect Network (LIN) Bus
– One Enhanced Controller Area Network
(eCAN) Bus
• Advanced Emulation Features
– Analysis and Breakpoint Functions
– Real-Time Debug via Hardware
• Community Resources
– TI E2E Community
– TI Embedded Processors Wiki
1
Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of Texas
Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet.
2Piccolo, TMS320C28x, C28x, TMS320C2000, Code Composer Studio, XDS510 are trademarks of Texas Instruments.
3All other trademarks are the property of their respective owners.
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testingof all parameters.
The F2803x Piccolo™ family of microcontrollers provides the power of the C28x™ core and Control Law
Accelerator (CLA) coupled with highly integrated control peripherals in low pin-count devices. This family
is code-compatible with previous C28x-based code, as well as providing a high level of analog integration.
An internal voltage regulator allows for single rail operation. Enhancements have been made to the
HRPWM module to allow for dual-edge control (frequency modulation). Analog comparators with internal
10-bit references have been added and can be routed directly to control the PWM outputs. The ADC
converts from 0 to 3.3-V fixed full scale range and supports ratio-metric V
REFHI/VREFLO
references. The
ADC interface has been optimized for low overhead/latency.
1.3Getting Started
This section gives a brief overview of the steps to take when first developing for a C28x device. For more
detail on each of these steps, see the following:
•Getting Started With TMS320C28x Digital Signal Controllers (literature number SPRAAM0).
•C2000 Getting Started Website (http://www.ti.com/c2000getstarted)
•TMS320F28x MCU Development and Experimenter's Kits (http://www.ti.com/f28xkits)
32-Bit CPU timers–333333
HiRES ePWM Channels1––67676767
Comparators with IntegratedDACs0333333
Inter-integrated circuit (I2C)0111111
Enhanced Controller AreaNetwork
(eCAN)
Local Interconnect Network(LIN)0111111
Serial Peripheral Interface(SPI)1121212121212
Serial Communications Interface
(SCI)
I/O pins
(shared)
External interrupts–333333
Supply voltage (nominal)–3.3 V3.3 V3.3 V3.3 V3.3 V3.3 V
Temperature
options
Product status
Channels141614161416141614161416
Temperature SensorYesYesYesYesYesYes
Dual
Sample-and-Hold
GPIO–334533453345334533453345
AIO–666666
T: –40°C to 105°C–YesYesYesYesYesYes
S: –40°C to 125°C–YesYesYesYesYesYes
Q: –40°C to 125°C
(3)
(1)
–YesYesYesYesYesYes
–1K1K1K1K1K1K
0111111
0111111
(2)
–YesYesYesYesYesYes
–TMSTMSTMSTMSTMSTMS
(1) A type change represents a major functional feature difference in a peripheral module. Within a peripheral type, there may be minor
differences between devices that do not affect the basic functionality of the module. These device-specific differences are listed in the
TMS320x28xx, 28xxx DSP Peripheral Reference Guide (literature number SPRU566) and in the peripheral reference guides.
(2) "Q" refers to Q100 qualification for automotive applications.
(3) See Section 5.1 , Device and Development Support Tool Nomenclature, for descriptions of device stages. The "TMS" product status
Table 2-2 describes the signals. With the exception of the JTAG pins, the GPIO function is the default at
reset, unless otherwise mentioned. The peripheral signals that are listed under them are alternate
functions. Some peripheral functions may not be available in all devices. See Table 2-1 for details. Inputs
are not 5-V tolerant. All GPIO pins are I/O/Z and have an internal pullup, which can be selectively
enabled/disabled on a per-pin basis. This feature only applies to the GPIO pins. The pullups on the PWM
pins are not enabled at reset. The pullups on other GPIO pins are enabled upon reset. The AIO pins do
not have an internal pullup.
Table 2-2. Terminal Functions
TERMINAL
NAME
TRST108Inormal device operation. An external pull-down resistor is required on this pin. The
TCKSee GPIO38ISee GPIO38. JTAG test clock with internal pullup (↑)
TMSSee GPIO36I
TDISee GPIO35I
TDOSee GPIO37O/Zregister (instruction or data) are shifted out of TDO on the falling edge of TCK. (8 mA
TEST23830I/OTest Pin. Reserved for TI. Must be left unconnected.
XCLKOUTSee GPIO18O/Z
XCLKINIpath must be disabled by bit 13 in the CLKCTL register.
X15241I
X25140O
PNPAG
PIN #PIN #
See GPIO19 and
GPIO38
I/O/ZDESCRIPTION
JTAG
JTAG test reset with internal pulldown. TRST, when driven high, gives the scan
system control of the operations of the device. If this signal is not connected or driven
low, the device operates in its functional mode, and the test reset signals are ignored.
NOTE: TRST is an active high test pin and must be maintained low at all times during
value of this resistor should be based on drive strength of the debugger pods
applicable to the design. A 2.2-kΩ resistor generally offers adequate protection. Since
this is application-specific, it is recommended that each target board be validated for
proper operation of the debugger and the application. (↓)
See GPIO36. JTAG test-mode select (TMS) with internal pullup. This serial control
input is clocked into the TAP controller on the rising edge of TCK. (↑)
See GPIO35. JTAG test data input (TDI) with internal pullup. TDI is clocked into the
selected register (instruction or data) on a rising edge of TCK. (↑)
See GPIO37. JTAG scan out, test data output (TDO). The contents of the selected
drive)
FLASH
CLOCK
See GPIO18. Output clock derived from SYSCLKOUT. XCLKOUT is either the same
frequency, one-half the frequency, or one-fourth the frequency of SYSCLKOUT. This
is controlled by bits 1:0 (XCLKOUTDIV) in the XCLK register. At reset, XCLKOUT =
SYSCLKOUT/4. The XCLKOUT signal can be turned off by setting XCLKOUTDIV
to 3. The mux control for GPIO18 must also be set to XCLKOUT for this signal to
propogate to the pin.
See GPIO19 and GPIO38. External oscillator input. Pin source for the clock is
controlled by the XCLKINSEL bit in the XCLK register, GPIO38 is the default
selection. This pin feeds a clock from an external 3.3-V oscillator. In this case, the X1
pin, if available, must be tied to GND and the on-chip crystal oscillator must be
disabled via bit 14 in the CLKCTL register. If a crystal/resonator is used, the XCLKIN
NOTE: Designs that use the GPIO38/TCK/XCLKIN pin to supply an external clock for
normal device operation may need to incorporate some hooks to disable this path
during debug using the JTAG connector. This is to prevent contention with the TCK
signal, which is active during JTAG debug sessions. The zero-pin internal oscillators
may be used during this time to clock the device.
On-chip crystal-oscillator input. To use this oscillator, a quartz crystal or a ceramic
resonator must be connected across X1 and X2. In this case, the XCLKIN path must
be disabled by bit 13 in the CLKCTL register. If this pin is not used, it must be tied to
GND. (I)
On-chip crystal-oscillator output. A quartz crystal or a ceramic resonator must be
connected across X1 and X2. If X2 is not used, it must be left unconnected. (O)
(1)
(1) I = Input, O = Output, Z = High Impedance, OD = Open Drain, ↑ = Pullup, ↓ = Pulldown
ADCINB12419IADC Group B, Channel 1 input
ADCINB02318
VREFLO2217NOTE: VREFLO is always connected to V
PNPAG
PIN #PIN #
I/O/ZDESCRIPTION
RESET
Device Reset (in) and Watchdog Reset (out). Piccolo devices have a built-in
power-on-reset (POR) and brown-out-reset (BOR) circuitry. As such, no external
circuitry is needed to generate a reset pulse. During a power-on or brown-out
condition, this pin is driven low by the device. See the electrical section for thresholds
of the POR/BOR block. This pin is also driven low by the MCU when a watchdog reset
occurs. During watchdog reset, the XRS pin is driven low for the watchdog reset
duration of 512 OSCCLK cycles. If need be, an external circuitry may also drive this
pin to assert a device reset. In this case, it is recommended that this pin be driven by
an open-drain device. An R-C circuit must be connected to this pin for noise immunity
reasons. Regardless of the source, a device reset causes the device to terminate
execution. The program counter points to the address contained at the location
0x3FFFC0. When reset is deactivated, execution begins at the location designated by
the program counter. The output buffer of this pin is an open-drain with an internal
pullup. (I/OD)
ADC, COMPARATOR, ANALOG I/O
I
I/O
ADC Group A, Channel 0 input.
use is mutually exclusive to one another.
ADC External Reference – only used when in ADC external reference mode. See
ADC Section..
NOTE: VREFHI and ADCINA0 share the same pin on the 64-pin PAG device and their
use is mutually exclusive to one another.
2016Analog Power Pin. Tie with a 2.2-mF capacitor (typical) close to the pin.
2117
Analog Ground Pin.
NOTE: VREFLO is always connected to V
on the 64-pin PAG device.
SSA
75CPU and Logic Digital Power Pins – no supply source needed when using internal
5443
7259
3629
7057
VREG. Tie with 1.2 µF (minimum) ceramic capacitor (10% tolerance) to ground when
using internal VREG. Higher value capacitors may be used, but could impact
supply-rail ramp-up time.
Digital I/O and Flash Power Pin – Single Supply source when VREG is enabled
86
3528
5342
Digital Ground Pins
7158
VOLTAGE REGULATOR CONTROL SIGNAL
VREGENZ7360IInternal VREG Enable/Disable – pull low to enable VREG, pull high to disable VREG
GPIO AND PERIPHERAL SIGNALS
(1)
GPIO06956I/O/ZGeneral purpose input/output 0
EPWM1AOEnhanced PWM1 Output A and HRPWM channel
–––
–––
GPIO16855I/O/ZGeneral purpose input/output 1
EPWM1BOEnhanced PWM1 Output B
––
COMP1OUTODirect output of Comparator 1
GPIO26754I/O/ZGeneral purpose input/output 2
EPWM2AOEnhanced PWM2 Output A and HRPWM channel
––
––
GPIO36653I/O/ZGeneral purpose input/output 3
EPWM2BOEnhanced PWM2 Output B
SPISOMIAI/OSPI-A slave out, master in
COMP2OUTODirect output of Comparator 2
GPIO46351I/O/ZGeneral purpose input/output 4
EPWM3AOEnhanced PWM3 output A and HRPWM channel
––
––
GPIO56250I/O/ZGeneral purpose input/output 5
EPWM3BOEnhanced PWM3 output B
SPISIMOAI/OSPI-A slave in, master out
ECAP1I/OEnhanced Capture input/output 1
(1) The GPIO function (shown in bold italics) is the default at reset. The peripheral signals that are listed under them are alternate functions.
For JTAG pins that have the GPIO functionality multiplexed, the input path to the GPIO block is always valid. The output path from the
GPIO block and the path to the JTAG block from a pin is enabled/disabled based on the condition of the TRST signal. See the
TMS320x2803x Piccolo System Control and Interrupts Reference Guide (literature number SPRUGL8) for details.
GPIO164636I/O/ZGeneral purpose input/output 16
SPISIMOAI/OSPI-A slave in, master out
––
TZ2ITrip Zone input 2
GPIO174234I/O/ZGeneral purpose input/output 17
SPISOMIAI/OSPI-A slave out, master in
––
TZ3ITrip zone input 3
GPIO184133I/O/ZGeneral purpose input/output 18
SPICLKAI/OSPI-A clock input/output
LINTXAOLIN transmit
XCLKOUTO/ZOutput clock derived from SYSCLKOUT. XCLKOUT is either the same frequency,
GPIO195544I/O/ZGeneral purpose input/output 19
XCLKINExternal Oscillator Input. The path from this pin to the clock block is not gated by the
one-half the frequency, or one-fourth the frequency of SYSCLKOUT. This is controlled
by bits 1:0 (XCLKOUTDIV) in the XCLK register. At reset, XCLKOUT =
SYSCLKOUT/4. The XCLKOUT signal can be turned off by setting XCLKOUTDIV
to 3. The mux control for GPIO18 must also be set to XCLKOUT for this signal to
propogate to the pin.
mux function of this pin. Care must be taken not to enable this path for clocking if it is
being used for the other periperhal functions
NOTE: The SPI-B peripheral is only available in the PN package.
GPIO375846I/O/ZGeneral-Purpose Input/Output 37
TDOO/ZJTAG scan out, test data output (TDO). The contents of the selected register
GPIO385745I/O/ZGeneral-Purpose Input/Output 38
TCKIJTAG test clock with internal pullup
XCLKINIExternal Oscillator Input. The path from this pin to the clock block is not gated by the
In Figure 3-2 through Figure 3-5, the following apply:
•Memory blocks are not to scale.
•Peripheral Frame 0, Peripheral Frame 1 and Peripheral Frame 2 memory maps are restricted to data
memory only. A user program cannot access these memory maps in program space.
•Protected means the order of Write-followed-by-Read operations is preserved rather than the pipeline
order.
•Certain memory ranges are EALLOW protected against spurious writes after configuration.
•Locations 0x3D7C80 – 0x3D7CC0 contain the internal oscillator and ADC calibration routines. These
locations are not programmable by the user.
Table 3-1. Addresses of Flash Sectors in F28034/28035
ADDRESS RANGEPROGRAM AND DATA SPACE
0x3E 8000 – 0x3E 9FFFSector H (8K x 16)
0x3E A000 – 0x3E BFFFSector G (8K x 16)
0x3E C000 – 0x3E DFFFSector F (8K x 16)
0x3E E000 – 0x3E FFFFSector E (8K x 16)
0x3F 0000 – 0x3F 1FFFSector D (8K x 16)
0x3F 2000 – 0x3F 3FFFSector C (8K x 16)
0x3F 4000 – 0x3F 5FFFSector B (8K x 16)
0x3F 6000 – 0x3F 7F7FSector A (8K x 16)
0x3F 7F80 – 0x3F 7FF5
0x3F 7FF6 – 0x3F 7FF7
0x3F 7FF8 – 0x3F 7FFF
Table 3-2. Addresses of Flash Sectors in F28031/28032/28033
ADDRESS RANGEPROGRAM AND DATA SPACE
0x3F 0000 – 0x3F 0FFFSector H (4K x 16)
0x3F 1000 – 0x3F 1FFFSector G (4K x 16)
0x3F 2000 – 0x3F 2FFFSector F (4K x 16)
0x3F 3000 – 0x3F 3FFFSector E (4K x 16)
0x3F 4000 – 0x3F 4FFFSector D (4K x 16)
0x3F 5000 – 0x3F 5FFFSector C (4K x 16)
0x3F 6000 – 0x3F 6FFFSector B (4K x 16)
0x3F 7000 – 0x3F 7F7FSector A (4K x 16)
0x3F 7F80 – 0x3F 7FF5
0x3F 7FF6 – 0x3F 7FF7
0x3F 7FF8 – 0x3F 7FFF
www.ti.com
Program to 0x0000 when using the
Code Security Module
Boot-to-Flash Entry Point
(program branch instruction here)
Security Password (128-Bit)
(Do not program to all zeros)
Program to 0x0000 when using the
Code Security Module
Boot-to-Flash Entry Point
(program branch instruction here)
Security Password (128-Bit)
(Do not program to all zeros)
Table 3-3. Addresses of Flash Sectors in F28030
ADDRESS RANGEPROGRAM AND DATA SPACE
0x3F 4000 – 0x3F 4FFFSector D (4K x 16)
0x3F 5000 – 0x3F 5FFFSector C (4K x 16)
0x3F 6000 – 0x3F 6FFFSector B (4K x 16)
0x3F 7000 – 0x3F 7F7FSector A (4K x 16)
•When the code-security passwords are programmed, all addresses between 0x3F 7F80
and 0x3F 7FF5 cannot be used as program code or data. These locations must be
programmed to 0x0000.
•If the code security feature is not used, addresses 0x3F 7F80 through 0x3F 7FEF may
be used for code or data. Addresses 0x3F 7FF0 – 0x3F 7FF5 are reserved for data and
should not contain program code.
Table 3-4 shows how to handle these memory locations.
Table 3-4. Impact of Using the Code Security Module
ADDRESS
0x3F 7F80 – 0x3F 7FEFApplication code and data
0x3F 7FF0 – 0x3F 7FF5Reserved for data only
CODE SECURITY ENABLEDCODE SECURITY DISABLED
Fill with 0x0000
FLASH
Peripheral Frame 1 and Peripheral Frame 2 are grouped together to enable these blocks to be write/read
peripheral block protected. The protected mode makes sure that all accesses to these blocks happen as
written. Because of the pipeline, a write immediately followed by a read to different memory locations, will
appear in reverse order on the memory bus of the CPU. This can cause problems in certain peripheral
applications where the user expected the write to occur first (as written). The CPU supports a block
protection mode where a region of memory can be protected so that operations occur as written (the
penalty is extra cycles are added to align the operations). This mode is programmable and by default, it
protects the selected zones.
The wait-states for the various spaces in the memory map area are listed in Table 3-5.
Table 3-5. Wait-States
AREAWAIT-STATES (CPU)COMMENTS
M0 and M1 SARAMs0-waitFixed
Peripheral Frame 00-wait
Peripheral Frame 10-wait (writes)Cycles can be extended by peripheral generated ready.
2-wait (reads)Back-to-back write operations to Peripheral Frame 1 registers will incur
Peripheral Frame 20-wait (writes)Fixed. Cycles cannot be extended by the peripheral.
2-wait (reads)
L0 SARAM0-wait data and programAssumes no CPU conflicts
L1 SARAM0-wait data and programAssumes no CPU conflicts
L2 SARAM0-wait data and programAssumes no CPU conflicts
L3 SARAM0-wait data and programAssumes no CPU conflicts
OTPProgrammableProgrammed via the Flash registers.
1-wait minimum1-wait is minimum number of wait states allowed.
FLASHProgrammableProgrammed via the Flash registers.
0-wait Paged min
1-wait Random min
Random ≥ Paged
FLASH Password16-wait fixedWait states of password locations are fixed.
The 2803x (C28x) family is a member of the TMS320C2000™ microcontroller (MCU) platform. The
C28x-based controllers have the same 32-bit fixed-point architecture as existing C28x MCUs. It is a very
efficient C/C++ engine, enabling users to develop not only their system control software in a high-level
language, but also enabling development of math algorithms using C/C++. The device is as efficient at
MCU math tasks as it is at system control tasks that typically are handled by microcontroller devices. This
efficiency removes the need for a second processor in many systems. The 32 x 32-bit MAC 64-bit
processing capabilities enable the controller to handle higher numerical resolution problems efficiently.
Add to this the fast interrupt response with automatic context save of critical registers, resulting in a device
that is capable of servicing many asynchronous events with minimal latency. The device has an
8-level-deep protected pipeline with pipelined memory accesses. This pipelining enables it to execute at
high speeds without resorting to expensive high-speed memories. Special branch-look-ahead hardware
minimizes the latency for conditional discontinuities. Special store conditional operations further improve
performance.
3.3.2Control Law Accelerator (CLA)
The C28x control law accelerator is a single-precision (32-bit) floating-point unit that extends the
capabilities of the C28x CPU by adding parallel processing. The CLA is an independent processor with its
own bus structure, fetch mechanism, and pipeline. Eight individual CLA tasks, or routines, can be
specified. Each task is started by software or a peripheral such as the ADC, an ePWM, or CPU Timer 0.
The CLA executes one task at a time to completion. When a task completes the main CPU is notified by
an interrupt to the PIE and the CLA automatically begins the next highest-priority pending task. The CLA
can directly access the ADC Result registers and the ePWM+HRPWM registers. Dedicated message
RAMs provide a method to pass additional data between the main CPU and the CLA.
www.ti.com
3.3.3Memory Bus (Harvard Bus Architecture)
As with many MCU-type devices, multiple busses are used to move data between the memories and
peripherals and the CPU. The memory bus architecture contains a program read bus, data read bus, and
data write bus. The program read bus consists of 22 address lines and 32 data lines. The data read and
write busses consist of 32 address lines and 32 data lines each. The 32-bit-wide data busses enable
single cycle 32-bit operations. The multiple bus architecture, commonly termed Harvard Bus, enables the
C28x to fetch an instruction, read a data value and write a data value in a single cycle. All peripherals and
memories attached to the memory bus prioritize memory accesses. Generally, the priority of memory bus
accesses can be summarized as follows:
Highest:Data Writes(Simultaneous data and program writes cannot occur on the
memory bus.)
Program Writes(Simultaneous data and program writes cannot occur on the
memory bus.)
Data Reads
Program Reads(Simultaneous program reads and fetches cannot occur on the
memory bus.)
Lowest:Fetches(Simultaneous program reads and fetches cannot occur on the
To enable migration of peripherals between various Texas Instruments (TI) MCU family of devices, the
devices adopt a peripheral bus standard for peripheral interconnect. The peripheral bus bridge multiplexes
the various busses that make up the processor Memory Bus into a single bus consisting of 16 address
lines and 16 or 32 data lines and associated control signals. Three versions of the peripheral bus are
supported. One version supports only 16-bit accesses (called peripheral frame 2). Another version
supports both 16- and 32-bit accesses (called peripheral frame 1).
3.3.5Real-Time JTAG and Analysis
The devices implement the standard IEEE 1149.1 JTAG
Additionally, the devices support real-time mode of operation allowing modification of the contents of
memory, peripheral, and register locations while the processor is running and executing code and
servicing interrupts. The user can also single step through non-time-critical code while enabling
time-critical interrupts to be serviced without interference. The device implements the real-time mode in
hardware within the CPU. This is a feature unique to the 28x family of devices, requiring no software
monitor. Additionally, special analysis hardware is provided that allows setting of hardware breakpoint or
data/address watch-points and generating various user-selectable break events when a match occurs.
These devices do not support boundary scan; however, IDCODE and BYPASS features are available if
the following considerations are taken into account. The IDCODE does not come by default. The user
needs to go through a sequence of SHIFT IR and SHIFT DR state of JTAG to get the IDCODE. For
BYPASS instruction, the first shifted DR value would be 1.
(1)
interface for in-circuit based debug.
3.3.6Flash
The F28035/34 devices contain 64K x 16 of embedded flash memory, segregated into eight 8K x 16
sectors. The F28033/32/31 devices contain 32K x 16 of embedded flash memory, segregated into eight
4K x 16 sectors. The F28030 device contains 16K x 16 of embedded flash memory, segregated into four
4K x 16 sectors. All devices also contain a single 1K x 16 of OTP memory at address range 0x3D 7800 –
0x3D 7BFF. The user can individually erase, program, and validate a flash sector while leaving other
sectors untouched. However, it is not possible to use one sector of the flash or the OTP to execute flash
algorithms that erase/program other sectors. Special memory pipelining is provided to enable the flash
module to achieve higher performance. The flash/OTP is mapped to both program and data space;
therefore, it can be used to execute code or store data information. Addresses 0x3F 7FF0 – 0x3F 7FF5
are reserved for data variables and should not contain program code.
NOTE
The Flash and OTP wait-states can be configured by the application. This allows applications
running at slower frequencies to configure the flash to use fewer wait-states.
Flash effective performance can be improved by enabling the flash pipeline mode in the
Flash options register. With this mode enabled, effective performance of linear code
execution will be much faster than the raw performance indicated by the wait-state
configuration alone. The exact performance gain when using the Flash pipeline mode is
application-dependent.
For more information on the Flash options, Flash wait-state, and OTP wait-state registers,
see the TMS320x2803x Piccolo System Control and Interrupts Reference Guide (literature
number SPRUGL8).
(1) IEEE Standard 1149.1-1990 Standard Test Access Port and Boundary Scan Architecture
All devices contain these two blocks of single access memory, each 1K x 16 in size. The stack pointer
points to the beginning of block M1 on reset. The M0 and M1 blocks, like all other memory blocks on C28x
devices, are mapped to both program and data space. Hence, the user can use M0 and M1 to execute
code or for data variables. The partitioning is performed within the linker. The C28x device presents a
unified memory map to the programmer. This makes for easier programming in high-level languages.
3.3.8L0 SARAM, and L1, L2, and L3 DPSARAMs
The device contains up to 8K x 16 of single-access RAM. To ascertain the exact size for a given device,
see the device-specific memory map figures in Section 3.2. This block is mapped to both program and
data space. Block L0 is 2K in size and is dual mapped to both program and data space. Blocks L1 and L2
are both 1K in size and are shared with the CLA which can ultilize these blocks for its data space. Block
L3 is 4K (2K on the 28031 device) in size and is shared with the CLA which can ultilize this block for its
program space. DPSARAM refers to the dual-port configuration of these blocks.
3.3.9Boot ROM
The Boot ROM is factory-programmed with boot-loading software. Boot-mode signals are provided to tell
the bootloader software what boot mode to use on power up. The user can select to boot normally or to
download new software from an external connection or to select boot software that is programmed in the
internal Flash/ROM. The Boot ROM also contains standard tables, such as SIN/COS waveforms, for use
in math-related algorithms.
www.ti.com
Table 3-6. Boot Mode Selection
MODEGPIO37/TDOTRSTMODE
3110GetMode
2100Wait (see Section 3.3.10 for description)
1010SCI
0000Parallel IO
EMUxx1Emulation Boot
GPIO34/COMP2OUT/
COMP3OUT
3.3.9.1Emulation Boot
When the emulator is connected, the GPIO37/TDO pin cannot be used for boot mode selection. In this
case, the boot ROM detects that an emulator is connected and uses the contents of two reserved SARAM
locations in the PIE vector table to determine the boot mode. If the content of either location is invalid,
then the Wait boot option is used. All boot mode options can be accessed in emulation boot.
3.3.9.2GetMode
The default behavior of the GetMode option is to boot to flash. This behavior can be changed to another
boot option by programming two locations in the OTP. If the content of either OTP location is invalid, then
boot to flash is used. One of the following loaders can be specified: SCI, SPI, I2C, CAN, or OTP.
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 flash, user OTP, or L0
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 (i.e., 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.
The solution is to use the Wait boot option. This will sit in a loop around a software breakpoint to allow an
emulator to be connected without tripping security. Piccolo devices do not support a hardware
wait-in-reset mode.
NOTE
•When the code-security passwords are programmed, all addresses between 0x3F7F80
and 0x3F7FF5 cannot be used as program code or data. These locations must be
programmed to 0x0000.
•If the code security feature is not used, addresses 0x3F7F80 through 0x3F7FEF may be
used for code or data. Addresses 0x3F7FF0 – 0x3F7FF5 are reserved for data and
should not contain program code.
The 128-bit password (at 0x3F 7FF8 – 0x3F 7FFF) must not be programmed to zeros. Doing
so would permanently lock the device.
Disclaimer
Code Security Module Disclaimer
THE CODE SECURITY MODULE (CSM) INCLUDED ON THIS DEVICE WAS DESIGNED
TO PASSWORD PROTECT THE DATA STORED IN THE ASSOCIATED MEMORY
(EITHER ROM OR FLASH) AND IS WARRANTED BY TEXAS INSTRUMENTS (TI), IN
ACCORDANCE WITH ITS STANDARD TERMS AND CONDITIONS, TO CONFORM TO
TI'S PUBLISHED SPECIFICATIONS FOR THE WARRANTY PERIOD APPLICABLE FOR
THIS DEVICE.
TI DOES NOT, HOWEVER, WARRANT OR REPRESENT THAT THE CSM CANNOT BE
COMPROMISED OR BREACHED OR THAT THE DATA STORED IN THE ASSOCIATED
MEMORY CANNOT BE ACCESSED THROUGH OTHER MEANS. MOREOVER, EXCEPT
AS SET FORTH ABOVE, TI MAKES NO WARRANTIES OR REPRESENTATIONS
CONCERNING THE CSM OR OPERATION OF THIS DEVICE, INCLUDING ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL TI BE LIABLE FOR ANY CONSEQUENTIAL, SPECIAL, INDIRECT,
INCIDENTAL, OR PUNITIVE DAMAGES, HOWEVER CAUSED, ARISING IN ANY WAY
OUT OF YOUR USE OF THE CSM OR THIS DEVICE, WHETHER OR NOT TI HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. EXCLUDED DAMAGES INCLUDE,
BUT ARE NOT LIMITED TO LOSS OF DATA, LOSS OF GOODWILL, LOSS OF USE OR
INTERRUPTION OF BUSINESS OR OTHER ECONOMIC LOSS.
www.ti.com
3.3.11Peripheral Interrupt Expansion (PIE) Block
The PIE block serves to multiplex numerous interrupt sources into a smaller set of interrupt inputs. The
PIE block can support up to 96 peripheral interrupts. On the F2803x, 54 of the possible 96 interrupts are
used by peripherals. The 96 interrupts are grouped into blocks of 8 and each group is fed into 1 of
12 CPU interrupt lines (INT1 to INT12). Each of the 96 interrupts is supported by its own vector stored in a
dedicated RAM block that can be overwritten by the user. The vector is automatically fetched by the CPU
on servicing the interrupt. It takes 8 CPU clock cycles to fetch the vector and save critical CPU registers.
Hence the CPU can quickly respond to interrupt events. Prioritization of interrupts is controlled in
hardware and software. Each individual interrupt can be enabled/disabled within the PIE block.
The devices support three masked external interrupts (XINT1–XINT3). Each of the interrupts can be
selected for negative, positive, or both negative and positive edge triggering and can also be
enabled/disabled. These interrupts also contain a 16-bit free running up counter, which is reset to zero
when a valid interrupt edge is detected. This counter can be used to accurately time stamp the interrupt.
There are no dedicated pins for the external interrupts. XINT1, XINT2, and XINT3 interrupts can accept
inputs from GPIO0–GPIO31 pins.
3.3.13Internal Zero Pin Oscillators, Oscillator, and PLL
The device can be clocked by either of the two internal zero-pin oscillators, an external oscillator, or by a
crystal attached to the on-chip oscillator circuit. A PLL is provided supporting up to 12 input-clock-scaling
ratios. The PLL ratios can be changed on-the-fly in software, enabling the user to scale back on operating
frequency if lower power operation is desired. Refer to the Electrical Specification section for timing
details. The PLL block can be set in bypass mode.
3.3.14Watchdog
Each device contains two watchdogs: CPU-Watchdog that monitors the core and NMI-Watchdog that is a
missing clock-detect circuit. The user software must regularly reset the CPU-watchdog counter within a
certain time frame; otherwise, the CPU-watchdog generates a reset to the processor. The CPU-watchdog
can be disabled if necessary. The NMI-Watchdog engages only in case of a clock failure and can either
generate an interrupt or a device reset.
3.3.15Peripheral Clocking
The clocks to each individual peripheral can be enabled/disabled to reduce power consumption when a
peripheral is not in use. Additionally, the system clock to the serial ports (except I2C) can be scaled
relative to the CPU clock.
3.3.16Low-power Modes
The devices are full static CMOS devices. Three low-power modes are provided:
IDLE:Place CPU in low-power mode. Peripheral clocks may be turned off selectively and
only those peripherals that need to function during IDLE are left operating. An
enabled interrupt from an active peripheral or the watchdog timer will wake the
processor from IDLE mode.
STANDBY: Turns off clock to CPU and peripherals. This mode leaves the oscillator and PLL
functional. An external interrupt event will wake the processor and the peripherals.
Execution begins on the next valid cycle after detection of the interrupt event
HALT:This mode basically shuts down the device and places it in the lowest possible power
consumption mode. If the internal zero-pin oscillators are used as the clock source,
the HALT mode turns them off, by default. To keep these oscillators from shutting
down, the INTOSCnHALTI bits in CLKCTL register may be used. The zero-pin
oscillators may thus be used to clock the CPU-watchdog in this mode. If the on-chip
crystal oscillator is used as the clock source, it is shut down in this mode. A reset or
an external signal (through a GPIO pin) or the CPU-watchdog can wake the device
from this mode.
The CPU clock (OSCCLK) and WDCLK should be from the same clock source before attempting to put
the device into HALT or STANDBY.
The device segregates peripherals into three sections. The mapping of peripherals is as follows:
PF0:PIE:PIE Interrupt Enable and Control Registers Plus PIE Vector Table
Flash:Flash Waitstate Registers
Timers:CPU-Timers 0, 1, 2 Registers
CSM:Code Security Module KEY Registers
ADC:ADC Result Registers
CLAControl Law Accelrator Registers and Message RAMs
PF1:GPIO:GPIO MUX Configuration and Control Registers
eCAN:Enhanced Control Area Network Configuration and Control Registers
LIN:Local Interconnect Network Configuration and Control Registers
ePWM:Enhanced Pulse Width Modulator Module and Registers
eCAP:Enhanced Capture Module and Registers
eQEP:Enhanced Quadrature Encoder Pulse Module and Registers
Comparators:Comparator Modules
PF2:SYS:System Control Registers
SCI:Serial Communications Interface (SCI) Control and RX/TX Registers
SPI:Serial Port Interface (SPI) Control and RX/TX Registers
ADC:ADC Status, Control, and Configuration Registers
I2C:Inter-Integrated Circuit Module and Registers
XINT:External Interrupt Registers
Most of the peripheral signals are multiplexed with general-purpose input/output (GPIO) signals. This
enables the user to use a pin as GPIO if the peripheral signal or function is not used. On reset, GPIO pins
are configured as inputs. The user can individually program each pin for GPIO mode or peripheral signal
mode. For specific inputs, the user can also select the number of input qualification cycles. This is to filter
unwanted noise glitches. The GPIO signals can also be used to bring the device out of specific low-power
modes.
3.3.1932-Bit CPU-Timers (0, 1, 2)
CPU-Timers 0, 1, and 2 are identical 32-bit timers with presettable periods and with 16-bit clock
prescaling. The timers have a 32-bit count-down register, which generates an interrupt when the counter
reaches zero. The counter is decremented at the CPU clock speed divided by the prescale value setting.
When the counter reaches zero, it is automatically reloaded with a 32-bit period value.
CPU-Timer 0 is for general use and is connected to the PIE block. CPU-Timer 1 is also for general use
and can be connected to INT13 of the CPU. CPU-Timer 2 is reserved for DSP/BIOS. It is connected to
INT14 of the CPU. If DSP/BIOS is not being used, CPU-Timer 2 is available for general use.
CPU-Timer 2 can be clocked by any one of the following:
generation, adjustable dead-band generation for leading/trailing edges,
latched/cycle-by-cycle trip mechanism. Some of the PWM pins support the
HRPWM high resolution duty and period features. The type 1 module found on
2803x devices also supports increased dead-band resolution, enhanced SOC and
interrupt generation, and advanced triggering including trip functions based on
comparator outputs.
eCAP:The enhanced capture peripheral uses a 32-bit time base and registers up to four
programmable events in continuous/one-shot capture modes.
This peripheral can also be configured to generate an auxiliary PWM signal.
eQEP:The enhanced QEP peripheral uses a 32-bit position counter, supports low-speed
measurement using capture unit and high-speed measurement using a 32-bit unit
timer. This peripheral has a watchdog timer to detect motor stall and input error
detection logic to identify simultaneous edge transition in QEP signals.
ADC:The ADC block is a 12-bit converter. It has up to 13 single-ended channels pinned
out, depending on the device. It contains two sample-and-hold units for
simultaneous sampling.
Comparator:Each comparator block consists of one analog comparator along with an internal
10-bit reference for supplying one input of the comparator.
3.3.21Serial Port Peripherals
The devices support the following serial communication peripherals:
SPI:The SPI is a high-speed, synchronous serial I/O port that allows a serial bit stream
of programmed length (one to sixteen bits) to be shifted into and out of the device
at a programmable bit-transfer rate. Normally, the SPI is used for communications
between the MCU and external peripherals or another processor. Typical
applications include external I/O or peripheral expansion through devices such as
shift registers, display drivers, and ADCs. Multi-device communications are
supported by the master/slave operation of the SPI. The SPI contains a 4-level
receive and transmit FIFO for reducing interrupt servicing overhead.
SCI:The serial communications interface is a two-wire asynchronous serial port,
commonly known as UART. The SCI contains a 4-level receive and transmit FIFO
for reducing interrupt servicing overhead.
I2C:The inter-integrated circuit (I2C) module provides an interface between a MCU
and other devices compliant with Philips Semiconductors Inter-IC bus (I2C-bus)
specification version 2.1 and connected by way of an I2C-bus. External
components attached to this 2-wire serial bus can transmit/receive up to 8-bit data
to/from the MCU through the I2C module. The I2C contains a 4-level receive and
transmit FIFO for reducing interrupt servicing overhead.
eCAN:This is the enhanced version of the CAN peripheral. It supports 32 mailboxes, time
stamping of messages, and is CAN 2.0B-compliant.
LIN:LIN 1.3 or 2.0 compatible peripheral. Can also be configured as additional SCI
(0 wait read only)
CPU–TIMER0/1/2 Registers0x00 0C00 – 0x00 0C3F64No
PIE Registers0x00 0CE0 – 0x00 0CFF32No
PIE Vector Table0x00 0D00 – 0x00 0DFF256No
CLA Registers0x00 1400 – 0x00 147F128Yes
CLA to CPU Message RAM (CPU writes ignored)0x00 1480 – 0x00 14FF128NA
CPU to CLA Message RAM (CLA writes ignored)0x00 1500 – 0x00 157F128NA
(1) Registers in Frame 0 support 16-bit and 32-bit accesses.
(2) If registers are EALLOW protected, then writes cannot be performed until the EALLOW instruction is executed. The EDIS instruction
disables writes to prevent stray code or pointers from corrupting register contents.
(3) The Flash Registers are also protected by the Code Security Module (CSM).
(1) Some registers are EALLOW protected. See the module reference guide for more information.
(1)
(1)
3.5Device Emulation Registers
These registers are used to control the protection mode of the C28x CPU and to monitor some critical
device signals. The registers are defined in Table 3-11 .
Table 3-11. Device Emulation Registers
NAMESIZE (x16)DESCRIPTION
DEVICECNF2Device Configuration RegisterYes
PARTID
CLASSID0x08821Class ID RegisterTMS320F280350x00BF
REVID0x08831Revision ID
(1) For TMS320F2803x devices, the PARTID register location differs from the TMS320F2802x devices' location of 0x3D7FFF.
Eight PIE block interrupts are grouped into one CPU interrupt. In total, 12 CPU interrupt groups, with
8 interrupts per group equals 96 possible interrupts. Table 3-12 shows the interrupts used by 2803x
devices.
The TRAP #VectorNumber instruction transfers program control to the interrupt service routine
corresponding to the vector specified. TRAP #0 attempts to transfer program control to the address
pointed to by the reset vector. The PIE vector table does not, however, include a reset vector. Therefore,
TRAP #0 should not be used when the PIE is enabled. Doing so will result in undefined behavior.
When the PIE is enabled, TRAP #1 through TRAP #12 will transfer program control to the interrupt service
routine corresponding to the first vector within the PIE group. For example: TRAP #1 fetches the vector
from INT1.1, TRAP #2 fetches the vector from INT2.1, and so forth.
Figure 3-7. Multiplexing of Interrupts Using the PIE Block
(1) Out of 96 possible interrupts, some interrupts are not used. These interrupts are reserved for future devices. These interrupts can be
used as software interrupts if they are enabled at the PIEIFRx level, provided none of the interrupts within the group is being used by a
peripheral. Otherwise, interrupts coming in from peripherals may be lost by accidentally clearing their flag while modifying the PIEIFR.
To summarize, there are two safe cases when the reserved interrupts could be used as software interrupts:
• No peripheral within the group is asserting interrupts.
• No peripheral interrupts are assigned to the group (e.g., PIE group 7).
Table 3-13. PIE Configuration and Control Registers
NAMEADDRESSSIZE (x16)DESCRIPTION
PIECTRL0x0CE01PIE, Control Register
PIEACK0x0CE11PIE, Acknowledge Register
PIEIER10x0CE21PIE, INT1 Group Enable Register
PIEIFR10x0CE31PIE, INT1 Group Flag Register
PIEIER20x0CE41PIE, INT2 Group Enable Register
PIEIFR20x0CE51PIE, INT2 Group Flag Register
PIEIER30x0CE61PIE, INT3 Group Enable Register
PIEIFR30x0CE71PIE, INT3 Group Flag Register
PIEIER40x0CE81PIE, INT4 Group Enable Register
PIEIFR40x0CE91PIE, INT4 Group Flag Register
PIEIER50x0CEA1PIE, INT5 Group Enable Register
PIEIFR50x0CEB1PIE, INT5 Group Flag Register
PIEIER60x0CEC1PIE, INT6 Group Enable Register
PIEIFR60x0CED1PIE, INT6 Group Flag Register
PIEIER70x0CEE1PIE, INT7 Group Enable Register
PIEIFR70x0CEF1PIE, INT7 Group Flag Register
PIEIER80x0CF01PIE, INT8 Group Enable Register
PIEIFR80x0CF11PIE, INT8 Group Flag Register
PIEIER90x0CF21PIE, INT9 Group Enable Register
PIEIFR90x0CF31PIE, INT9 Group Flag Register
PIEIER100x0CF41PIE, INT10 Group Enable Register
PIEIFR100x0CF51PIE, INT10 Group Flag Register
PIEIER110x0CF61PIE, INT11 Group Enable Register
PIEIFR110x0CF71PIE, INT11 Group Flag Register
PIEIER120x0CF81PIE, INT12 Group Enable Register
PIEIFR120x0CF91PIE, INT12 Group Flag Register
Reserved0x0CFA –6Reserved
0x0CFF
(1) The PIE configuration and control registers are not protected by EALLOW mode. The PIE vector table
Each external interrupt can be enabled/disabled or qualified using positive, negative, or both positive and
negative edge. For more information, see the TMS320x2803x Piccolo System Control and InterruptsReference Guide (literature number SPRUGL8).
3.7VREG/BOR/POR
Although the core and I/O circuitry operate on two different voltages, these devices have an on-chip
voltage regulator (VREG) to generate the VDDvoltage from the V
supply. This eliminates the cost and
DDIO
space of a second external regulator on an application board. Additionally, internal power-on reset (POR)
and brown-out reset (BOR) circuits monitor both the VDDand V
rails during power-up and run mode.
DDIO
3.7.1On-chip Voltage Regulator (VREG)
A linear regulator generates the core voltage (VDD) from the V
are required on each VDDpin to stabilize the generated voltage, power need not be supplied to these pins
to operate the device. Conversely, the VREG can be disabled, should power or redundancy be the
primary concern of the application.
3.7.1.1Using the On-chip VREG
To utilize the on-chip VREG, the VREGENZ pin should be tied low and the appropriate recommended
operating voltage should be supplied to the V
DDIO
and V
DDA
the core logic will be generated by the VREG. Each VDDpin requires on the order of 1.2 mF (minimum)
capacitance for proper regulation of the VREG. These capacitors should be located as close as possible
to the VDDpins.
supply. Therefore, although capacitors
DDIO
pins. In this case, the VDDvoltage needed by
www.ti.com
3.7.1.2Disabling the On-chip VREG
To conserve power, it is also possible to disable the on-chip VREG and supply the core logic voltage to
the VDDpins with a more efficient external regulator. To enable this option, the VREGENZ pin must be tied
high.
3.7.2On-chip Power-On Reset (POR) and Brown-Out Reset (BOR) Circuit
Two on-chip supervisory circuits, the power-on reset (POR) and the brown-out reset (BOR) remove the
burden of monitoring the VDDand V
to create a clean reset throughout the device during the entire power-up procedure. The trip point is a
looser, lower trip point than the BOR, which watches for dips in the VDDor V
operation. The POR function is present on both VDDand V
power-up, the BOR function is present on V
enabled (VREGENZ pin is tied low). Both functions tie the XRS pin low when one of the voltages is below
their respective trip point. Additionally, when the internal voltage regulator is enabled, an over-voltage
protection circuit will tie XRS low if the VDDrail rises above its trip point. See Section 6 for the various trip
points as well as the delay time for the device to release the XRS pin after the under/over-voltage
condition is removed. Figure 3-8 shows the VREG, POR, and BOR. To disable both the VDDand V
BOR functions, a bit is provided in the BORCFG register. Refer to the TMS320x2803x Piccolo SystemControl and Interrupts Reference Guide (literature number SPRUGL8) for details.
supply rails from the application board. The purpose of the POR is
The F2803x devices contain two independent internal zero pin oscillators. By default both oscillators are
turned on at power up, and internal oscillator 1 is the default clock source at this time. For power savings,
unused oscillators may be powered down by the user. The center frequency of these oscillators is
determined by their respective oscillator trim registers, written to in the calibration routine as part of the
boot ROM execution. See the electrical section for more information on these oscillators.
3.8.2Crystal Oscillator Option
The typical specifications for the external quartz crystal (fundamental mode, parallel resonant) are listed in
Table 3-16. Furthermore, ESR range = 30 to 150 Ω.
Table 3-16. Typical Specifications for External Quartz Crystal
1. CL1and CL2are the total capacitance of the circuit board and components excluding the
IC and crystal. The value is usually approximately twice the value of the crystal's load
capacitance.
2. The load capacitance of the crystal is described in the crystal specifications of the
manufacturers.
3. TI recommends that customers have the resonator/crystal vendor characterize the
operation of their device with the MCU chip. The resonator/crystal vendor has the
equipment and expertise to tune the tank circuit. The vendor can also advise the
customer regarding the proper tank component values that will produce proper start up
and stability over the entire operating range.
The devices have an on-chip, PLL-based clock module. This module provides all the necessary clocking
signals for the device, as well as control for low-power mode entry. The PLL has a 4-bit ratio control
PLLCR[DIV] to select different CPU clock rates. The watchdog module should be disabled before writing
to the PLLCR register. It can be re-enabled (if need be) after the PLL module has stabilized, which takes
1 ms. The input clock and PLLCR[DIV] bits should be chosen in such a way that the output frequency of
the PLL (VCOCLK) is at least 50 MHz.
The PLL-based clock module provides four modes of operation:
•INTOSC1 (Internal Zero-pin Oscillator 1): This is the on-chip internal oscillator 1. This can provide
the clock for the Watchdog block, core and CPU-Timer 2
•INTOSC2 (Internal Zero-pin Oscillator 2): This is the on-chip internal oscillator 2. This can provide
the clock for the Watchdog block, core and CPU-Timer 2. Both INTOSC1 and INTOSC2 can be
independently chosen for the Watchdog block, core and CPU-Timer 2.
•Crystal/Resonator Operation: The on-chip (crystal) oscillator enables the use of an external
crystal/resonator attached to the device to provide the time base. The crystal/resonator is connected to
the X1/X2 pins. Some devices may not have the X1/X2 pins. See for details.
•External Clock Source Operation: If the on-chip (crystal) oscillator is not used, this mode allows it to
be bypassed. The device clocks are generated from an external clock source input on the XCLKIN pin.
Note that the XCLKIN is multiplexed with GPIO19 or GPIO38 pin. The XCLKIN input can be selected
as GPIO19 or GPIO38 via the XCLKINSEL bit in XCLK register. The CLKCTL[XCLKINOFF] bit
disables this clock input (forced low). If the clock source is not used or the respective pins are used as
GPIOs, the user should disable at boot time.
Before changing clock sources, ensure that the target clock is present. If a clock is not present, then that
clock source must be disabled (using the CLKCTL register) before switching clocks.
Table 3-19. Possible PLL Configuration Modes
PLL MODEREMARKSPLLSTS[DIVSEL]
Invoked by the user setting the PLLOFF bit in the PLLSTS register. The PLL block
PLL Offpower operation. The PLLCR register must first be set to 0x0000 (PLL Bypass)2OSCCLK/2
PLL Bypass2OSCCLK/2
PLL Enable2OSCCLK * n/2
is disabled in this mode. This can be useful to reduce system noise and for low0, 1OSCCLK/4
before entering this mode. The CPU clock (CLKIN) is derived directly from the3OSCCLK/1
input clock on either X1/X2, X1 or XCLKIN.
PLL Bypass is the default PLL configuration upon power-up or after an external
reset (XRS). This mode is selected when the PLLCR register is set to 0x0000 or
while the PLL locks to a new frequency after the PLLCR register has been
modified. In this mode, the PLL itself is bypassed but the PLL is not turned off.
Achieved by writing a non-zero value n into the PLLCR register. Upon writing to the
PLLCR the device will switch to PLL Bypass mode until the PLL locks.
0, 1OSCCLK/4
3OSCCLK/1
0, 1OSCCLK * n/4
3OSCCLK * n/1
CLKIN AND
SYSCLKOUT
3.8.4Loss of Input Clock (NMI Watchdog Function)
The2803xdevicesmaybeclockedfromeitheroneoftheinternalzero-pinoscillators
(INTOSC1/INTOSC2), the on-chip crystal oscillator, or from an external clock input. Regardless of the
clock source, in PLL-enabled and PLL-bypass mode, if the input clock to the PLL vanishes, the PLL will
issue a limp-mode clock at its output. This limp-mode clock continues to clock the CPU and peripherals at
a typical frequency of 1–5 MHz.
When the limp mode is activated, a CLOCKFAIL signal is generated that is latched as an NMI interrupt.
Depending on how the NMIRESETSEL bit has been configured, a reset to the device can be fired
immediately or the NMI watchdog counter can issue a reset when it overflows. In addition to this, the
Missing Clock Status (MCLKSTS) bit is set. The NMI interrupt could be used by the application to detect
the input clock failure and initiate necessary corrective action such as switching over to an alternative
clock source (if available) or initiate a shut-down procedure for the system.
If the software does not respond to the clock-fail condition, the NMI watchdog triggers a reset after a
preprogrammed time interval. Figure 3-13 shows the interrupt mechanisms involved.
The CPU-watchdog module on the 2803x device is similar to the one used on the 281x/280x/283xx
devices. This module generates an output pulse, 512 oscillator clocks wide (OSCCLK), whenever the 8-bit
watchdog up counter has reached its maximum value. To prevent this, the user must disable the counter
or the software must periodically write a 0x55 + 0xAA sequence into the watchdog key register that resets
the watchdog counter. Figure 3-14 shows the various functional blocks within the watchdog module.
Normally, when the input clocks are present, the CPU-watchdog counter decrements to initiate a
CPU-watchdog reset or WDINT interrupt. However, when the external input clock fails, the CPU-watchdog
counter stops decrementing (i.e., the watchdog counter does not change with the limp-mode clock).
NOTE
The CPU-watchdog is different from the NMI watchdog. It is the legacy watchdog that is
present in all 28x devices.
Applications in which the correct CPU operating frequency is absolutely critical should
implement a mechanism by which the MCU will be held in reset, should the input clocks ever
fail. For example, an R-C circuit may be used to trigger the XRS pin of the MCU, should the
capacitor ever get fully charged. An I/O pin may be used to discharge the capacitor on a
periodic basis to prevent it from getting fully charged. Such a circuit would also help in
detecting failure of the flash memory.
A.The WDRST signal is driven low for 512 OSCCLK cycles.
Figure 3-14. CPU-watchdog Module
SPRS584D–APRIL 2009–REVISED JUNE 2010
The WDINT signal enables the watchdog to be used as a wakeup from IDLE/STANDBY mode.
In STANDBY mode, all peripherals are turned off on the device. The only peripheral that remains
functional is the CPU-watchdog. This module will run off OSCCLK. The WDINT signal is fed to the LPM
block so that it can wake the device from STANDBY (if enabled). See Section 3.9, Low-power Modes
Block, for more details.
In IDLE mode, the WDINT signal can generate an interrupt to the CPU, via the PIE, to take the CPU out of
IDLE mode.
In HALT mode, the CPU-watchdog can be used to wake up the device through a device reset.
(1) The Exit column lists which signals or under what conditions the low power mode is exited. A low signal, on any of the signals, exits the
low power condition. This signal must be kept low long enough for an interrupt to be recognized by the device. Otherwise, the low-power
mode will not be exited and the device will go back into the indicated low power mode.
(2) The JTAG port can still function even if the CPU clock (CLKIN) is turned off.
(3) The WDCLK must be active for the device to go into HALT mode.
1XPLL turned off, zero-pin oscillatorOffOff
(CPU-watchdog still running)Port A signal, debugger
(on-chip crystal oscillator and
and CPU-watchdog state
dependent on user code.)
OnXRS, CPU-watchdog interrupt, GPIO
Off
XRS, CPU-watchdog interrupt, any
enabled interrupt
XRS, GPIO Port A signal, debugger
CPU-watchdog
The various low-power modes operate as follows:
IDLE Mode:This mode is exited by any enabled interrupt that is recognized by the
processor. The LPM block performs no tasks during this mode as long as
the LPMCR0(LPM) bits are set to 0,0.
STANDBY Mode:Any GPIO port A signal (GPIO[31:0]) can wake the device from STANDBY
mode. The user must select which signal(s) will wake the device in the
GPIOLPMSEL register. The selected signal(s) are also qualified by the
OSCCLK before waking the device. The number of OSCCLKs is specified in
the LPMCR0 register.
HALT Mode:CPU-watchdog, XRS, and any GPIO port A signal (GPIO[31:0]) can wake
the device from HALT mode. The user selects the signal in the
GPIOLPMSEL register.
(1)
(2)
(2)
,
NOTE
The low-power modes do not affect the state of the output pins (PWM pins included). They
will be in whatever state the code left them in when the IDLE instruction was executed. See
the TMS320x2803x Piccolo System Control and Interrupts Reference Guide (literature
number SPRUGL8) for more details.
The control law accelerator extends the capabilities of the C28x CPU by adding parallel processing.
Time-critical control loops serviced by the CLA can achieve low ADC sample to output delay. Thus, the
CLA enables faster system response and higher frequency control loops. Utilizing the CLA for time-critical
tasks frees up the main CPU to perform other system and communication functions concurently. The
following is a list of major features of the CLA.
•Clocked at the same rate as the main CPU (SYSCLKOUT).
•An independent architecture allowing CLA algorithm execution independent of the main C28x CPU.
– Complete bus architecture:
•Program address bus and program data bus
•Data address bus, data read bus, and data write bus
– Independent eight-stage pipeline.
– 12-bit program counter (MPC)
– Four 32-bit result registers (MR0–MR3)
– Two 16-bit auxillary registers (MAR0, MAR1)
– Status register (MSTF)
•Instruction set includes:
– IEEE single-precision (32-bit) floating-point math operations
– Floating-point math with parallel load or store
– Floating-point multiply with parallel add or subtract
– 1/X and 1/sqrt(X) estimations
– Data type conversions.
– Conditional branch and call
– Data load/store operations
•The CLA program code can consist of up to eight tasks or interrupt service routines.
– The start address of each task is specified by the MVECT registers.
– No limit on task size as long as the tasks fit within the CLA program memory space.
– One task is serviced at a time through to completion. There is no nesting of tasks.
– Upon task completion, a task-specific interrupt is flagged within the PIE.
– When a task finishes, the next highest-priority pending task is automatically started.
•Task trigger mechanisms:
– C28x CPU via the IACK instruction
– Task1 to Task7: the corresponding ADC or ePWM module interrupt. For example:
•Task1: ADCINT1 or EPWM1_INT
•Task2: ADCINT2 or EPWM2_INT
•Task7: ADCINT7 or EPWM7_INT
– Task8: ADCINT8 or by CPU Timer 0.
•Memory and Shared Peripherals:
– Two dedicated message RAMs for communication between the CLA and the main CPU.
– The C28x CPU can map CLA program and data memory to the main CPU space or CLA space.
– The CLA has direct access to the ADC Result registers, comparator registers, and the
MIPCTL0x14271YesInterrupt Priority Control Register
(2)
MPC
MAR0
MAR1
MSTF
MR0
MR1
MR2
MR3
(2)
(2)
(2)
(2)
(2)
(2)
(2)
0x14281–CLA Program Counter
0x142A1–CLA Aux Register 0
0x142B1–CLA Aux Register 1
0x142E2–CLA STF Register
0x14302–CLA R0H Register
0x14342–CLA R1H Register
0x14382–CLA R2H Register
0x143C2–CLA R3H Register
(1) All registers in this table are CSM protected
(2) The main C28x CPU has read only access to this register for debug purposes. The main CPU cannot perform CPU or debugger writes
to this register.
(1)
Table 4-2. CLA Message RAM
ADDRESS RANGESIZE (x16)DESCRIPTION
0x1480 – 0x14FF128CLA to CPU Message RAM
0x1500 – 0x157F128CPU to CLA Message RAM
A 12-bit ADC core is implemented that has different timings than the 12-bit ADC used on F280x/F2833x.
The ADC wrapper is modified to incorporate the new timings and also other enhancements to improve the
timing control of start of conversions. Figure 4-2 shows the interaction of the analog module with the rest
of the F2803x system.
The core of the ADC contains a single 12-bit converter fed by two sample-and-hold circuits. The
sample-and-hold circuits can be sampled simultaneously or sequentially. These, in turn, are fed by a total
of up to 16 analog input channels. The converter can be configured to run with an internal bandgap
reference to create true-voltage based conversions or with a pair of external voltage references
(V
REFHI/VREFLO
Contrary to previous ADC types, this ADC is not sequencer-based. It is easy for the user to create a
series of conversions from a single trigger. However, the basic principle of operation is centered around
the configurations of individual conversions, called SOCs, or Start-Of-Conversions.
Functions of the ADC module include:
•12-bit ADC core with built-in dual sample-and-hold (S/H)
•Simultaneous sampling or sequential sampling modes
•Full range analog input: 0 V to 3.3 V fixed, or V
analog voltage is derived by:
– Internal Reference
) to create ratiometric-based conversions.
REFHI/VREFLO
ratiometric. The digital value of the input
– External Reference
•Runs at full system clock, no prescaling required
•Up to 16-channel, multiplexed inputs
•16 SOCs, configurable for trigger, sample window, and channel
•16 result registers (individually addressable) to store conversion values
It is recommended that the connections for the analog power pins be kept, even if the ADC is not used.
Following is a summary of how the ADC pins should be connected, if the ADC is not used in an
application:
•V
•V
•V
•ADCINAn, ADCINBn – Connect to V
When the ADC module is used in an application, unused ADC input pins should be connected to analog
ground (V
NOTE: Unused ADCIN pins that are multiplexed with AIO function should not be directly connected to
analog ground. They should be grounded through a 1-kΩ resistor. This is to prevent an errant code from
configuring these pins as AIO outputs and driving grounded pins to a logic-high state.
When the ADC is not used, be sure that the clock to the ADC module is not turned on to realize power
savings.
The ADC channel and Comparator functions are always available. The digital I/O function is available only
when the respective bit in the AIOMUX1 register is 0. In this mode, reading the AIODAT register reflects
the actual pin state.
The digital I/O function is disabled when the respective bit in the AIOMUX1 register is 1. In this mode,
reading the AIODAT register reflects the output latch of the AIODAT register and the input digital I/O buffer
is disabled to prevent analog signals from generating noise.
On reset, the digital function is disabled. If the pin is used as an analog input, users should keep the AIO
function disabled for that pin.
The device includes the four-pin serial peripheral interface (SPI) module. Up to two SPI modules are
available. The SPI is a high-speed, synchronous serial I/O port that allows a serial bit stream of
programmed length (one to sixteen bits) to be shifted into and out of the device at a programmable
bit-transfer rate. Normally, the SPI is used for communications between the MCU and external peripherals
or another processor. Typical applications include external I/O or peripheral expansion through devices
such as shift registers, display drivers, and ADCs. Multidevice communications are supported by the
master/slave operation of the SPI.
NOTE: All four pins can be used as GPIO if the SPI module is not used.
•Two operational modes: master and slave
Baud rate: 125 different programmable rates.
www.ti.com
•Data word length: one to sixteen data bits
•Four clocking schemes (controlled by clock polarity and clock phase bits) include:
– Falling edge without phase delay: SPICLK active-high. SPI transmits data on the falling edge of the
SPICLK signal and receives data on the rising edge of the SPICLK signal.
– Falling edge with phase delay: SPICLK active-high. SPI transmits data one half-cycle ahead of the
falling edge of the SPICLK signal and receives data on the falling edge of the SPICLK signal.
– Rising edge without phase delay: SPICLK inactive-low. SPI transmits data on the rising edge of the
SPICLK signal and receives data on the falling edge of the SPICLK signal.
– Rising edge with phase delay: SPICLK inactive-low. SPI transmits data one half-cycle ahead of the
falling edge of the SPICLK signal and receives data on the rising edge of the SPICLK signal.
•Simultaneous receive and transmit operation (transmit function can be disabled in software)
•Transmitter and receiver operations are accomplished through either interrupt-driven or polled
algorithms.
•Nine SPI module control registers: Located in control register frame beginning at address 7040h.
NOTE
All registers in this module are 16-bit registers that are connected to Peripheral Frame 2.
When a register is accessed, the register data is in the lower byte (7–0), and the upper byte
(15–8) is read as zeros. Writing to the upper byte has no effect.
The devices include one serial communications interface (SCI) module (SCI-A). The SCI module supports
digital communications between the CPU and other asynchronous peripherals that use the standard
non-return-to-zero (NRZ) format. The SCI receiver and transmitter are double-buffered, and each has its
own separate enable and interrupt bits. Both can be operated independently or simultaneously in the
full-duplex mode. To ensure data integrity, the SCI checks received data for break detection, parity,
overrun, and framing errors. The bit rate is programmable to over 65000 different speeds through a 16-bit
baud-select register.
NOTE: Both pins can be used as GPIO if not used for SCI.
– Baud rate programmable to 64K different rates:
•Data-word format
– One start bit
– Data-word length programmable from one to eight bits
– Optional even/odd/no parity bit
– One or two stop bits
•Four error-detection flags: parity, overrun, framing, and break detection
•Two wake-up multiprocessor modes: idle-line and address bit
•Half- or full-duplex operation
•Double-buffered receive and transmit functions
•Transmitter and receiver operations can be accomplished through interrupt-driven or polled algorithms
with status flags.
– Transmitter: TXRDY flag (transmitter-buffer register is ready to receive another character) and TX
EMPTY flag (transmitter-shift register is empty)
– Receiver: RXRDY flag (receiver-buffer register is ready to receive another character), BRKDT flag
(break condition occurred), and RX ERROR flag (monitoring four interrupt conditions)
•Separate enable bits for transmitter and receiver interrupts (except BRKDT)
•NRZ (non-return-to-zero) format
NOTE
All registers in this module are 8-bit registers that are connected to Peripheral Frame 2.
When a register is accessed, the register data is in the lower byte (7–0), and the upper byte
(15–8) is read as zeros. Writing to the upper byte has no effect.
The device contains one LIN controller. The LIN standard is based on the SCI (UART) serial data link
format. The LIN module can be configured to work as a SCI as well.
The LIN module has the following features:
•Compatible to LIN 1.3 or 2.0 protocols
•Two external pins: LINRX and LINTX
•Multi-buffered receive and transmit units
•Identification masks for message filtering
•Automatic master header generation
– Programmable sync break field
– Sync field
– Identifier field
The CAN module (eCAN-A) has the following features:
•Fully compliant with CAN protocol, version 2.0B
•Supports data rates up to 1 Mbps
•Thirty-two mailboxes, each with the following properties:
– Configurable as receive or transmit
– Configurable with standard or extended identifier
– Has a programmable receive mask
– Supports data and remote frame
– Composed of 0 to 8 bytes of data
– Uses a 32-bit time stamp on receive and transmit message
– Protects against reception of new message
– Holds the dynamically programmable priority of transmit message
– Employs a programmable interrupt scheme with two interrupt levels
– Employs a programmable alarm on transmission or reception time-out
•Low-power mode
•Programmable wake-up on bus activity
•Automatic reply to a remote request message
•Automatic retransmission of a frame in case of loss of arbitration or error
•32-bit local network time counter synchronized by a specific message (communication in conjunction
with mailbox 16)
•Self-test mode
– Operates in a loopback mode receiving its own message. A "dummy" acknowledge is provided,
thereby eliminating the need for another node to provide the acknowledge bit.
NOTE
For a SYSCLKOUT of 60 MHz, the smallest bit rate possible is 9.375 kbps.
The F2803x CAN has passed the conformance test per ISO/DIS 16845. Contact TI for test report and
exceptions.
SN65HVD230Q3.3 VStandbyAdjustableYes––40°C to 125°C
SN65HVD2313.3 VSleepAdjustableYes––40°C to 85°C
SN65HVD231Q3.3 VSleepAdjustableYes––40°C to 125°C
SN65HVD2323.3 VNoneNoneNone––40°C to 85°C
SN65HVD232Q3.3 VNoneNoneNone––40°C to 125°C
SN65HVD2333.3 VStandbyAdjustableNoneDiagnostic Loopback–40°C to 125°C
SN65HVD2343.3 VStandby and SleepAdjustableNone––40°C to 125°C
SN65HVD2353.3 VStandbyAdjustableNoneAutobaud Loopback–40°C to 125°C
ISO10503–5.5 VNoneNoneNoneBuilt-in Isolation–55°C to 105°C
If the eCAN module is not used in an application, the RAM available (LAM, MOTS, MOTO,
and mailbox RAM) can be used as general-purpose RAM. The CAN module clock should be
enabled for this.
The CAN registers listed in Table 4-11 are used by the CPU to configure and control the CAN controller
and the message objects. eCAN control registers only support 32-bit read/write operations. Mailbox RAM
can be accessed as 16 bits or 32 bits. 32-bit accesses are aligned to an even boundary.
Table 4-11. CAN Register Map
REGISTER NAMESIZE (x32)DESCRIPTION
CANME0x60001Mailbox enable
CANMD0x60021Mailbox direction
CANTRS0x60041Transmit request set
CANTRR0x60061Transmit request reset
CANES0x60181Error and status
CANTEC0x601A1Transmit error counter
CANREC0x601C1Receive error counter
CANGIF00x601E1Global interrupt flag 0
CANGIM0x60201Global interrupt mask
CANGIF10x60221Global interrupt flag 1
CANMIM0x60241Mailbox interrupt mask
CANMIL0x60261Mailbox interrupt level
CANOPC0x60281Overwrite protection control
CANTIOC0x602A1TX I/O control
CANRIOC0x602C1RX I/O control
CANTSC0x602E1Time stamp counter (Reserved in SCC mode)
CANTOC0x60301Time-out control (Reserved in SCC mode)
CANTOS0x60321Time-out status (Reserved in SCC mode)
(1) These registers are mapped to Peripheral Frame 1.
The device contains one I2C Serial Port. Figure 4-11 shows how the I2C peripheral module interfaces
within the device.
The I2C module has the following features:
•Compliance with the Philips Semiconductors I2C-bus specification (version 2.1):
– Support for 1-bit to 8-bit format transfers
– 7-bit and 10-bit addressing modes
– General call
– START byte mode
– Support for multiple master-transmitters and slave-receivers
– Support for multiple slave-transmitters and master-receivers
– Combined master transmit/receive and receive/transmit mode
– Data transfer rate of from 10 kbps up to 400 kbps (I2C Fast-mode rate)
•One 4-word receive FIFO and one 4-word transmit FIFO
•One interrupt that can be used by the CPU. This interrupt can be generated as a result of one of the
following conditions:
– Transmit-data ready
– Receive-data ready
– Register-access ready
– No-acknowledgment received
– Arbitration lost
– Stop condition detected
– Addressed as slave
•An additional interrupt that can be used by the CPU when in FIFO mode
The devices contain up to seven enhanced PWM Modules (ePWM). Figure 4-12 shows a block diagram of
multiple ePWM modules. Figure 4-13 shows the signal interconnections with the ePWM. See the
Table 4-13. ePWM1–ePWM4 Control and Status Registers
NAMEePWM1ePWM2ePWM3ePWM4DESCRIPTION
TBCTL0x68000x68400x68800x68C01 / 0Time Base Control Register
TBSTS0x68010x68410x68810x68C11 / 0Time Base Status Register
TBPHSHR0x68020x68420x68820x68C21 / 0Time Base Phase HRPWM Register
TBPHS0x68030x68430x68830x68C31 / 0Time Base Phase Register
TBCTR0x68040x68440x68840x68C41 / 0Time Base Counter Register
TBPRD0x68050x68450x68850x68C51 / 1Time Base Period Register Set
TBPRDHR0x68060x68460x68860x68C61 / 1Time Base Period High Resolution Register
CMPCTL0x68070x68470x68870x68C71 / 0Counter Compare Control Register
CMPAHR0x68080x68480x68880x68C81 / 1Time Base Compare A HRPWM Register
CMPA0x68090x68490x68890x68C91 / 1Counter Compare A Register Set
CMPB0x680A0x684A0x688A0x68CA1 / 1Counter Compare B Register Set
AQCTLA0x680B0x684B0x688B0x68CB1 / 0Action Qualifier Control Register For Output A
AQCTLB0x680C0x684C0x688C0x68CC1 / 0Action Qualifier Control Register For Output B
AQSFRC0x680D0x684D0x688D0x68CD1 / 0Action Qualifier Software Force Register
AQCSFRC0x680E0x684E0x688E0x68CE1 / 1Action Qualifier Continuous S/W Force Register Set
DBCTL0x680F0x684F0x688F0x68CF1 / 1Dead-Band Generator Control Register
DBRED0x68100x68500x68900x68D01 / 0Dead-Band Generator Rising Edge Delay Count Register
DBFED0x68110x68510x68910x68D11 / 0Dead-Band Generator Falling Edge Delay Count Register
TZSEL0x68120x68520x68920x68D21 / 0Trip Zone Select Register
TZDCSEL0x68130x68530x68930x98D31 / 0Trip Zone Digital Compare Register
TZCTL0x68140x68540x68940x68D41 / 0Trip Zone Control Register
TZEINT0x68150x68550x68950x68D51 / 0Trip Zone Enable Interrupt Register
TZFLG0x68160x68560x68960x68D61 / 0Trip Zone Flag Register
TZCLR0x68170x68570x68970x68D71 / 0Trip Zone Clear Register
TZFRC0x68180x68580x68980x68D81 / 0Trip Zone Force Register
ETSEL0x68190x68590x68990x68D91 / 0Event Trigger Selection Register
ETPS0x681A0x685A0x689A0x68DA1 / 0Event Trigger Prescale Register
ETFLG0x681B0x685B0x689B0x68DB1 / 0Event Trigger Flag Register
ETCLR0x681C0x685C0x689C0x68DC1 / 0Event Trigger Clear Register
ETFRC0x681D0x685D0x689D0x68DD1 / 0Event Trigger Force Register
PCCTL0x681E0x685E0x689E0x68DE1 / 0PWM Chopper Control Register
HRCNFG0x68200x68600x68A00x68E01 / 0HRPWM Configuration Register
Table 4-13. ePWM1–ePWM4 Control and Status Registers (continued)
NAMEePWM1ePWM2ePWM3ePWM4DESCRIPTION
HRPWR0x6821---1 / 0HRPWM Power Register
HRMSTEP0x6826---1 / 0HRPWM MEP Step Register
HRPCTL0x68280x68680x68A80x68E81 / 0High resolution Period Control Register
TBPRDHRM0x682A0x686A0x68AA0x68EA1 / W
TBPRDM0x682B0x686B0x68AB0x68EB1 / W
CMPAHRM0x682C0x686C0x68AC0x68EC1 / W
CMPAM0x682D0x686D0x68AD0x68ED1 / W
DCTRIPSEL0x68300x68700x68B00x68F01 / 0Digital Compare Trip Select Register
DCACTL0x68310x68710x68B10x68F11 / 0Digital Compare A Control Register
DCBCTL0x68320x68720x68B20x68F21 / 0Digital Compare B Control Register
DCFCTL0x68330x68730x68B30x68F31 / 0Digital Compare Filter Control Register
DCCAPCT0x68340x68740x68B40x68F41 / 0Digital Compare Capture Control Register
DCFOFFSET0x68350x68750x68B50x68F51 / 1Digital Compare Filter Offset Register
DCFOFFSETCNT0x68360x68760x68B60x68F61 / 0Digital Compare Filter Offset Counter Register
DCFWINDOW0x68370x68770x68B70x68F71 / 0Digital Compare Filter Window Register
DCFWINDOWCNT0x68380x68780x68B80x68F81 / 0Digital Compare Filter Window Counter Register
DCCAP0x68390x68790x68B90x68F91 / 1Digital Compare Counter Capture Register
(2) W = Write to shadow register
SIZE (x16) /
#SHADOW
(2)
(2)
(2)
(2)
(1)
Time Base Period HRPWM Register Mirror
Time Base Period Register Mirror
Compare A HRPWM Register Mirror
Compare A Register Mirror
(1)
(1)
(1)
(1)
(1)
www.ti.com
Table 4-14. ePWM5–ePWM7 Control and Status Registers
NAMEePWM5ePWM6ePWM7DESCRIPTION
TBCTL0x69000x69400x69801 / 0Time Base Control Register
TBSTS0x69010x69410x69811 / 0Time Base Status Register
TBPHSHR0x69020x69420x69821 / 0Time Base Phase HRPWM Register
TBPHS0x69030x69430x69831 / 0Time Base Phase Register
TBCTR0x69040x69440x69841 / 0Time Base Counter Register
TBPRD0x69050x69450x69851 / 1Time Base Period Register Set
TBPRDHR0x69060x69460x69861 / 1Time Base Period High Resolution Register
CMPCTL0x69070x69470x69871 / 0Counter Compare Control Register
CMPAHR0x69080x69480x69881 / 1Time Base Compare A HRPWM Register
CMPA0x69090x69490x69891 / 1Counter Compare A Register Set
This module combines multiple delay lines in a single module and a simplified calibration system by using
a dedicated calibration delay line. For each ePWM module there is one HR delay line.
The HRPWM module offers PWM resolution (time granularity) that is significantly better than what can be
achieved using conventionally derived digital PWM methods. The key points for the HRPWM module are:
•Significantly extends the time resolution capabilities of conventionally derived digital PWM
•This capability can be utilized in both single edge (duty cycle and phase-shift control) as well as dual
edge control for frequency/period modulation.
•Finer time granularity control or edge positioning is controlled via extensions to the Compare A and
Phase registers of the ePWM module.
•HRPWM capabilities, when available on a particular device, are offered only on the A signal path of an
ePWM module (i.e., on the EPWMxA output). EPWMxB output has conventional PWM capabilities.
NOTE
The minimum SYSCLKOUT frequency allowed for HRPWM is 60 MHz.
NOTE
When dual-edge high-resolution is enabled (high-resolution period mode), the PWMxB output
is not available for use.
The device contains an enhanced capture (eCAP) module. Figure 4-14 shows a functional block diagram
of a module.
Figure 4-14. eCAP Functional Block Diagram
The eCAP module is clocked at the SYSCLKOUT rate.
The clock enable bits (ECAP1 ENCLK) in the PCLKCR1 register turn off the eCAP module individually (for
low power operation). Upon reset, ECAP1ENCLK is set to low, indicating that the peripheral clock is off.
The device contains one enhanced quadrature encoder pulse (eQEP) module.
Table 4-16. eQEP Control and Status Registers
NAMESIZE(x16)/REGISTER DESCRIPTION
QPOSCNT0x6B002/0eQEP Position Counter
QPOSINIT0x6B022/0eQEP Initialization Position Count
QPOSMAX0x6B042/0eQEP Maximum Position Count
QPOSCMP0x6B062/1eQEP Position-compare
QPOSILAT0x6B082/0eQEP Index Position Latch
QPOSSLAT0x6B0A2/0eQEP Strobe Position Latch
QPOSLAT0x6B0C2/0eQEP Position Latch
QUTMR0x6B0E2/0eQEP Unit Timer
QUPRD0x6B102/0eQEP Unit Period Register
QWDTMR0x6B121/0eQEP Watchdog Timer
QWDPRD0x6B131/0eQEP Watchdog Period Register
QDECCTL0x6B141/0eQEP Decoder Control Register
QEPCTL0x6B151/0eQEP Control Register
QCAPCTL0x6B161/0eQEP Capture Control Register
QPOSCTL0x6B171/0eQEP Position-compare Control Register
QEINT0x6B181/0eQEP Interrupt Enable Register
QFLG0x6B191/0eQEP Interrupt Flag Register
QCLR0x6B1A1/0eQEP Interrupt Clear Register
QFRC0x6B1B1/0eQEP Interrupt Force Register
QEPSTS0x6B1C1/0eQEP Status Register
QCTMR0x6B1D1/0eQEP Capture Timer
QCPRD0x6B1E1/0eQEP Capture Period Register
QCTMRLAT0x6B1F1/0eQEP Capture Timer Latch
QCPRDLAT0x6B201/0eQEP Capture Period Latch
Reserved0x6B21 –31/0
On the 2803x device, the JTAG port is reduced to 5 pins (TRST, TCK, TDI, TMS, TDO). TCK, TDI, TMS
and TDO pins are also GPIO pins. The TRST signal selects either JTAG or GPIO operating mode for the
pins in Figure 4-16. During emulation/debug, the GPIO function of these pins are not available. If the
GPIO38/TCK/XCLKIN pin is used to provide an external clock, an alternate clock source should be used
to clock the device during emulation/debug since this pin will be needed for the TCK function.
NOTE
In 2803x devices, the JTAG pins may also be used as GPIO pins. Care should be taken in
the board design to ensure that the circuitry connected to these pins do not affect the
emulation capabilities of the JTAG pin function. Any circuitry connected to these pins should
not prevent the emulator from driving (or being driven by) the JTAG pins for successful
debug.
The GPIO MUX can multiplex up to three independent peripheral signals on a single GPIO pin in addition
to providing individual pin bit-banging I/O capability.
The device supports 45 GPIO pins. The GPIO control and data registers are mapped to Peripheral
Frame 1 to enable 32-bit operations on the registers (along with 16-bit operations). Table 4-17 shows the
GPIO register mapping.
Table 4-17. GPIO Registers
NAMEADDRESSSIZE (x16)DESCRIPTION
GPIO CONTROL REGISTERS (EALLOW PROTECTED)
GPACTRL0x6F802GPIO A Control Register (GPIO0 to 31)
GPAQSEL10x6F822GPIO A Qualifier Select 1 Register (GPIO0 to 15)
GPAQSEL20x6F842GPIO A Qualifier Select 2 Register (GPIO16 to 31)
GPAMUX10x6F862GPIO A MUX 1 Register (GPIO0 to 15)
GPAMUX20x6F882GPIO A MUX 2 Register (GPIO16 to 31)
GPADIR0x6F8A2GPIO A Direction Register (GPIO0 to 31)
GPAPUD0x6F8C2GPIO A Pull Up Disable Register (GPIO0 to 31)
GPBCTRL0x6F902GPIO B Control Register (GPIO32 to 44)
GPBQSEL10x6F922GPIO B Qualifier Select 1 Register (GPIO32 to 44)
GPBMUX10x6F962GPIO B MUX 1 Register (GPIO32 to 44)
GPBDIR0x6F9A2GPIO B Direction Register (GPIO32 to 44)
GPBPUD0x6F9C2GPIO B Pull Up Disable Register (GPIO32 to 44)
AIOMUX10x6FB62Analog, I/O mux 1 register (AIO0 to AIO15)
AIODIR0x6FBA2Analog, I/O Direction Register (AIO0 to AIO15)
GPIO DATA REGISTERS (NOT EALLOW PROTECTED)
GPADAT0x6FC02GPIO A Data Register (GPIO0 to 31)
GPASET0x6FC22GPIO A Data Set Register (GPIO0 to 31)
GPACLEAR0x6FC42GPIO A Data Clear Register (GPIO0 to 31)
GPATOGGLE0x6FC62GPIO A Data Toggle Register (GPIO0 to 31)
GPBDAT0x6FC82GPIO B Data Register (GPIO32 to 44)
GPBSET0x6FCA2GPIO B Data Set Register (GPIO32 to 44)
GPBCLEAR0x6FCC2GPIO B Data Clear Register (GPIO32 to 44)
GPBTOGGLE0x6FCE2GPIO B Data Toggle Register (GPIO32 to 44)
AIODAT0x6FD82Analog I/O Data Register (AIO0 to AIO15)
AIOSET0x6FDA2Analog I/O Data Set Register (AIO0 to AIO15)
AIOCLEAR0x6FDC2Analog I/O Data Clear Register (AIO0 to AIO15)
AIOTOGGLE0x6FDE2Analog I/O Data Toggle Register (AIO0 to AIO15)
GPIO INTERRUPT AND LOW POWER MODES SELECT REGISTERS (EALLOW PROTECTED)
GPIOXINT1SEL0x6FE01XINT1 GPIO Input Select Register (GPIO0 to 31)
GPIOXINT2SEL0x6FE11XINT2 GPIO Input Select Register (GPIO0 to 31)
GPIOXINT3SEL0x6FE21XINT3 GPIO Input Select Register (GPIO0 to 31)
GPIOLPMSEL0x6FE82LPM GPIO Select Register (GPIO0 to 31)
www.ti.com
NOTE
There is a two-SYSCLKOUT cycle delay from when the write to the GPxMUXn/AIOMUXn
and GPxQSELn registers occurs to when the action is valid.
(1) The word reserved means that there is no peripheral assigned to this GPxMUX1/2 register setting. Should it be selected, the state of the
pin will be undefined and the pin may be driven. This selection is a reserved configuration for future expansion.
(2) I = Input, O = Output, OD = Open Drain
(3) These pins are not available in the 64-pin package.
The user can select the type of input qualification for each GPIO pin via the GPxQSEL1/2 registers from
four choices:
•Synchronization To SYSCLKOUT Only (GPxQSEL1/2 = 0, 0): This is the default mode of all GPIO pins
at reset and it simply synchronizes the input signal to the system clock (SYSCLKOUT).
•Qualification Using Sampling Window (GPxQSEL1/2 = 0, 1 and 1, 0): In this mode the input signal,
after synchronization to the system clock (SYSCLKOUT), is qualified by a specified number of cycles
before the input is allowed to change.
•The sampling period is specified by the QUALPRD bits in the GPxCTRL register and is configurable in
groups of 8 signals. It specifies a multiple of SYSCLKOUT cycles for sampling the input signal. The
sampling window is either 3-samples or 6-samples wide and the output is only changed when ALL
samples are the same (all 0s or all 1s) as shown in Figure 4-18 (for 6 sample mode).
•No Synchronization (GPxQSEL1/2 = 1,1): This mode is used for peripherals where synchronization is
not required (synchronization is performed within the peripheral).
Due to the multi-level multiplexing that is required on the device, there may be cases where a peripheral
input signal can be mapped to more then one GPIO pin. Also, when an input signal is not selected, the
input signal will default to either a 0 or 1 state, depending on the peripheral.
A.x stands for the port, either A or B. For example, GPxDIR refers to either the GPADIR and GPBDIR register
depending on the particular GPIO pin selected.
B.GPxDAT latch/read are accessed at the same memory location.
C.This is a generic GPIO MUX block diagram. Not all options may be applicable for all GPIO pins. See the
TMS320x2803x Piccolo System Control and Interrupts Reference Guide (literature number SPRUGL8) for pin-specific
Texas Instruments (TI) offers an extensive line of development tools for the C28x™ generation of MCUs,
including tools to evaluate the performance of the processors, generate code, develop algorithm
implementations, and fully integrate and debug software and hardware modules.
The following products support development of 2803x-based applications:
Software Development Tools
•Code Composer Studio™ Integrated Development Environment (IDE)
– C/C++ Compiler
– Code generation tools
– Assembler/Linker
– Cycle Accurate Simulator
•Application algorithms
•Sample applications code
Hardware Development Tools
•Development and evaluation boards
•JTAG-based emulators - XDS510™ Class, XDS100
•Flash programming tools
•Power supply
•Documentation and cables
5.1Device and Development Support Tool Nomenclature
To designate the stages in the product development cycle, TI assigns prefixes to the part numbers of all
TMS320™ MCU devices and support tools. Each TMS320™ MCU commercial family member has one of
three prefixes: TMX, TMP, or TMS (e.g., TMS320F28032). Texas Instruments recommends two of three
possible prefix designators for its support tools: TMDX and TMDS. These prefixes represent evolutionary
stages of product development from engineering prototypes (TMX/TMDX) through fully qualified
production devices/tools (TMS/TMDS).
Device development evolutionary flow:
TMXExperimental device that is not necessarily representative of the final device's electrical
specifications
TMPFinal silicon die that conforms to the device's electrical specifications but has not
completed quality and reliability verification
TMSFully qualified production device
Support tool development evolutionary flow:
TMDXDevelopment-support product that has not yet completed Texas Instruments internal
qualification testing
TMDSFully qualified development-support product
TMX and TMP devices and TMDX development-support tools are shipped against the following
disclaimer:
"Developmental product is intended for internal evaluation purposes."
TMS devices and TMDS development-support tools have been characterized fully, and the quality and
reliability of the device have been demonstrated fully. TI's standard warranty applies.
Predictions show that prototype devices (TMX or TMP) have a greater failure rate than the standard
production devices. Texas Instruments recommends that these devices not be used in any production
system because their expected end-use failure rate still is undefined. Only qualified production devices are
to be used.
TI device nomenclature also includes a suffix with the device family name. This suffix indicates the
package type (for example, PN) and temperature range (for example, T). Figure 5-1 provides a legend for
reading the complete device name for any family member.
Extensive documentation supports all of the TMS320™ MCU family generations of devices from product
announcement through applications development. The types of documentation available include: data
sheets and data manuals, with design specifications; and hardware and software applications.
Table 5-1 shows the peripheral reference guides appropriate for use with the devices in this data manual.
See the TMS320x28xx, 28xxx DSP Peripheral Reference Guide (literature number SPRU566) for more
information on types of peripherals.
TMS320x2803x Piccolo System Control and InterruptsSPRUGL8–X
TMS320x2802x, 2803x Piccolo Analog-to-Digital Converter (ADC) and ComparatorSPRUGE53/0
TMS320x2802x, 2803x Piccolo Serial Communications Interface (SCI)SPRUGH10X
TMS320x2802x, 2803x Piccolo Serial Peripheral Interface (SPI)SPRUG711X
TMS320x2803x Piccolo Boot ROMSPRUGO0–X
TMS320x2802x, 2803x Piccolo Enhanced Pulse Width Modulator (ePWM) ModuleSPRUGE91X
TMS320x2802x, 2803x Piccolo Enhanced Capture (eCAP) ModuleSPRUFZ80X
TMS320x2802x, 2803x Piccolo Inter-Integrated Circuit (I2C)SPRUFZ90X
TMS320x2802x, 2803x Piccolo High-Resolution Pulse-Width Modulator (HRPWM)SPRUGE81X
TMS320x2803x Piccolo Control Law Accelerator (CLA)SPRUGE60X
TMS320x2803x Piccolo Local Interconnect Network (LIN) ModuleSPRUGE20X
TMS320x2803x Piccolo Enhanced Quadrature Encoder Pulse (eQEP)SPRUFK80X
TMS320x2803x Piccolo Enhanced Controller Area Network (eCAN)SPRUGL70X
(1) A type change represents a major functional feature difference in a peripheral module. Within a peripheral type, there may be minor
differences between devices that do not affect the basic functionality of the module. These device-specific differences are listed in the
peripheral reference guides.
(2) The ADC module is Type 3 and the comparator module is Type 0.
(1)
(2)
28032, 28033,
28034, 28035
X
The following documents can be downloaded from the TI website (www.ti.com):
TMS320F28035 Piccolo MCU Silicon Errata describes known advisories on silicon and
provides workarounds.
CPU User's Guides
SPRU430TMS320C28x CPU and Instruction Set Reference Guide describes the central processing
unit (CPU) and the assembly language instructions of the TMS320C28x fixed-point digital
signal processors (DSPs). It also describes emulation features available on these DSPs.
Peripheral Guides
SPRUGL8TMS320x2803x Piccolo System Control and Interrupts Reference Guide describes the
various interrupts and system control features of the 2803x microcontrollers (MCUs).
SPRU566TMS320x28xx, 28xxx DSP Peripheral Reference Guide describes the peripheral reference
guides of the 28x digital signal processors (DSPs).
SPRUGO0TMS320x2803x Piccolo Boot ROM Reference Guide describes the purpose and features
of the boot loader (factory-programmed boot-loading software) and provides examples of
code. It also describes other contents of the device on-chip boot ROM and identifies where
all of the information is located within that memory.
SPRUGE5TMS320x2802x, 2803x Piccolo Analog-to-Digital Converter (ADC) and Comparator
Reference Guide describes how to configure and use the on-chip ADC module, which is a
12-bit pipelined ADC.
SPRUGE9TMS320x2802x, 2803x Piccolo Enhanced Pulse Width Modulator (ePWM) Module
Reference Guide describes the main areas of the enhanced pulse width modulator that
include digital motor control, switch mode power supply control, UPS (uninterruptible power
supplies), and other forms of power conversion.
SPRUGE8TMS320x2802x, 2803x Piccolo High-Resolution Pulse Width Modulator (HRPWM)
describes the operation of the high-resolution extension to the pulse width modulator
(HRPWM).
SPRUGH1TMS320x2802x, 2803x Piccolo Serial Communications Interface (SCI) Reference Guide
describes how to use the SCI.
SPRUFZ8TMS320x2802x, 2803x Piccolo Enhanced Capture (eCAP) Module Reference Guide
describes the enhanced capture module. It includes the module description and registers.
SPRUG71TMS320x2802x, 2803x Piccolo Serial Peripheral Interface (SPI) Reference Guide
describes the SPI - a high-speed synchronous serial input/output (I/O) port - that allows a
serial bit stream of programmed length (one to sixteen bits) to be shifted into and out of the
device at a programmed bit-transfer rate.
www.ti.com
SPRUFZ9TMS320x2802x, 2803x Piccolo Inter-Integrated Circuit (I2C) Reference Guide describes
the features and operation of the inter-integrated circuit (I2C) module.
SPRUGE6TMS320x2803x Piccolo Control Law Accelerator (CLA) Reference Guide describes the
operation of the Control Law Accelerator (CLA).
SPRUGE2TMS320x2803x Piccolo Local Interconnect Network (LIN) Module Reference Guide
describes the operation of the Local Interconnect Network (LIN) Module.
SPRUFK8TMS320x2803x Piccolo Enhanced Quadrature Encoder Pulse (eQEP) Reference Guide
describes the operation of the Enhanced Quadrature Encoder Pulse (eQEP) .
SPRUGL7TMS320x2803x Piccolo Enhanced Controller Area Network (eCAN) Reference Guide
describes the operation of the Enhanced Controller Area Network (eCAN).
Tools Guides
SPRU513TMS320C28x Assembly Language Tools v5.0.0 User's Guide describes the assembly
language tools (assembler and other tools used to develop assembly language code),
assembler directives, macros, common object file format, and symbolic debugging directives
for the TMS320C28x device.
TMS320C28x™ C/C++ compiler. This compiler accepts ANSI standard C/C++ source code
and produces TMS320 DSP assembly language source code for the TMS320C28x device.
SPRU608TMS320C28x Instruction Set Simulator Technical Overview describes the simulator,
available within the Code Composer Studio for TMS320C2000 IDE, that simulates the
instruction set of the C28x™ core.
Supply voltage range, V
Supply voltage range, V
Analog voltage range, V
Input voltage range, VIN(3.3 V)–0.3 V to 4.6 V
Output voltage range, V
Input clamp current, IIK(VIN< 0 or VIN> V
Output clamp current, IOK(VO< 0 or VO> V
Junction temperature range, T
Storage temperature range, T
(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 is not implied. Exposure to
absolute-maximum-rated conditions for extended periods may affect device reliability.
(2) All voltage values are with respect to VSS, unless otherwise noted.
(3) Continuous clamp current per pin is ± 2 mA.
(4) Long-term high-temperature storage and/or extended use at maximum temperature conditions may result in a reduction of overall device
life. For additional information, see IC Package Thermal Metrics Application Report (literature number SPRA953) and Reliability Data for
TMS320LF24xx and TMS320F28xx Devices Application Report (literature number SPRA963).
(I/O and Flash)with respect to V
DDIO
DD
DDA
O
(4)
J
(4)
stg
6.2Recommended Operating Conditions
Device supply voltage, I/O, V
Device supply voltage CPU, VDD(When internal1.711.81.995
VREG is disabled and 1.8 V is supplied externally)
Supply ground, V
Analog supply voltage, V
Analog ground, V
Table 6-1. TMS320F2803x Current Consumption at 60-MHz SYSCLKOUT
VREG ENABLEDVREG DISABLED
MODETEST CONDITIONSI
TYP
The following peripheral clocks
are enabled:
•ePWM1/2/3/4/5/6/7
•eCAP1
•eQEP1
•eCAN
•LIN
•CLA
•HRPWM
Operational
(Flash)
IDLE13 mA23 mA73 mA80 mA13 mA24 mA120 mA 400 mA73 mA80 mA
STANDBY4 mA9 mA10 mA15 mA4 mA7 mA120 mA 400 mA10 mA15 mA
HALTPeripheral clocks are off.46 mA10 mA15 mA30 mA24 mA10 mA15 mA
(1) I
DDIO
(2) In order to realize the I
writing to the PCLKCR0 register.
•SCI-A
•SPI-A/B
•ADC
•I2C
•COMP1/2/3
•CPU-TIMER0/1/2
All PWM pins are toggled at
60 kHz.
All I/O pins are left
unconnected.
Code is running out of flash
with 2 wait-states.
XCLKOUT is turned off.
Flash is powered down.
XCLKOUT is turned off.
All peripheral clocks are turned
off.
Flash is powered down.
Peripheral clocks are off.
Flash is powered down.
Input clock is disabled.
(4)(5)
(7)
114 mA
current is dependent on the electrical loading on the I/O pins.
currents shown for IDLE, STANDBY, and HALT, clock to the ADC module must be turned off explicitly by
DDA
DDIO
(3)
(6)
(1)
MAXTYP
(6)
135 mA
14 mA18 mA101 mA
(3) The TYP numbers are applicable over room temperature and nominal voltage.
(4) The following is done in a loop:
• Data is continuously transmitted out of SPI-A/B, SCI-A, eCAN, LIN, and I2C ports.
• The hardware multiplier is exercised.
• Watchdog is reset.
• ADC is performing continuous conversion.
• COMP1/2 are continuously switching voltages.
• GPIO17 is toggled.
(5) CLA is continuously performing polynomial calculations.
(6) For F2803x devices that do not have CLA, subtract the IDDcurrent number for CLA (see Table 6-2 ) from the IDD(VREG disabled)/I
(VREG enabled) current numbers shown in Table 6-1 for operational mode.
(7) If a quartz crystal or ceramic resonator is used as the clock source, the HALT mode shuts down the on-chip crystal oscillator.
(2)
I
DDA
(3)
MAXTYP
(3)
(6)
I
DD
MAXTYP
120 mA
(1)
I
DDIO
(3)
MAXTYP
(6)
14 mA18 mA14 mA18 mA
(2)
I
DDA
(3)
MAX
DDIO
NOTE
The peripheral - I/O multiplexing implemented in the device prevents all available peripherals
from being used at the same time. This is because more than one peripheral function may
share an I/O pin. It is, however, possible to turn on the clocks to all the peripherals at the
same time, although such a configuration is not useful. If this is done, the current drawn by
the device will be more than the numbers specified in the current consumption tables.
The 2803x devices incorporate a method to reduce the device current consumption. Since each peripheral
unit has an individual clock-enable bit, significant reduction in current consumption can be achieved by
turning off the clock to any peripheral module that is not used in a given application. Furthermore, any one
of the three low-power modes could be taken advantage of to reduce the current consumption even
further. Table 6-2 indicates the typical reduction in current consumption achieved by turning off the clocks.
Table 6-2. Typical Current Consumption by Various
Peripherals (at 60 MHz)
PERIPHERALIDDCURRENT
MODULE
COMP/DAC1
CPU-TIMER1
Internal zero-pin oscillator0.5
(1) All peripheral clocks (except CPU Timer clock) are disabled upon
reset. Writing to/reading from peripheral registers is possible only
after the peripheral clocks are turned on.
(2) For peripherals with multiple instances, the current quoted is per
module. For example, the 2 mA value quoted for ePWM is for one
ePWM module.
(3) This number represents the current drawn by the digital portion of
the ADC module. Turning off the clock to the ADC module results in
the elimination of the current drawn by the analog portion of the ADC
(I
) as well.
DDA
(2)
ADC2
I2C3
ePWM2
eCAP2
eQEP2
SCI2
SPI2
HRPWM3
CAN2.5
LIN1.5
CLA20
(1)
REDUCTION (mA)
(3)
www.ti.com
NOTE
I
current consumption is reduced by 15 mA (typical) when XCLKOUT is turned off.
DDIO
NOTE
The baseline IDDcurrent (current when the core is executing a dummy loop with no
peripherals enabled) is 40 mA, typical. To arrive at the IDDcurrent for a given application, the
current-drawn by the peripherals (enabled by that application) must be added to the baseline
IDDcurrent.
Following are other methods to reduce power consumption further:
•The flash module may be powered down if code is run off SARAM. This results in a current reduction
of 18 mA (typical) in the VDDrail and 13 mA (typical) in the V
Based on the end application design and operational profile, the IDDand I
Systems that exceed the recommended maximum power dissipation in the end product may require
additional thermal enhancements. Ambient temperature (TA) varies with the end application and product
design. The critical factor that affects reliability and functionality is TJ, the junction temperature, not the
ambient temperature. Hence, care should be taken to keep TJwithin the specified limits. T
measured to estimate the operating junction temperature TJ. T
is normally measured at the center of
case
the package top-side surface. The thermal application reports IC Package Thermal Metrics (literature
number SPRA953) and Reliability Data for TMS320LF24xx and TMS320F28xx Devices (literature number
SPRA963) help to understand the thermal metrics and definitions.
currents could vary.
DDIO
6.6Emulator Connection Without Signal Buffering for the MCU
Figure 6-4 shows the connection between the MCU and JTAG header for a single-processor configuration.
If the distance between the JTAG header and the MCU is greater than 6 inches, the emulation signals
must be buffered. If the distance is less than 6 inches, buffering is typically not needed. Figure 6-4 shows
the simpler, no-buffering situation. For the pullup/pulldown resistor values, see the pin description section.
should be
case
A.See Figure 4-16 for JTAG/GPIO multiplexing.
Figure 6-4. Emulator Connection Without Signal Buffering for the MCU
NOTE
The 2803x devices do not have EMU0/EMU1 pins. For designs that have a JTAG Header
on-board, the EMU0/EMU1 pins on the header must be tied to V
(typical) resistor.
Timing parameter symbols used are created in accordance with JEDEC Standard 100. To shorten the
symbols, some of the pin names and other related terminology have been abbreviated as follows:
Lowercase subscripts and theirLetters and symbols and their
meanings:meanings:
aaccess timeHHigh
ccycle time (period)LLow
ddelay timeVValid
ffall timeX
hhold timeZHigh impedance
rrise time
susetup time
ttransition time
vvalid time
wpulse duration (width)
Unknown, changing, or don't care
level
6.7.1General Notes on Timing Parameters
All output signals from the 28x devices (including XCLKOUT) are derived from an internal clock such that
all output transitions for a given half-cycle occur with a minimum of skewing relative to each other.
www.ti.com
The signal combinations shown in the following timing diagrams may not necessarily represent actual
cycles. For actual cycle examples, see the appropriate cycle description section of this document.
6.7.2Test Load Circuit
This test load circuit is used to measure all switching characteristics provided in this document.
A.Input requirements in this data sheet are tested with an input slew rate of < 4 Volts per nanosecond (4 V/ns) at the
device pin.
B.The data sheet provides timing at the device pin. For output timing analysis, the tester pin electronics and its
transmission line effects must be taken into account. A transmission line with a delay of 2 ns or longer can be used to
produce the desired transmission line effect. The transmission line is intended as a load only. It is not necessary to
add or subtract the transmission line delay (2 ns or longer) from the data sheet timing.