Texas Instruments | TMS320DM35x DMSoC Serial Peripheral Interface (SPI) (Rev. B) | User Guides | Texas Instruments TMS320DM35x DMSoC Serial Peripheral Interface (SPI) (Rev. B) User guides

Texas Instruments TMS320DM35x DMSoC Serial Peripheral Interface (SPI) (Rev. B) User guides
TMS320DM35x Digital Media
System-on-Chip (DMSoC)
Serial Peripheral Interface (SPI)
Reference Guide
Literature Number: SPRUED4B
May 2006 – Revised October 2007
2
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Contents
Preface ............................................................................................................................... 6
1
Introduction................................................................................................................ 9
1.1
Purpose of the Peripheral ....................................................................................... 9
1.2
Features ........................................................................................................... 9
1.3
Functional Block Diagram ..................................................................................... 10
............................................................... 10
Peripheral Architecture .............................................................................................. 10
2.1
Clock Control .................................................................................................... 10
2.2
Signal Descriptions ............................................................................................. 11
2.3
Pin Multiplexing ................................................................................................. 11
2.4
SPI Operation ................................................................................................... 11
2.5
Reset Considerations .......................................................................................... 18
2.6
Initialization ...................................................................................................... 18
2.7
Interrupt Support ................................................................................................ 19
2.8
EDMA Event Support .......................................................................................... 20
2.9
Power Management ............................................................................................ 21
2.10 SPI Internal Loop-Back Test Mode ........................................................................... 21
2.11 Emulation Considerations ..................................................................................... 21
Registers .................................................................................................................. 22
3.1
SPI Global Control Register 0 (SPIGCR0) .................................................................. 22
3.2
SPI Global Control Register 1 (SPIGCR1) .................................................................. 23
3.3
SPI Interrupt Register (SPIINT) ............................................................................... 24
3.4
SPI Interrupt Level Register (SPILVL) ....................................................................... 25
3.5
SPI Flag Register (SPIFLG) ................................................................................... 26
3.6
SPI Pin Control Register (SPIPC0) .......................................................................... 27
3.7
SPI Pin Control Register 2 (SPIPC2) ........................................................................ 28
3.8
SPI Shift Register (SPIDAT1) ................................................................................. 29
3.9
SPI Buffer Register (SPIBUF)................................................................................. 30
3.10 SPI Emulation Register (SPIEMU) ........................................................................... 31
3.11 SPI Delay Register (SPIDELAY) ............................................................................. 32
3.12 SPI Default Chip Select Register (SPIDEF)................................................................. 33
3.13 SPI Data Format Registers (SPIFMTn) ...................................................................... 34
3.14 SPI Interrupt Vector Register 0 (INTVECT0) ............................................................... 35
3.15 SPI Interrupt Vector Register 1 (INTVECT1) ............................................................... 36
1.4
2
3
Industry Standard(s) Compliance Statement
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Table of Contents
3
List of Figures
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
4
Serial Peripheral Interface (SPI) Block Diagram .......................................................................
Right-Aligned Transmit Data in SPIDAT1 Field of the SPI Shift Register (SPIDAT1) ............................
Right-Aligned Receive Data in SPIBUF Field of the SPI Buffer Register (SPIBUF) ..............................
Clock Mode with POLARITY = 0 and PHASE = 0 .....................................................................
Clock Mode with POLARITY = 0 and PHASE = 1 .....................................................................
Clock Mode with POLARITY = 1 and PHASE = 0 .....................................................................
Clock Mode with POLARITY = 1 and PHASE = 1 .....................................................................
Five Bits per Character (Four-Pin Option) ..............................................................................
SPI Operation (3-Pin Option) .............................................................................................
SPI Operation (4-Pin Option) .............................................................................................
SPI Global Control Register 0 (SPIGCR0) ..............................................................................
SPI Global Control Register 1 (SPIGCR1) ..............................................................................
SPI Interrupt Register (SPIINT) ..........................................................................................
SPI Interrupt Level Register (SPILVL) ...................................................................................
SPI Flag Register (SPIFLG) ..............................................................................................
SPI Pin Control Register (SPIPC0) ......................................................................................
SPI Pin Control Register 2 (SPIPC2) ....................................................................................
SPI Shift Register (SPIDAT1).............................................................................................
SPI Buffer Register (SPIBUF) ............................................................................................
SPI Emulation Register (SPIEMU) .......................................................................................
SPI Delay Register (SPIDELAY) .........................................................................................
SPI Default Chip Select Register (SPIDEF) ............................................................................
SPI Data Format Register (SPIFMTn) ...................................................................................
SPI Interrupt Vector Register 0 (INTVECT0) ...........................................................................
SPI Interrupt Vector Register 1 (INTVECT1) ...........................................................................
List of Figures
10
12
12
13
13
14
14
15
17
17
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
List of Tables
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Serial Peripheral Interface (SPI) Pins ...................................................................................
SPI Clocking Modes .......................................................................................................
SPI Registers ...............................................................................................................
SPI Global Control Register 0 (SPIGCR0) Field Descriptions .......................................................
SPI Global Control Register 1 (SPIGCR1) Field Descriptions .......................................................
SPI Interrupt Register (SPIINT) Field Descriptions ....................................................................
SPI Interrupt Level Register (SPILVL) Field Descriptions ............................................................
SPI Flag Register (SPIFLG) Field Descriptions ........................................................................
SPI Pin Control Register (SPIPC0) Field Descriptions ................................................................
SPI Pin Control Register 2 (SPIPC2) Field Descriptions..............................................................
SPI Shift Register (SPIDAT1) Field Descriptions ......................................................................
SPI Buffer Register (SPIBUF) Field Descriptions ......................................................................
SPI Emulation Register (SPIEMU) Field Descriptions.................................................................
SPI Delay Register (SPIDELAY) Field Descriptions ...................................................................
SPI Default Chip Select Register (SPIDEF) Field Descriptions ......................................................
SPI Data Format Register (SPIFMTn) Field Descriptions ............................................................
SPI Interrupt Vector Register 0 (INTVECT0) Field Descriptions .....................................................
SPI Interrupt Vector Register 1 (INTVECT1) Field Descriptions .....................................................
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
List of Tables
11
12
22
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
5
Preface
SPRUED4B – May 2006 – Revised October 2007
Read This First
This document describes the Serial Peripheral Interface (SPI) on the TMS320DM35x Digital Media
System-on-Chip (DMSoC).
Notational Conventions
This document uses the following conventions.
• Hexadecimal numbers are shown with the suffix h. For example, the following number is 40
hexadecimal (decimal 64): 40h.
• Registers in this document are shown in figures and described in tables.
– Each register figure shows a rectangle divided into fields that represent the fields of the register.
Each field is labeled with its bit name, its beginning and ending bit numbers above, and its
read/write properties below. A legend explains the notation used for the properties.
– Reserved bits in a register figure designate a bit that is used for future device expansion.
TMS320DM355 Digital Media System-on-Chip (DMSoC)
Related Documentation From Texas Instruments
The following documents describe the TMS320DM355 Digital Media System-on-Chip (DMSoC). Copies of
these documents are available on the internet at www.ti.com. Contact your TI representative for Extranet
access.
SPRS463— TMS320DM355 Digital Media System-on-Chip (DMSoC) Data Manual This document
describes the overall TMS320DM355 system, including device architecture and features, memory
map, pin descriptions, timing characteristics and requirements, device mechanicals, etc.
SPRZ264— TMS320DM355 DMSoC Silicon Errata Describes the known exceptions to the functional
specifications for the TMS320DM355 DMSoC.
SPRUFB3— TMS320DM355 ARM Subsystem Reference Guide This document describes the ARM
Subsystem in the TMS320DM355 Digital Media System-on-Chip (DMSoC). The ARM subsystem is
designed to give the ARM926EJ-S (ARM9) master control of the device. In general, the ARM is
responsible for configuration and control of the device; including the components of the ARM
Subsystem, the peripherals, and the external memories.
SPRUED1— TMS320DM35x DMSoC Asynchronous External Memory Interface (EMIF) Reference
Guide This document describes the asynchronous external memory interface (EMIF) in the
TMS320DM35x Digital Media System-on-Chip (DMSoC). The EMIF supports a glueless interface to
a variety of external devices.
SPRUED2— TMS320DM35x DMSoC Universal Serial Bus (USB) Controller Reference Guide This
document describes the universal serial bus (USB) controller in the TMS320DM35x Digital Media
System-on-Chip (DMSoC). The USB controller supports data throughput rates up to 480 Mbps. It
provides a mechanism for data transfer between USB devices and also supports host negotiation.
SPRUED3— TMS320DM35x DMSoC Audio Serial Port (ASP) Reference Guide This document
describes the operation of the audio serial port (ASP) audio interface in the TMS320DM35x Digital
Media System-on-Chip (DMSoC). The primary audio modes that are supported by the ASP are the
AC97 and IIS modes. In addition to the primary audio modes, the ASP supports general serial port
receive and transmit operation, but is not intended to be used as a high-speed interface.
6
Preface
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
TMS320DM355 Digital Media System-on-Chip (DMSoC)
SPRUED4— TMS320DM35x DMSoC Serial Peripheral Interface (SPI) Reference Guide This
document describes the serial peripheral interface (SPI) in the TMS320DM35x Digital Media
System-on-Chip (DMSoC). The SPI is a high-speed synchronous serial input/output port that allows
a serial bit stream of programmed length (1 to 16 bits) to be shifted into and out of the device at a
programmed bit-transfer rate. The SPI is normally used for communication between the DMSoC
and external peripherals. Typical applications include an interface to external I/O or peripheral
expansion via devices such as shift registers, display drivers, SPI EPROMs and analog-to-digital
converters.
SPRUED9— TMS320DM35x DMSoC Universal Asynchronous Receiver/Transmitter (UART)
Reference Guide This document describes the universal asynchronous receiver/transmitter
(UART) peripheral in the TMS320DM35x Digital Media System-on-Chip (DMSoC). The UART
peripheral performs serial-to-parallel conversion on data received from a peripheral device, and
parallel-to-serial conversion on data received from the CPU.
SPRUEE0— TMS320DM35x DMSoC Inter-Integrated Circuit (I2C) Peripheral Reference Guide This
document describes the inter-integrated circuit (I2C) peripheral in the TMS320DM35x Digital Media
System-on-Chip (DMSoC). The I2C peripheral provides an interface between the DMSoC and other
devices compliant with the I2C-bus specification and connected by way of an I2C-bus. External
components attached to this 2-wire serial bus can transmit and receive up to 8-bit wide data to and
from the DMSoC through the I2C peripheral. This document assumes the reader is familiar with the
I2C-bus specification.
SPRUEE2— TMS320DM35x DMSoC Multimedia Card (MMC)/Secure Digital (SD) Card Controller
Reference Guide This document describes the multimedia card (MMC)/secure digital (SD) card
controller in the TMS320DM35x Digital Media System-on-Chip (DMSoC). The MMC/SD card is
used in a number of applications to provide removable data storage. The MMC/SD controller
provides an interface to external MMC and SD cards. The communication between the MMC/SD
controller and MMC/SD card(s) is performed by the MMC/SD protocol.
SPRUEE4— TMS320DM35x DMSoC Enhanced Direct Memory Access (EDMA) Controller Reference
Guide This document describes the operation of the enhanced direct memory access (EDMA3)
controller in the TMS320DM35x Digital Media System-on-Chip (DMSoC). The EDMA controller's
primary purpose is to service user-programmed data transfers between two memory-mapped slave
endpoints on the DMSoC.
SPRUEE5— TMS320DM35x DMSoC 64-bit Timer Reference Guide This document describes the
operation of the software-programmable 64-bit timers in the TMS320DM35x Digital Media
System-on-Chip (DMSoC). Timer 0, Timer 1, and Timer 3 are used as general-purpose (GP) timers
and can be programmed in 64-bit mode, dual 32-bit unchained mode, or dual 32-bit chained mode;
Timer 2 is used only as a watchdog timer. The GP timer modes can be used to generate periodic
interrupts or enhanced direct memory access (EDMA) synchronization events and Real Time
Output (RTO) events (Timer 3 only). The watchdog timer mode is used to provide a recovery
mechanism for the device in the event of a fault condition, such as a non-exiting code loop.
SPRUEE6— TMS320DM35x DMSoC General-Purpose Input/Output (GPIO) Reference Guide This
document describes the general-purpose input/output (GPIO) peripheral in the TMS320DM35x
Digital Media System-on-Chip (DMSoC). The GPIO peripheral provides dedicated general-purpose
pins that can be configured as either inputs or outputs. When configured as an input, you can
detect the state of the input by reading the state of an internal register. When configured as an
output, you can write to an internal register to control the state driven on the output pin.
SPRUEE7— TMS320DM35x DMSoC Pulse-Width Modulator (PWM) Reference Guide This document
describes the pulse-width modulator (PWM) peripheral in the TMS320DM35x Digital Media
System-on-Chip (DMSoC).
SPRUEH7— TMS320DM35x DMSoC DDR2/Mobile DDR (DDR2/mDDR) Memory Controller
Reference Guide This document describes the DDR2 / mobile DDR memory controller in the
TMS320DM35x Digital Media System-on-Chip (DMSoC). The DDR2 / mDDR memory controller is
used to interface with JESD79D-2A standard compliant DDR2 SDRAM and mobile DDR devices.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Read This First
7
www.ti.com
TMS320DM355 Digital Media System-on-Chip (DMSoC)
SPRUF71— TMS320DM35x DMSoC Video Processing Front End (VPFE) Users Guide This document
describes the Video Processing Front End (VPFE) in the TMS320DM35x Digital Media
System-on-Chip (DMSoC).
SPRUF72— TMS320DM35x DMSoC Video Processing Back End (VPBE) Users Guide This document
describes the Video Processing Back End (VPBE) in the TMS320DM35x Digital Media
System-on-Chip (DMSoC).
SPRUF74— TMS320DM35x DMSoC Real Time Out (RTO) Controller Reference Guide This document
describes the Real Time Out (RTO) controller in the TMS320DM35x Digital Media System-on-Chip
(DMSoC).
SPRUFC8— TMS320DM355 DMSoC Peripherals Overview Reference Guide This document provides
an overview of the peripherals in the TMS320DM355 Digital Media System-on-Chip (DMSoC).
The following documents describe TMS320DM35x Digital Media System-on-Chip (DMSoC) that are not
available by literature number. Copies of these documents are available (by title only) on the internet at
www.ti.com. Contact your TI representative for Extranet access.
8
—
TMS320DM35x DDR2 / mDDR Board Design Application Note This provides board design
recommendations and guidelines for DDR2 and mobile DDR.
—
TMS320DM35x USB Board Design and Layout Guidelines Application Note This provides
board design recommendations and guidelines for high speed USB.
Read This First
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Reference Guide
SPRUED4B – May 2006 – Revised October 2007
Serial Peripheral Interface (SPI)
1
Introduction
This document describes the serial peripheral interface (SPI) in the TMS320DM35x Digital Media
System-on-Chip (DMSoC).
1.1
Purpose of the Peripheral
The SPI is a high-speed synchronous serial input/output port that allows a serial bit stream of programmed
length (1 to 16 bits) to be shifted into and out of the device at a programmed bit-transfer rate. The SPI is
normally used for communication between the TMS320DM35x DMSoC and external peripherals. Typical
applications include an interface to external I/O or peripheral expansion via devices such as shift registers,
display drivers, SPI EPROMs and analog-to-digital converters.
The SPI allows serial communication with other SPI devices through a 3-pin or 4-pin mode interface. The
DM35x DMSoC implementation supports multichip-select operation for up to two SPI slave devices. The
SPI operates as a master SPI device only.
1.2
Features
The SPI has the following features:
• 16-bit shift register
• Receive buffer register
• 8-bit clock prescaler
• Programmable SPI clock frequency range
• Programmable character length (2 to 16 bits)
• Programmable clock phase (delay or no delay)
• Programmable clock polarity (high or low)
• Two chip select signals (SPI_EN0 and SPI_EN1) provide the ability to control two slave devices
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
9
www.ti.com
Peripheral Architecture
1.3
Functional Block Diagram
A block diagram of the major components of the SPI is shown in Figure 1.
Figure 1. Serial Peripheral Interface (SPI) Block Diagram
SPI_DO
16−bit Shift Register SPIDAT1
Write by CPU or EDMA
16
Read by CPU or EDMA 16
Read by CPU or EDMA
16
SPUBUF
16
SPIEMU
16
Character Length (CHARLENn)
Clock Polarity (POLARITYn)
SPI_DI
SPI_CLK
Control Logic and Interrupt
Generation
SPI_EN0
SPI_EN1
Clock Phase (PHASEn)
Interrupt to
ARM Interrupt Controller
EDMA Sync Events
SPI peripheral
clock
1.4
Clock Prescaler
(PRESCALEn)
Industry Standard(s) Compliance Statement
The programmable configuration capability of the SPI allows it to gluelessly interface to a variety of SPI
format devices. The SPI does not conform to a specific industry standard.
2
Peripheral Architecture
This section describes the architecture of the SPI.
2.1
Clock Control
The output clock generated (SPI_CLK) is a derivative of the internal peripheral clock that drives the SPI
Module divided by the PRESCALEn bit in the SPI data format register (SPIFMTn). For specific information
on the maximum SPI clock rate supported, refer to the SPI timings in the TMS320DM355 Digital Media
Processor Data Manual (literature number SPRS463). The phase and polarity of the SPI clock signal are
also programmable, these configurations are explained in Section 2.4.2. The clock rate is set
independently for each of the four software-programmable data formats. For more information on the data
formats, see Section 2.4.1. The clock rate for a given data format n is calculated as:
SPI_CLK frequency = [peripheral clock frequency ] / [PRESCALEn + 1]
10
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Peripheral Architecture
PRESCALEn is only supported for values >1, where the SPI clock rate is (peripheral clock frequency)/2.
2.2
Signal Descriptions
Table 1 shows the SPI pins used to interface to external devices. SPI_CLK, SPI_DO, and SPI_DI are
always used. The SPI_EN [1:0] pins are optional and may be used if the pins are present on the slave
device(s). The SPI_EN[1:0] pins are used to selectively enable slaves in a multiple slave system. The SPI
can be operated in a 3-pin or 4-pin mode configuration. In the 3-pin mode configuration, the SPI_EN[1:0]
pins are not used.
Table 1. Serial Peripheral Interface (SPI) Pins
2.3
Pin
Type
Function
SPI_CLK
Output
Serial clock
SPI_DI
Input
Serial data input
SPI_DO
Output
Serial data output
SPI_EN0
Output
Slave 0 chip select
SPI_EN1
Output
Slave 1 chip select
Pin Multiplexing
Most of the SPI pins are multiplexed with other device functions on the DM35x. For example, when the
SPI serial port functions are not selected, the pins may be used as general-purpose input/output (GPIO)
pins. For specific information on pin multiplexing, refer to the TMS320DM355 Digital Media Processor
Data Manual (literature number SPRS463).
2.4
SPI Operation
The SPI operates as a master SPI device only. The MASTER and CLKMOD bits in the SPI global control
register 1 (SPIGCR1) must be set to 1 for SPI module proper operation.
2.4.1
Data Formats
The SPI provides the capability to configure four independent data formats. These formats are configured
by programming the corresponding SPI data format register (SPIFMTn). In each data format, the following
characteristics of the SPI operation are selected:
• Character length from 2 to 16 bits: The character length is configured by the CHARLENn bit.
• Shift direction (MSB first or LSB first): The shift out direction is configured by the SHIFTDIRn bit.
• Clock polarity: The clock polarity is configured by the POLARITYn bit. The clock polarity is explained
in Section 2.4.2.
• Clock phase: The clock phase is configured by the PHASEn bit. The clock phase formats are
explained in Section 2.4.2.
The data format is chosen on each transaction, providing the capability to use different formats with
different slaves. Transmit data is written to the SPI shift register (SPIDAT1) and in the same write the data
word format select (DFSEL) bit in SPIDAT1 indicates which data format is to be used for the next
transaction. Alternatively, the data format can be configured once and applies to all transactions that
follow until the data format is changed.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
11
www.ti.com
Peripheral Architecture
2.4.1.1
Character Length
The character length is configured by the CHARLENn bit. Legal values are 2 bits (2h) to 16 bits (10h). The
character length is independently configured for each of the four data formats.
Transmit data is written to SPIDAT1. The transmit data must be written right-justified in the SPIDAT1 field.
The SPI automatically sends out the data correctly based on the chosen data format. Figure 2 shows an
example of how transmit data should be written for a 14-bit character length.
Figure 2. Right-Aligned Transmit Data in SPIDAT1 Field of the SPI Shift Register (SPIDAT1)
D15
D14
D13
D12
D11
D10
D9
D8
D7
D6
D5
D4
D3
D2
D1
D0
X
X
1
0
1
0
1
0
1
0
1
0
1
0
1
0
When a full word of receive data arrives in SPIDAT1, it is copied to the SPI buffer register (SPIBUF). The
received data is read from SPIBUF by the CPU or the EDMA. The received data in SPIBUF is
right-justified. If the character length is less than 16 bits, additional bits may be present in SPIBUF left
over from the transmitted data. But since the data in SPIBUF is right-justified and the character length is
known, the additional bits can be ignored. Figure 3 shows an example of how receive data will be aligned
for a 14-bit character length.
Figure 3. Right-Aligned Receive Data in SPIBUF Field of the SPI Buffer Register (SPIBUF)
D15
D14
D13
D12
D11
D10
D9
D8
D7
D6
D5
D4
D3
D2
D1
D0
X
X
1
0
1
0
1
0
1
0
1
0
1
0
1
0
2.4.1.2
Shift Direction
The shift out direction is configured as most-significant bit (MSB) first or least significant bit (LSB) first. The
shift out direction is selected by the SHIFTDIRn bit. The shift out direction is independently configured for
each of the four data formats.
• When SHIFTDIRn is 0, the transmit data is shifted out MSB first.
• When SHIFTDIRn is 1, the transmit data is shifted out LSB first.
2.4.2
Clock Polarity and Phase
The SPI provides the flexibility to program four different clock mode combinations that SPI_CLK may
operate, enabling a choice of the clock phase (delay or no delay) and the clock polarity (rising edge or
falling edge). When operating with PHASE active, the SPI makes the first bit of data available after
SPIDAT1 is written and before the first edge of SPI_CLK. The data input and output edges depend on the
values of both the POLARITY and PHASE bits as shown in Table 2.
Table 2. SPI Clocking Modes
SPIFMTn Bit
12
POLARITY
PHASE
0
0
Data is output on the rising edge of SPI_CLK. Input data is latched on the falling edge.
0
1
Data is output one half-cycle before the first rising edge of SPI_CLK and on subsequent falling
edges. Input data is latched on the rising edge of SPI_CLK.
1
0
Data is output on the falling edge of SPI_CLK. Input data is latched on the rising edge.
1
1
Data is output one half-cycle before the first falling edge of SPI_CLK and on subsequent rising
edges. Input data is latched on the falling edge of SPI_CLK.
Serial Peripheral Interface (SPI)
Action
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Peripheral Architecture
Figure 4 through Figure 7 show the four possible signals of SPI_CLK corresponding to each mode. Having
four signal options allows the SPI to interface with different types of serial devices. Also shown on the
footnotes in each figure is the SPI_CLK control bit polarity and phase values corresponding to each signal.
Figure 4. Clock Mode with POLARITY = 0 and PHASE = 0
Write SPIDAT1
SPI_CLK
1
2
3
4
5
6
7
8
SPI_DO
MSB
D6
D5
D4
D3
D2
D1
LSB
SPI_DI
D7
D6
D5
D4
D3
D2
D1
D0
Sample in
reception
Clock phase = 0 (SPI_CLK without delay)
− Data is output on the rising edge of SPI_CLK
− Input data is latched on the falling edge of SPI_CLK
− A write to SPIDAT1 starts SPI_CLK
Figure 5. Clock Mode with POLARITY = 0 and PHASE = 1
Write SPIDAT1
SPI_CLK
1
2
3
4
5
6
7
8
SPI_DO
MSB
D6
D5
D4
D3
D2
D1
LSB
SPI_DI
D7
D6
D5
D4
D3
D2
D1
D0
Sample in
reception
Clock phase = 1 (SPI_CLK with delay)
− Data is output one-half cycle before the first rising of SPI_CLK and on
subsequent falling edges of SPI_CLK
− Input data is latched on the rising edge of SPI_CLK
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
13
www.ti.com
Peripheral Architecture
Figure 6. Clock Mode with POLARITY = 1 and PHASE = 0
Write SPIDAT1
SPI_CLK
1
2
3
4
5
6
7
8
SPI_DO
MSB
D6
D5
D4
D3
D2
D1
LSB
SPI_DI
D7
D6
D5
D4
D3
D2
D1
D0
Sample in
reception
Clock phase = 0 (SPI_CLK without delay)
− Data is output on the falling edge of SPI_CLK
− Input data is latched on the rising edge of SPI_CLK
− A write to SPIDAT1 starts SPI_CLK
Figure 7. Clock Mode with POLARITY = 1 and PHASE = 1
Write SPIDAT1
SPI_CLK
1
2
3
4
5
6
7
8
SPI_DO
MSB
D6
D5
D4
D3
D2
D1
LSB
SPI_DI
D7
D6
D5
D4
D3
D2
D1
D0
Sample in
reception
Clock phase = 1 (SPI_CLK with delay)
− Data is output one-half cycle before the first falling edge of SPI_CLK
and on the subsequent rising edges of SPI_CLK
− Input data is latched on the falling edge of SPI_CLK
14
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Peripheral Architecture
Figure 8 shows an example of an SPI data transfer between two devices using a character length of 5 bits
and the different clock mode scenarios in 4-pin mode.
Figure 8. Five Bits per Character (Four-Pin Option)
Master SPI Interrupt flag
Slave SPI Interrupt flag
SPI_DI from slave
7
6
5
4
3
7
6
5
4
3
7
6
5
4
3
7
6
5
4
3
SPI_DO from
master
SPI_CLK signal options:
Clock polarity = 0
Clock phase = 0
Clock polarity = 0
Clock phase = 1
Clock polarity = 1
Clock phase = 0
Clock polarity = 1
Clock phase = 1
SPI_ENx
2.4.3
Chip Select Control
The SPI provides two chip select signals (SPI_EN0 and SPI_EN1) that are used to selectively enable
multiple slaves. The behavior of the chip selects is controlled by the CSNR and CSHOLD bits in SPIDAT1.
2.4.3.1
Enabling Chip Selects
The CSNR bit controls which chip selects are active during the transactions that follow. This bit is used to
enable either or both chip selects. To use the chip selects, the ENnFUN bit in the SPI pin control register
(SPIPC0) must be set to 1 for each chip select.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
15
www.ti.com
Peripheral Architecture
2.4.3.2
Holding Chip Selects Active Between Transactions
Some SPI slave devices require that chip selects remain active between transactions, such as serial
EEPROMs that use internal address counters, as long as the chip select is active. The CSHOLD bit
controls whether chip selects remain asserted between transactions or not.
• When CSHOLD = 0, the chip selects are deasserted between transactions.
• When CSHOLD = 1, the chip selects remain asserted between transactions as long as the chip select
information (controlled by the CSNR bits in SPIDAT1) has not changed since the last transaction. If the
chip select information is altered between transactions, the chip select is deasserted even if CSHOLD
= 1.
2.4.3.3
Programming Chip Select Setup and Hold Timing
The setup time between when the chip select signal goes active and the beginning of the transaction is
programmable using the C2TDELAY bit in the SPI delay register (SPIDELAY). The setup time is
[C2TDELAY + 2] cycles of the SPI peripheral clock (not the SPI_CLK).
The hold time between the end of the transaction and when the chip select signal goes inactive is
programmable using the T2CDELAY bit in SPIDELAY. The hold time is [T2CDELAY + 1] cycles of the SPI
peripheral clock (not the SPI_CLK).
If the CSHOLD function is active, the setup and hold delays are not applied between transactions where
the chip select remains asserted.
2.4.3.4
Inactive Chip Select State Control
The driven state of the chip select pins when no transaction is in progress is controlled by the ENnDEF
bits in the SPI default chip select register (SPIDEF).
• When ENnDEF = 0, the corresponding chip select is driven to logic 0 when no transaction is in
progress.
• When ENnDEF = 1, the corresponding chip select is driven to logic 1 when no transaction is in
progress.
2.4.4
SPI Operation: 3-Pin Mode
The minimum required number of signal connections for SPI communications is 3 pins: SPI_CLK, SPI_DI,
and SPI_DO. The chip select pins (SPI_EN0 and SPI_EN1) are not used in 3-pin mode. This connection
could be used when a single slave is present and, therefore, no chip selects are required. The SPI
operates as a SPI master and provides the serial clock on the SPI_CLK pin during the current word
transfer and stops between word transfers. Data is transmitted on the SPI_DO pin and received from the
SPI_DI pin, as shown in Figure 9.
Right-aligned data written to the SPI shift register (SPIDAT1) initiates data transmission on the SPI_DO
pin. Simultaneously, received data is shifted through the SPI_DI pin into the least-significant bit (LSB) of
SPIDAT1. The SPI applies data format selected in the DFSEL bit of SPIDAT1 as the format for the
transaction. When the selected number of bits have been transferred, the received data is copied to the
SPI buffer register (SPIBUF) for the CPU or EDMA to read. Data is stored right-justified in SPIBUF.
When the specified number of bits is shifted through SPIDAT1, the following events occur:
• The receive interrupt flag (RXINTFLAG) bit in the SPI flag register (SPIFLG) is set to 1.
• The newly received SPIDAT1 contents transfer to SPIBUF.
• An interrupt is asserted, if the receive interrupt enable (RXINTEN) bit in the SPI interrupt register
(SPIINT) is set to 1.
16
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Peripheral Architecture
Figure 9. SPI Operation (3-Pin Option)
Master
(Master = 1; CLKMOD = 1)
Slave
SPI_DO
SPISIMO
SPI_DI
MSB
LSB
SPI_CLK
SPIDAT1
SPISOMI
SPICLK
Write to
Write to SPIDAT1
SPICLK
SIMO
SOMI
2.4.5
SPI Operation: 4-Pin Mode
The 3-pin mode and the 4-pin mode of the SPI are similar, except that the 4-pin mode uses the chip select
pins (SPI_EN0 and SPI_EN1) to enable communication with multiple chip selects. Figure 10 shows how
the 4-pin mode is connected. For detailed information on how the chip selects are controlled and used,
see Section 2.4.3.
Figure 10. SPI Operation (4-Pin Option)
Master
(Master = 1; CLKMOD = 1)
Slave
SPI_DO
SPISIMO
SPI_DI
MSB
LSB
SPISOMI
SPIDAT1
SPI_CLK
SPICLK
Write to
SPIDAT1
SPI_ENn
SPISCS
Write to SPIDAT1
SPICSCS
SPICLK
SPISIMO
SPISOMI
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
17
www.ti.com
Peripheral Architecture
2.5
Reset Considerations
This section provides the software and hardware reset considerations.
2.5.1
Software Reset Considerations
In the event of an emulator software reset, the SPI module register values are not affected.
The SPI module contains a software reset (RESET) bit in the SPI global control register 0 (SPIGCR0) that
is used to reset the SPI module. As a result of a reset, the SPI module register values go to their reset
state. The RESET bit must be set before any operation on the SPI is done.
2.5.2
Hardware Reset Considerations
In the event of a hardware reset, the SPI module register values go to their reset state and the application
software needs to reprogram the registers to the desired values.
There are two different methods to perform hardware reset that affects the SPI module register values.
One is a full device hardware reset that resets all the device modules and the second is an individual
peripheral hardware reset initiated by the Power and Sleep Controller (PSC) module. For information
about the operation of the PSC, see the TMS320DM355 DMSoC ARM Subsystem Reference Guide
(SPRUFB3).
2.6
Initialization
The following section provides procedures for initializing the SPI in 3-pin or 4-pin mode.
2.6.1
3-Pin Mode Initialization
1. Make sure the SPI module is in reset by clearing the RESET bit in the SPI global control register 0
(SPIGCR0) to 0.
2. Remove the SPI peripheral from reset by setting the RESET bit in SPIGCR0 to 1.
3. Enable the CLKMOD and MASTER bits in the SPI global control register 1 (SPIGCR1).
4. Enable the SPI_DI, SPI_DO, and SPI_CLK pins by setting the corresponding bits in the SPI pin control
register (SPIPC0).
5. Configure the desired data format in the SPI data format register (SPIFMTn).
a. Program the clock prescale value in the PRESCALEn bit.
b. Program the character size in the CHARLENn bit.
c. Set the SPI clock PHASEn and POLARITYn bits.
d. Set the shift direction in the SHIFTDIRn bit.
6. Select the preconfigured data format using the DFSEL bit in the SPI shift register (SPIDAT1).
7. Enable the desired interrupts, if any, in the SPI interrupt register (SPIINT).
8. Select whether you want the interrupt events mapped to INT0 or INT1 using the selection bits in the
SPI interrupt level register (SPILVL).
9. If using the EDMA to perform the transfers, setup and enable the EDMA channels for transmit or
receive.
10. Enable the SPIENA bit in SPIGCR1.
11. If using the EDMA, set the DMAREQEN bit in SPIINT to 1 initiating the EDMA to start writing to
SPIDAT1; therefore, initiating the data transfer.
12. Data is ready to be transferred using the CPU by writing to SPIDAT1.
18
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Peripheral Architecture
2.6.2
4-Pin Mode Initialization
1. Make sure the SPI module is in reset by clearing the RESET bit in the SPI global control register 0
(SPIGCR0) to 0.
2. Remove the SPI peripheral from reset by setting the RESET bit in SPIGCR0 to 1.
3. Enable the CLKMOD and MASTER bits in the SPI global control register 1 (SPIGCR1).
4. Enable the SPI_DI, SPI_DO, and SPI_CLK pins and the necessary chip select pins (SPI_EN0 and
SPI_EN1) by setting the corresponding bits in the SPI pin control register (SPIPC0).
5. Configure the desired data format in the SPI data format register (SPIFMTn).
a. Program the clock prescale value in the PRESCALEn bit.
b. Program the character size in the CHARLENn bit.
c. Set the SPI clock PHASEn and POLARITYn bits.
d. Set the shift direction in the SHIFTDIRn bit.
6. Select the preconfigured data format using the DFSEL bit in the SPI shift register (SPIDAT1).
7. If needed, configure the setup or hold time for the chip select lines using the C2TDELAY or
T2CDELAY bits in the SPI delay register (SPIDELAY).
8. Select the desired chip select number. The CSNR field in SPIDAT1 defines the chip select that shall be
activated during the data transfer. Note that the SPI_ENn signals are active low.
9. Setup the default chip select pin value when chip select lines are inactive using the ENnDEF bits in the
SPI default chip select register (SPIDEF).
10. Enable the desired interrupts, if any, in the SPI interrupt register (SPIINT).
11. Select whether you want the interrupt events mapped to INT0 or INT1 using the selection bits in the
SPI interrupt level register (SPILVL).
12. If using the EDMA to perform the transfers, setup and enable the EDMA channels for transmit or
receive.
13. Enable the SPIENA bit in SPIGCR1.
14. If using the EDMA, set the DMAREQEN bit in SPIINT to 1 initiating the EDMA to start writing to
SPIDAT1; therefore, initiating the data transfer.
15. Data is ready to be transferred using the CPU by writing to SPIDAT1.
2.7
Interrupt Support
The SPI module outputs two interrupts that are routed to the ARM CPU interrupt controller, SPIINT0 and
SPIINT1. Each of the interrupt events causes a CPU interrupt on SPIINT0 or SPIINT1. The SPI interrupt
system is controlled by three registers:
• The SPI interrupt level register (SPILVL) controls which events (SPIINT0 or SPIINT1) are assigned to
each interrupt.
• The SPI interrupt register (SPIINT) contains bits to selectively enable/disable each interrupt event.
• The SPI flag register (SPIFLG) contains flags indicating when each of the interrupt conditions have
occurred.
Multiple interrupt sources can be assigned to the same CPU interrupt. To identify the interrupt source in
the SPI peripheral, the CPU reads the SPI flag register (SPIFLG) or the INTVECTn code in the SPI
interrupt vector register n (IINTVECTn).
2.7.1
Interrupt Events and Requests
2.7.1.1
Receive Interrupt
The receive interrupt occurs when a data character has been received and copied in the SPI buffer
register (SPIBUF). To enable the SPI receive interrupt, set the RXINTEN bit in the SPI interrupt register
(SPIINT) to 1. To assign the receive interrupt to occur on SPIINT0, clear the RXINTLVL bit in the SPI
interrupt level register (SPILVL) to 0; to assign the receive interrupt to occur on SPIINT1, set the
RXINTLVL bit in SPILVL to 1.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
19
www.ti.com
Peripheral Architecture
The occurrence of the receive interrupt is recorded in the RXINTFLAG bit in the SPI flag register
(SPIFLG). This flag is cleared by reading SPIBUF, writing a 1 to the RXINTFLAG bit, disabling the receive
interrupt, or a system reset.
2.7.1.2
Receive Overrun Interrupt
The receive overrun interrupt occurs when a data character has been received in the shift register before
the previous character has been read from the SPI buffer register (SPIBUF). To enable the SPI receive
overrun interrupt, set the OVRNINTEN bit in the SPI interrupt register (SPIINT) to 1. To assign the receive
overrun interrupt to occur on SPIINT0, clear the OVRNINTLVL bit in the SPI interrupt level register
(SPILVL) to 0; to assign the receive overrun interrupt to occur on SPIINT1, set the OVRNINTLVL bit in
SPILVL to 1.
The occurrence of the receive overrun interrupt is recorded in the OVRNINTFLAG bit in the SPI flag
register (SPIFLG). This flag is cleared by writing a 1 to the OVRNINTFLAG bit, disabling the receive
overrun interrupt, or a system reset. Reading SPIBUF does not clear the OVRNINTFLAG bit.
2.7.1.3
Transmit Error Interrupt
The transmit error interrupt occurs when the internal data transmitted does not match the external data
bits sensed on the SPI_DO signal. This error is used as an indication of a fault on the SPI_DO line. To
enable the SPI transmit error interrupt, set the BITERRENA bit in the SPI interrupt register (SPIINT) to 1.
To assign the transmit error interrupt to occur on SPIINT0, clear the BITERRLVL bit in the SPI interrupt
level register (SPILVL) to 0; to assign the transmit error interrupt to occur on SPIINT1, set the BITERRLVL
bit in SPILVL to 1.
The occurrence of the transmit error interrupt is recorded in the BITERRFLG bit in the SPI flag register
(SPIFLG).
2.7.2
Interrupt Multiplexing
The total number of interrupts in DM35x exceeds 64, which is the maximum number of interrupts
supported by the ARM Interrupt Controller (AINTC) module. Therefore, several interrupts are multiplexed,
and you must use the register ARM_INTMUX in the System Control Module to select the interrupt source
for multiplexed interrupts. Some of the SPI peripheral interrupts are multiplexed. Refer to the
TMS320DM355 DMSoC ARM Subsystem Reference Guide (SPRUFB3) for more information on the
System Control Module and ARM Interrupt Controller.
2.8
EDMA Event Support
If handling the SPI message traffic on a character-by-character basis requires too much CPU overhead,
the SPI may use the system EDMA to receive or transmit data directly to or from memory.
The SPI module has two EDMA synchronization event outputs that go to the system EDMA, allowing
EDMA transfers to be triggered by SPI read receive or write transmit events. SPIXEVT is a transmit sync
event; SPIREVT is a receive sync event. The SPI module enables EDMA requests by enabling the DMA
request enable (DMAREQEN) bit in the SPI interrupt register (SPIINT).
When a character is being transmitted or received, the SPI signals the EDMA via the EDMA
synchronization event signal. The EDMA controller then performs the needed data manipulation. EDMA
transfers the data from the source programmed into the SPI shift register (SPIDAT1). Data is then read
from the SPI buffer register (SPIBUF), which automatically clears the RXINTFLAG bit in the SPI flag
register (SPIFLG).
In most cases, if the EDMA is being used to service received data from the SPI, the receive interrupt
enable (RXINTEN) bit in SPIINT should be cleared to 0. This prevents the CPU from both responding to
the received data in addition to the EDMA. For specific SPI synchronization event number and detailed
EDMA features, refer to the TMS320DM35x DMSoC Enhanced Direct Memory Access (EDMA) Controller
Reference Guide (SPRUEE4).
20
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Peripheral Architecture
2.9
Power Management
The SPI can be placed in reduced-power modes to conserve power during periods of low activity. The
power management of the SPI is controlled by the processor Power and Sleep Controller (PSC). The PSC
acts as a master controller for power management for all of the peripherals on the device. For detailed
information on power management procedures using the PSC, see the TMS320DM355 DMSoC ARM
Subsystem Reference Guide (SPRUFB3).
Since entering a low-power mode has the effect of suspending all state machine activities, care must be
taken when entering such modes to ensure that a valid state is entered when low-power mode is active.
As a result, application software must ensure that a low-power mode is not entered during a transmission
or reception of data.
2.10 SPI Internal Loop-Back Test Mode
CAUTION
The internal loop-back self-test mode should not be entered during a normal
data transaction or unpredictable operation may occur.
The internal loop-back self-test mode can be utilized to test the SPI transmit path and receive path. In this
mode, the transmit signal is internally fed back to the receiver and the SPI_DO, SPI_DI, and SPI_CLK
pins are disconnected. For example, the transmitted data is internally transferred to the corresponding
receive buffer while external signals remain unchanged. This mode allows the CPU to write into the
transmit buffer, and check that the receive buffer contains the correct transmit data. If an error occurs the
corresponding error is set within the status field. This capability can be useful during code development
and debug. The loop-back test mode is enabled by setting the LOOPBACK bit in the SPI global control
register 1 (SPIGCR1) to 1.
2.11 Emulation Considerations
The SPI module does not support soft or hard stop during emulation breakpoints. The SPI module will
continue to run if an emulation breakpoint is encountered.
During debug, read the SPI emulation register (SPIEMU) if you need to read the received data without
otherwise altering the state of the SPI peripheral. Reading the SPI buffer register (SPIBUF) causes the
flags in SPIBUF to be cleared; reading SPIEMU will read the receive data without altering the flags in
SPIBUF.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
21
www.ti.com
Registers
3
Registers
Table 3 lists the memory-mapped registers for the SPI. See the device-specific data manual for the
memory address of these registers. All other register offset addresses not listed in Table 3 should be
considered as reserved locations and the register contents should not be modified.
Table 3. SPI Registers
3.1
Offset
Acronym
Register Description
Section
00h
SPIGCR0
SPI global control register 0
Section 3.1
04h
SPIGCR1
SPI global control register 1
Section 3.2
08h
SPIINT
SPI interrupt register
Section 3.3
0Ch
SPILVL
SPI interrupt level register
Section 3.4
10h
SPIFLG
SPI flag register
Section 3.5
14h
SPIPC0
SPI pin control register
Section 3.6
1Ch
SPIPC2
SPI pin control register 2
Section 3.7
3Ch
SPIDAT1
SPI shift register
Section 3.8
40h
SPIBUF
SPI buffer register
Section 3.9
44h
SPIEMU
SPI emulation register
Section 3.10
48h
SPIDELAY
SPI delay register
Section 3.11
4Ch
SPIDEF
SPI default chip select register
Section 3.12
50h
SPIFMT0
SPI data format register 0
Section 3.13
54h
SPIFMT1
SPI data format register 1
Section 3.13
58h
SPIFMT2
SPI data format register 2
Section 3.13
5Ch
SPIFMT3
SPI data format register 3
Section 3.13
60h
INTVECT0
SPI interrupt vector register 0
Section 3.14
64h
INTVECT1
SPI interrupt vector register 1
Section 3.15
SPI Global Control Register 0 (SPIGCR0)
The SPI global control register 0 (SPIGCR0) is shown in Figure 11 and described in Table 4.
Figure 11. SPI Global Control Register 0 (SPIGCR0)
31
16
Reserved
R-0
15
1
0
Reserved
RESET
R-0
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 4. SPI Global Control Register 0 (SPIGCR0) Field Descriptions
Bit
31-1
0
22
Field
Reserved
Value
0
RESET
Description
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Reset bit for the SPI module. RESET must be set before any operation on SPI is done.
0
SPI is in reset state.
1
SPI is out of reset state.
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.2
SPI Global Control Register 1 (SPIGCR1)
The SPI global control register 1 (SPIGCR1) is shown in Figure 12 and described in Table 5.
Figure 12. SPI Global Control Register 1 (SPIGCR1)
31
25
24
23
17
16
Reserved
SPIENA
Reserved
LOOPBACK
R-0
R/W-0
R-0
R/W-0
15
1
0
Reserved
2
CLKMOD
MASTER
R-0
R/W-0
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 5. SPI Global Control Register 1 (SPIGCR1) Field Descriptions
Bit
31-25
24
23-17
16
Field
Reserved
Value
0
SPIENA
Reserved
Description
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
SPI enable. Holds the SPI in a reset state after a chip reset. The SPI is enabled only after a 1 is
written to this bit. This bit must be set to 1 after all other SPI configuration bits have been written.
This prevents an invalid operation of the SPI while the clock polarity is being changed.
0
SPI is in reset. The RXINTFLAG and OVRNINTFLG bits in the SPI flag register (SPIFLG) are also
held in reset mode and forced to 0. SPI_CLK is disabled. The SPI shift register (SPIDAT1) is held
in reset mode and forced to 0.
1
Activates SPI.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
LOOPBACK
Internal loop-back test mode. The internal self-test option is enabled by setting this bit to 1. If the
SPI_DO and SPI_DI pins are configured with SPI functionality, then the SPI_DO pin is internally
connected to the SPI_DI pin. The transmit data is looped back as receive data and is stored in the
receive field of the concerned buffer.
Externally, during loop-back operation, the SPI_CLK pin outputs an inactive value and SPI_DI
remains in a high-impedance state. The SPI has to be initialized in master mode before the
loop-back is selected. If a data transfer is ongoing, errors may result.
15-2
Reserved
1
CLKMOD
0
0
Internal loop-back test mode is disabled.
1
Internal loop-back test mode is enabled.
0
Reserved. The reserved bit location is always read as 0. This field must be written as zeroes.
Clock mode. This bit must be set for the SPI module to operate.
0
Reserved
1
SPI module clock mode is enabled.
MASTER
Master mode. This bit must be set for the SPI module to operate.
0
Reserved
1
SPI module master mode is enabled.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
23
www.ti.com
Registers
3.3
SPI Interrupt Register (SPIINT)
The SPI interrupt register (SPIINT) is shown in Figure 13 and described in Table 6.
Figure 13. SPI Interrupt Register (SPIINT)
31
17
15
9
16
Reserved
DMAREQEN
R-0
R/W-0
8
Reserved
RXINTEN
R-0
R/W-0
7
6
5
Rsvd OVRNINTEN Rsvd
R-0
R/W-0
R-0
4
3
0
BITERRENA
Reserved
R/W-0
R-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 6. SPI Interrupt Register (SPIINT) Field Descriptions
Bit
31-17
16
Reserved
Value
0
DMAREQEN
15-9
Reserved
8
RXINTEN
7
Reserved
6
OVRNINTEN
5
Reserved
4
BITERRENA
3-0
24
Field
Reserved
Description
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
DMA request enable. Enables the DMA request signal to be generated for both receive and
transmit channels. When using the SPI module with the EDMA, it is important that the related
EDMA channels are configured and enabled before enabling this bit.
0
DMA is not used.
1
DMA is used.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Receive interrupt enable. An interrupt is generated when the RXINTFLAG bit in the SPI flag register
(SPIFLG) is set by hardware; otherwise, no interrupt is generated.
0
Interrupt is not generated.
1
Interrupt is generated.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Overrun interrupt enable. An interrupt is generated when the OVRNINTFLG bit in the SPI flag
register (SPIFLG) is set by hardware; otherwise, no interrupt is generated.
0
Overrun interrupt is not generated.
1
Overrun interrupt is generated.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Enables interrupt on bit error.
0
No interrupt asserted upon bit error.
1
Enables an interrupt on a bit error (BITERR = 1).
0
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.4
SPI Interrupt Level Register (SPILVL)
The SPI interrupt level register (SPILVL) is shown in Figure 14 and described in Table 7.
Figure 14. SPI Interrupt Level Register (SPILVL)
31
16
Reserved
R-0
15
9
8
Reserved
RXINTLVL
R-0
R/W-0
7
6
5
Rsvd OVRNINTLVL Rsvd
R-0
R/W-0
4
3
0
BITERRLVL
Reserved
R/W-0
R-0
R-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 7. SPI Interrupt Level Register (SPILVL) Field Descriptions
Bit
Field
31-9
Reserved
8
RXINTLVL
7
Reserved
6
OVRNINTLVL
5
Reserved
4
BITERRLVL
3-0
Reserved
Value
0
Description
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Receive interrupt level.
0
Receive interrupt is mapped to interrupt line INT0.
1
Receive interrupt is mapped to interrupt line INT1.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Receive overrun interrupt level.
0
Receive overrun interrupt is mapped to interrupt line INT0.
1
Receive overrun interrupt is mapped to interrupt line INT1.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Bit error interrupt level.
0
Bit error interrupt is mapped to interrupt line INT0.
1
Bit error interrupt is mapped to interrupt line INT1.
0
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
25
www.ti.com
Registers
3.5
SPI Flag Register (SPIFLG)
The SPI flag register (SPIFLG) is shown in Figure 15 and described in Table 8.
Figure 15. SPI Flag Register (SPIFLG)
31
16
Reserved
R-0
15
9
Reserved
8
7
RXINTFLAG Rsvd
R-0
R/W1C-0
R-0
6
OVRNINTFLG
R/W1C-0
5
4
3
Rsvd BITERRFLG
R-0
RC-0
0
Reserved
R-0
LEGEND: R/W = Read/Write; R = Read only; RC = Read bit to clear; W1C = Write 1 to clear (writing 0 has no effect); -n = value after reset
Table 8. SPI Flag Register (SPIFLG) Field Descriptions
Bit
31-9
8
Field
Reserved
Value
0
RXINTFLAG
Description
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Receive interrupt flag. RXINTFLAG is set when a word is received and copied into the SPI buffer
register (SPIBUF). If the RXINTEN bit in the SPI interrupt register (SPIINT) is set to 1 (enabled), an
interrupt is also generated. During emulation mode, a read of the SPI emulation register (SPIEMU)
does not clear RXINTFLAG. This bit is cleared by:
•
•
•
•
7
Reserved
6
OVRNINTFLG
Reading SPIBUF
Writing a 1 to this bit
Writing a 0 to the SPIENA bit in the SPI global control register 1 (SPIGCR1)
System reset
0
Interrupt condition did not occur.
1
Interrupt condition did occur.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Receiver overrun flag. OVRNINTFLG is set by the SPI hardware when an operation completes
before the previous character has been read from the buffer. OVRNINTFLG bit indicates that the
last received character has been overwritten and therefore lost. If the OVRNINTEN bit in the SPI
interrupt register (SPIINT) is set to 1 (enabled), an interrupt is also generated. This bit is cleared by:
• Reading INTVECT0 or INTVECT1
• Writing a 1 to this bit
• Writing a 0 to the SPIENA bit in the SPI global control register 1 (SPIGCR1)
• System reset
Reading the SPIBUF register does not clear this bit.
5
Reserved
4
BITERRFLG
3-0
26
Reserved
0
Overrun condition did not occur.
1
Overrun condition did occur.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Bit error flag. The SPI samples the signal of the transmit pin (master: SPI_DO) at the receive point
(half clock cycle after transmit point). If the sampled value differs from the transmitted value, a bit
error is detected and the BITERRFLG bit is set and the BITERR bit in the SPI buffer register
(SPIBUF) is set. Possible reasons for a bit error are a high bit rate/capacitive load or another
master/slave trying to transmit at the same time. If the BITERRENA bit in the SPI interrupt register
(SPIINT) is set to 1 (enabled) and the BITERR bit (in SPIBUF) is set to 1, an interrupt is also
generated. This bit is cleared by reading the bit.
0
Bit error did not occur.
1
Bit error did occur.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.6
SPI Pin Control Register (SPIPC0)
The SPI pin control register (SPIPC0) is shown in Figure 16 and described in Table 9.
Figure 16. SPI Pin Control Register (SPIPC0)
31
16
Reserved
R-0
15
12
11
Reserved
DIFUN
R-0
R/W-0
10
9
DOFUN CLKFUN
R/W-0
R/W-0
8
2
Reserved
1
0
EN1FUN EN0FUN
R-0
R/W-0
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 9. SPI Pin Control Register (SPIPC0) Field Descriptions
Bit
31-12
11
10
9
Field
Reserved
0
DIFUN
Reserved
EN1FUN
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
SPI data input (SPI_DI) functional pin. This bit must be set for the SPI module to operate.
Reserved
1
SPI_DI is a functional pin.
SPI data output (SPI_DO) functional pin. This bit must be set for the SPI module to operate.
0
Reserved
1
SPI_DO is a functional pin.
CLKFUN
1
Description
0
DOFUN
8-2
0
Value
SPI clock (SPI_CLK) functional pin. This bit must be set for the SPI module to operate.
0
Reserved
1
SPI_CLK is a functional pin.
0
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
SPI slave 1 (SPI_EN1) functional pin. This bit must be set for the SPI module to communicate with
slave SPI devices.
0
Reserved
1
SPI_EN1 is a functional pin.
EN0FUN
SPI slave 0 (SPI_EN0) functional pin. This bit must be set for the SPI module to communicate with
slave SPI devices.
0
Reserved
1
SPI_EN0 is a functional pin.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
27
www.ti.com
Registers
3.7
SPI Pin Control Register 2 (SPIPC2)
The SPI pin control register 2 (SPIPC2) is shown in Figure 17 and described in Table 10.
Figure 17. SPI Pin Control Register 2 (SPIPC2)
31
16
Reserved
R-0
15
11
10
9
1
0
Reserved
12
DIDIN
DODIN
CLKDIN
8
Reserved
2
EN1DIN
EN0DIN
R-0
R-x
R-x
R-x
R-0
R-x
R-x
LEGEND: R = Read only; -n = value after reset; -x = value is indeterminate after reset
Table 10. SPI Pin Control Register 2 (SPIPC2) Field Descriptions
Bit
31-12
11
10
9
8-2
1
0
28
Field
Reserved
Value
0
DIDIN
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
SPI data input (SPI_DI) pin value. This bit reflects the value on the SPI_DI pin.
0
Current value on SPI_DI pin is logic 0.
1
Current value on SPI_DI pin is logic 1.
DODIN
SPI data output (SPI_DO) pin value. This bit reflects the value on the SPI_DO pin.
0
Current value on SPI_DO pin is logic 0.
1
Current value on SPI_DO pin is logic 1.
CLKDIN
Reserved
Description
SPI clock (SPI_CLK) pin value. This bit reflects the value on the SPI_CLK pin.
0
Current value on SPI_CLK pin is logic 0.
1
Current value on SPI_CLK pin is logic 1.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
EN1DIN
SPI slave 1 (SPI_EN1) pin value. This bit reflects the value on the SPI_EN1 pin.
0
Current value on SPI_EN1 pin is logic 0.
1
Current value on SPI_EN1 pin is logic 1.
EN0DIN
SPI slave 0 (SPI_EN0) pin value. This bit reflects the value on the SPI_EN0 pin.
0
Current value on SPI_EN0 pin is logic 0.
1
Current value on SPI_EN0 pin is logic 1.
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.8
SPI Shift Register (SPIDAT1)
The SPI shift register (SPIDAT1) is shown in Figure 18 and described in Table 11.
Figure 18. SPI Shift Register (SPIDAT1)
31
29
28
27
26
25
24
23
18
17
16
Reserved
CSHOLD
Reserved
DFSEL
Reserved
CSNR
R-0
R/W-0
R-0
R/W-0
R-0
R/W-0
15
0
SPIDAT1
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 11. SPI Shift Register (SPIDAT1) Field Descriptions
Bit
Field
31-29
Reserved
28
CSHOLD
27-26
Reserved
25-24
DFSEL
23-18
Reserved
17-16
CSNR
15-0
SPIDAT1
Value
0
Description
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Chip select hold mode. CSHOLD is considered in 4-pin mode only. CSHOLD defines the behavior
of the chip select line at the end of a transfer.
0
Chip select signal is deactivated at the end of a transfer after the T2CDELAY time has passed. If
two consecutive transfers are dedicated to the same chip select, this chip select signal is shortly
deactivated before it is activated again.
1
Chip select signal is held active at the end of a transfer until a control field with new data and
control information is loaded into the SPIDAT1 bit. If the new chip select information equals the
previous information, the active chip select signal is extended until the end of transfer with
CSHOLD cleared or until the chip select information changes.
0
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
0-3h
Data word format select.
0
Data format 0 is selected.
1h
Data format 1 is selected.
2h
Data format 2 is selected.
3h
Data format 3 is selected.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
0-3h
Chip select number. CSNR defines the chip select that shall be activated during the data transfer.
Note that the SPI_ENn signals are active low.
0
Both chip select SPI_EN0 and SPI_EN1 are selected.
1h
Chip select SPI_EN1 is selected only.
2h
Chip select SPI_EN0 is selected only.
3h
No chip select is used.
0-FFFFh
SPI shift data 1. This field makes up the SPI shift register. Data is shifted out of the MSB (bit 15)
and into the LSB (bit 0). The SPIENA bit in the SPI global control register 1 (SPIGCR1) must be
set to 1 before this register can be written to. Writing a 0 to the SPIENA bit forces the SPIDAT1 bit
to 0.
A write to this field drives the SPI_EN[1:0] signal low if the SPI_EN[1:0] signals are enabled in the
SPI pin control register (SPIPC0).
When data is read from this field, the value is indeterminate because of the shift operation. The
value in the SPI buffer register (SPIBUF) should be read after the shift operation is complete to
determine what data was shifted into SPIDAT1.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
29
www.ti.com
Registers
3.9
SPI Buffer Register (SPIBUF)
The SPI buffer register (SPIBUF) is shown in Figure 19 and described in Table 12. Reading SPIBUF
clears the OVRNINTFLG and RXINTFLAG bits in the SPI flag register (SPIFLG).
Figure 19. SPI Buffer Register (SPIBUF)
31
30
29
28
RXEMPTY
RXOVR
TXFULL
BITERR
27
Reserved
18
17
LCSNR
16
R-1
RC-0
R-0
RC-0
R-0
R-0
15
0
SPIBUF
R-x
LEGEND: R/W = Read/Write; R = Read only; RC = Read bit to clear; -n = value after reset; -x = value is indeterminate after reset
Table 12. SPI Buffer Register (SPIBUF) Field Descriptions
Bit
Field
31
RXEMPTY
30
29
28
Value
Description
Receive data buffer empty. This is a read-only flag. When the host reads an SPIBUF field or the
entire SPIBUF, this automatically sets the RXEMPTY bit. When a data transfer has been finished
and the received data is copied into SPIBUF, the RXEMPTY bit is cleared.
0
Data is received and copied into an SPIBUF field.
1
No data received since last reading SPIBUF.
RXOVR
Receive data buffer overrun. This is a read-to-clear only flag, that is, reading this bit automatically
clears the bit. When a data transfer has been finished and the received data is copied into SPIBUF
with the RXEMPTY bit already cleared, the RXOVR bit is set.
0
No receive data overrun condition occurred since last time reading the status field.
1
A receive data overrun condition occurred since last time reading the status field.
TXFULL
Transmit data buffer full. This is a read-only flag. Writing into SPIDAT1 bits in the SPI shift register
(SPIDAT1) automatically sets the TXFULL bit. After transfer of the transmit data the TXFULL flag
is cleared.
0
No new transmit data from the host since previous transfer of transmit data.
1
Host provided new transmit data to SPIDAT1.
BITERR
Bit error. This is a read-to-clear only flag, that is, reading this bit automatically clears the bit. This
bit represents a copy of the BITERRFLG bit in the SPI flag register (SPIFLG). The SPI samples
the signal of the transmit pin (master: SIMO, slave: SOMI) at the receive point (half clock cycle
after transmit point). If the sampled value differs from the transmitted value, a bit error is detected
and the BITERRFLG bit is set and the BITERR bit is set. Possible reasons for a bit error are a
high bit rate/capacitive load or another master/slave trying to transmit at the same time. If the
BITERRENA bit in the SPI interrupt register (SPIINT) is set to 1 (enabled) and the BITERR bit is
set to 1, an interrupt is also generated.
0
Bit error did not occur.
1
Bit error did occur.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
27-18
Reserved
17-16
LCSNR
0-3h
Last chip select number. LCSNR in the status field is a copy of the CSNR bit in the corresponding
control field. It defines the chip select that has been activated during the last data transfer from the
corresponding buffer. LCSNR is copied after transmission during write back of received data.
15-0
SPIBUF
0-FFFFh
SPI receive buffer. This field makes up the SPI receive buffer. Data in this field is the data
received via the SPI_DI pin and transferred from the SPIDAT1 bits in the SPI shift register
(SPIDAT1). Since the data is shifted into the SPI with the most-significant bit first, for word lengths
less than 16, the data is stored right-justified in the register.
30
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.10 SPI Emulation Register (SPIEMU)
The SPI emulation register (SPIEMU) is shown in Figure 20 and described in Table 13.
Figure 20. SPI Emulation Register (SPIEMU)
31
16
Reserved
R-0
15
0
SPIEMU
R-x
LEGEND: R = Read only; -n = value after reset; -x = value is indeterminate after reset
Table 13. SPI Emulation Register (SPIEMU) Field Descriptions
Bit
Field
Value
Description
31-16
Reserved
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
15-0
SPIEMU
0-FFFFh
SPI emulation. SPI emulation is a mirror of the SPI buffer register (SPIBUF). The only difference
between SPIEMU and SPIBUF is that a read from SPIEMU does not clear the OVRNINTFLG and
RXINTFLAG bits in the SPI flag register (SPIFLG).
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
31
www.ti.com
Registers
3.11 SPI Delay Register (SPIDELAY)
The SPI delay register (SPIDELAY) is shown in Figure 21 and described in Table 14.
Figure 21. SPI Delay Register (SPIDELAY)
31
29
28
24
23
21
20
16
Reserved
C2TDELAY
Reserved
T2CDELAY
R-0
R/W-0
R-0
R/W-0
15
0
Reserved
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 14. SPI Delay Register (SPIDELAY) Field Descriptions
Bit
Field
31-29
Reserved
28-24
C2TDELAY
Value
Description
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
0-16h
Chip-select-active-to-transmit-start-delay. C2TDELAY defines a setup time for the slave device that
delays the data transmission from the chip select active edge by a multiple of SPI peripheral clock
cycles. C2TDELAY is configured between 2 and 22 SPI peripheral clock cycles.
SCS
CLK
SOMI
SYSCLK5
tC2TDELAY
The setup time value is calculated as:
t C2TDELAY +
C2TDELAY
)2
SPI peripheral clock
Example: SPI peripheral clock = 25 MHz and C2TDELAY = 06h; therefore, tC2TDELAY = 320 ns. When
the chip select signal becomes active, the slave has to prepare data transfer within 320 ns.
23-21
Reserved
20-16
T2CDELAY
0
0-16h
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Transmit-end-to-chip-select-inactive-delay. T2CDELAY defines a hold time for the slave device that
delays the chip select deactivation by a multiple of SPI peripheral clock cycles after the last bit is
transferred. T2CDELAY is configured between 1 and 22 SPI peripheral clock cycles.
SCS
CLK
SOMI
SYSCLK5
tT2CDELAY
The hold time value is calculated as:
t T2CDELAY +
T2CDELAY
)1
SPI peripheral clock
Example: SPI peripheral clock = 25 MHz and T2CDELAY = 02h; therefore, tT2CDELAY = 120 ns. After the
last data bit is being transferred, the chip select signal is held active for 120 ns.
15-0
32
Reserved
0
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
Serial Peripheral Interface (SPI)
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.12 SPI Default Chip Select Register (SPIDEF)
The SPI default chip select register (SPIDEF) is shown in Figure 22 and described in Table 15.
Figure 22. SPI Default Chip Select Register (SPIDEF)
31
16
Reserved
R-0
15
1
0
Reserved
2
EN1DEF
EN0DEF
R-0
R/W-1
R/W-1
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 15. SPI Default Chip Select Register (SPIDEF) Field Descriptions
Bit
Field
31-2
Reserved
1
EN1DEF
0
Value
0
Description
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Chip select default pattern. Selects the output to the slave 1 chip select pin (SPI_EN1) when no
transmission is currently in progress. EN1DEF allows you to set a chip select pattern that deselects all
the SPI slaves.
0
SPI_EN1 is driven to logic 0 when no transaction is in progress.
1
SPI_EN1 is driven to logic 1 when no transaction is in progress.
EN0DEF
Chip select default pattern. Selects the output to the slave 0 chip select pin (SPI_EN0) when no
transmission is currently in progress. EN0DEF allows you to set a chip select pattern that deselects all
the SPI slaves.
0
SPI_EN0 is driven to logic 0 when no transaction is in progress.
1
SPI_EN0 is driven to logic 1 when no transaction is in progress.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
33
www.ti.com
Registers
3.13 SPI Data Format Registers (SPIFMTn)
The SPI data format register (SPIFMT0, SPIFMT1, SPIFMT2, and SPIFMT3) is shown in Figure 23 and
described in Table 16.
Figure 23. SPI Data Format Register (SPIFMTn)
31
17
16
Reserved
21
SHIFTDIRn
Reserved
POLARITYn
PHASEn
R/W-0
R/W-0
R-0
R/W-0
R/W-0
15
8
7
20
5
19
18
4
0
PRESCALEn
Reserved
CHARLENn
R/W-0
R-0
R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 16. SPI Data Format Register (SPIFMTn) Field Descriptions
Bit
31-21
20
19-18
17
16
15-8
Field
Reserved
Value
0
SHIFTDIRn
Reserved
Reserved. The reserved bit location is always read as 0. This field must be written with zeroes.
Shift direction for data format n. SHIFTDIRn selects the shift direction for data format n (n = 1,2,3).
0
Most-significant bit is shifted out first.
1
Least-significant bit is shifted out first.
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
POLARITYn
Clock polarity for data format n. POLARITYn defines the clock polarity for data format n
(n = 1,2,3).
0
SPI clock signal is low-inactive, that is, before and after data transfer the clock signal is low.
1
SPI clock signal is high-inactive, that is, before and after data transfer the clock signal is high.
PHASEn
PRESCALEn
Description
Clock delay for data format n. PHASEn defines the clock delay for data format n (n = 1,2,3).
0
SPI clock signal is not delayed versus the transmit/receive data stream. The first data bit is
transmitted with the first clock edge and the first bit is received with the second (inverse) clock
edge.
1
SPI clock signal is delayed by a half SPI clock cycle versus the transmit/receive data stream. The
first transmit bit has to output prior to the first clock edge. Master and slave receive the first bit with
the first edge.
1-FFh
Prescaler for data format n. PRESCALEn defines the bit transfer rate for data format n (n = 1,2,3).
PRESCALEn is directly derived from SPI peripheral clock. The clock rate is calculated as:
SPI_CLK +
SPI periperal clock
(PRESCALEn ) 1)
PRESCALEn is only supported for values >1. For specific information on the maximum SPI clock
rate supported, refer to the SPI timings in the TMS320DM355 Digital Media Processor Data
Manual (literature number SPRS463).”
7-5
Reserved
4-0
CHARLENn
0
0-1Fh
0-1h
2h-10h
11h-1Fh
34
Serial Peripheral Interface (SPI)
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
Data word length for data format n. CHARLENn defines the word length for data format n
(n = 1,2,3). Legal values are 2h (data word length = 2 bits) to 10h (data word length = 16 bits).
Other values, such as 0 or 1Fh, are not detected and their effect is indeterminate.
Not detected and their effect is indeterminate.
Data word length is 2 bits to 16 bits.
Not detected and their effect is indeterminate.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
www.ti.com
Registers
3.14 SPI Interrupt Vector Register 0 (INTVECT0)
The SPI interrupt vector register 0 (INTVECT0) is shown in Figure 24 and described in Table 17.
Figure 24. SPI Interrupt Vector Register 0 (INTVECT0)
31
16
Reserved
R-0
15
6
5
1
0
Reserved
INTVECT0
Rsvd
R-0
R-0
R-0
LEGEND: R = Read only; -n = value after reset
Table 17. SPI Interrupt Vector Register 0 (INTVECT0) Field Descriptions
Bit
Field
Value
Description
31-6
Reserved
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
5-1
INTVECT0
0-1Fh
Interrupt vector for interrupt line INT0. INTVECT0 returns the vector of the pending interrupt at
interrupt line INT0. If more than one interrupt is pending, INTVECT0 always references the highest
prior interrupt source first.
The interrupts available for SPI, in the descending order of their priorities:
• Receive overrun interrupt
• Receive interrupt
• Transmission error interrupt
Vectors for each of these interrupts is reflected in the INTVECT0 bit, when they occur. Reading
the vectors for the receive overrun interrupt and receive interrupt automatically clears the
respective flags in the SPI flag register (SPIFLG). On reading the INTVECT0 bit, the vector of the
next highest priority interrupt (if any) is then reflected in the INTVECT0 bit. If two or more interrupts
occur simultaneously, the vector for the highest priority interrupt is reflected in the INTVECT0 bits.
0
1h-10h
Reserved
Reserved
11h
Error interrupt is pending. Refer to lower halfword of the SPI interrupt register (SPIINT) to
determine more details about the type of error and the concerned buffer.
12h
Receive interrupt is pending.
13h
Receive overrun interrupt is pending.
14h-1Fh
0
No interrupt is pending.
0
Reserved
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
Serial Peripheral Interface (SPI)
35
www.ti.com
Registers
3.15 SPI Interrupt Vector Register 1 (INTVECT1)
The SPI interrupt vector register 1 (INTVECT1) is shown in Figure 25 and described in Table 18.
Figure 25. SPI Interrupt Vector Register 1 (INTVECT1)
31
16
Reserved
R-0
15
6
5
1
0
Reserved
INTVECT1
Rsvd
R-0
R-0
R-0
LEGEND: R = Read only; -n = value after reset
Table 18. SPI Interrupt Vector Register 1 (INTVECT1) Field Descriptions
Bit
Field
Value
Description
31-6
Reserved
0
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
5-1
INTVECT1
0-1Fh
Interrupt vector for interrupt line INT1. INTVECT1 returns the vector of the pending interrupt at
interrupt line INT1. If more than one interrupt is pending, INTVECT1 always references the highest
prior interrupt source first.
The interrupts available for SPI, in the descending order of their priorities:
• Receive overrun interrupt
• Receive interrupt
• Transmission error interrupt
Vectors for each of these interrupts is reflected in the INTVECT1 bit, when they occur. Reading
the vectors for the receive overrun interrupt and receive interrupt automatically clears the
respective flags in the SPI flag register (SPIFLG). On reading the INTVECT1 bit, the vector of the
next highest priority interrupt (if any) is then reflected in the INTVECT1 bit. If two or more interrupts
occur simultaneously, the vector for the highest priority interrupt is reflected in the INTVECT1 bits.
0
1h-10h
36
Reserved
Reserved
11h
Error interrupt is pending. Refer to lower halfword of the SPI interrupt register (SPIINT) to
determine more details about the type of error and the concerned buffer.
12h
Receive interrupt is pending.
13h
Receive overrun interrupt is pending.
14h-1Fh
0
No interrupt is pending.
0
Serial Peripheral Interface (SPI)
Reserved
Reserved. The reserved bit location is always read as 0. A value written to this field has no effect.
SPRUED4B – May 2006 – Revised October 2007
Submit Documentation Feedback
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements,
improvements, and other changes to its products and services at any time and to discontinue any product or service without notice.
Customers should obtain the latest relevant information before placing orders and should verify that such information is current and
complete. All products are sold subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment.
TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TI’s
standard warranty. Testing and other quality control techniques are used to the extent TI deems necessary to support this
warranty. Except where mandated by government requirements, testing of all parameters of each product is not necessarily
performed.
TI assumes no liability for applications assistance or customer product design. Customers are responsible for their products and
applications using TI components. To minimize the risks associated with customer products and applications, customers should
provide adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right, copyright, mask
work right, or other TI intellectual property right relating to any combination, machine, or process in which TI products or services
are used. Information published by TI regarding third-party products or services does not constitute a license from TI to use such
products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under
the patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is
accompanied by all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an
unfair and deceptive business practice. TI is not responsible or liable for such altered documentation. Information of third parties
may be subject to additional restrictions.
Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service
voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business
practice. TI is not responsible or liable for any such statements.
TI products are not authorized for use in safety-critical applications (such as life support) where a failure of the TI product would
reasonably be expected to cause severe personal injury or death, unless officers of the parties have executed an agreement
specifically governing such use. Buyers represent that they have all necessary expertise in the safety and regulatory ramifications
of their applications, and acknowledge and agree that they are solely responsible for all legal, regulatory and safety-related
requirements concerning their products and any use of TI products in such safety-critical applications, notwithstanding any
applications-related information or support that may be provided by TI. Further, Buyers must fully indemnify TI and its
representatives against any damages arising out of the use of TI products in such safety-critical applications.
TI products are neither designed nor intended for use in military/aerospace applications or environments unless the TI products are
specifically designated by TI as military-grade or "enhanced plastic." Only products designated by TI as military-grade meet military
specifications. Buyers acknowledge and agree that any such use of TI products which TI has not designated as military-grade is
solely at the Buyer's risk, and that they are solely responsible for compliance with all legal and regulatory requirements in
connection with such use.
TI products are neither designed nor intended for use in automotive applications or environments unless the specific TI products
are designated by TI as compliant with ISO/TS 16949 requirements. Buyers acknowledge and agree that, if they use any
non-designated products in automotive applications, TI will not be responsible for any failure to meet such requirements.
Following are URLs where you can obtain information on other Texas Instruments products and application solutions:
Products
Applications
Amplifiers
amplifier.ti.com
Audio
www.ti.com/audio
Data Converters
dataconverter.ti.com
Automotive
www.ti.com/automotive
DSP
dsp.ti.com
Broadband
www.ti.com/broadband
Interface
interface.ti.com
Digital Control
www.ti.com/digitalcontrol
Logic
logic.ti.com
Military
www.ti.com/military
Power Mgmt
power.ti.com
Optical Networking
www.ti.com/opticalnetwork
Microcontrollers
microcontroller.ti.com
Security
www.ti.com/security
RFID
www.ti-rfid.com
Telephony
www.ti.com/telephony
Low Power
Wireless
www.ti.com/lpw
Video & Imaging
www.ti.com/video
Wireless
www.ti.com/wireless
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2007, Texas Instruments Incorporated
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Related manuals

Download PDF

advertising