8-/16-bit
– Serial NOR Flash controller
– Parallel NAND Flash controller, 8-/16-bit
data bus
– Parallel NOR Flash/FPGA interface,
8-/16-bit data bus
■ Connectivity:
– 2 x USB 2.0 Host ports (integrated PHY)
– 1 x USB 2.0 Device port (integrated PHY)
– 2 x Fast Ethernet ports (external MII/RMII
PHY)
– 1 x MMC-SD card/SDIO controller
– 2 x CAN 2.0 ports
–7 x UART ports
– 3 x I2C ports: master/slave
– 3 x synchronous serial ports,
SPI/Microwire/TI protocols, master/slave
– 1 x RS485 interface
– 1 x fast IrDA interface
– 1 x legacy parallel port (IEEE 1284), slave
mode
– 10-bit ADC, 8 channels, 1 Msps
– Up to 102 GPIOs with interrupt capability
■ HMI support:
– LCD display controller, up to XGA
(1024 x 768, 24 bpp)
– Resistive touchscreen interface
– JPEG codec accelerator
– 1 x I2S digital audio port
■ Security
– Cryptographic co-processor
SPEAr320S
Embedded MPU with ARM926 core
Datasheet − production data
■ Miscellaneous functions:
– System controller, vectored interrupt
controller, watchdog, real-time clock
– Dynamic power-saving features
– 8-channel DMA controller
– 6 x 16-bit general purpose timers with
prescaler and 4 capture inputs
– 4 x PWM generators
– Debug and trace interfaces: JTAG/ETM
Applications
The SPEAr320S embedded MPU is configurable
for a range of industrial and consumer
applications such as:
■ Human machine interface (HMI) terminals
■ Factory automation / PLCs
■ Medical equipment
■ Smart energy meters and gateways
■ VoIP phones
■ Small printers
The device is hardware-compliant to the support
of both real-time (RTOS) and high-level (HLOS)
operating systems, such as Linux and Windows
Embedded Compact 7.
Table 1.Device summary
Order code
SPEAR320S-2-40 to 85
Temp
range, ° C
PackagePacking
LFBGA289
(15x15 mm,
pitch 0.8 mm)
Tr ay
April 2012Doc ID 022508 Rev 11/97
This is information on a product in full production.
SPEAr320S is a member of the SPEAr family of embedded MPUs and is optimized for
industrial automation and consumer markets. The device is based on the ARM926EJ-S
processor (up to 333 MHz), widely used in applications where the processing performance
is required to be higher than the one achievable with microcontrollers.
SPEAr320S provides an integrated MMU (memory management unit) which enables to
support high-level operating systems (HLLs), such as Linux and Windows Embedded
Compact
HMI, cryptography) allows the device to be used in a wide range of embedded applications.
The SPEAr320S architecture is based on multiple functional blocks interacting through a
multilayer interconnection bus matrix. The switch matrix structure allows different subsystem
data flows to be executed in parallel improving the core platform efficiency. High
performance master agents are directly interconnected with the memory controller reducing
the memory access latency. The overall memory bandwidth assigned to each master port
can be programmed and optimized through an internal efficient weighted round-robin
arbitration mechanism.
The SPEAr320S device is fully backward-compatible with the previous SPEAr320 product at
both hardware and software programming levels. The extended functionality is achieved by
enhanced I/O multiplexing, preserving the same pinout and ball map, as well as by a new
software-definable configuration mode.
7. In addition, a rich set of integrated peripherals (memory interfaces, connectivity,
Doc ID 022508 Rev 19/97
Page 10
DescriptionSPEAr320S
MMU
ETMI/F
ARM9EJSCore
16KB
ICache
16KB
DCache
CPU
Subsystem
DisplayCtrl
JPEGCodec
I2SAudioI/F
USB2.0Host(2x)
USB2.0Device
HMIfeatures
Highspeedconnectivity
BUSMATRIXInterconnect
GPIO
XGPIO
SSP (3x)
FastIrDA
SPP
ADC
Lowspeedconnectivity
StaticMemoryCtrl
SerialFlashI/F
ExternalMemory
I/F
Memoryinterfaces
32KB
BootROM
DDR2/LPDDR
Ctrl
DMACtrl
Cryptographic
Coprocessor
Reset&clock
Generator
System
Controller
Config Regs
(MISC)
Timers(6x)
JTAGTrace
Opt.
Battery
CAN(2x)
PWM(4x)
RS485
FastEthernet
(2x)
I2C (3x)
UART (7x)
BusInterfaces
VectoredInterrupt
Controller
DebugI/F
4KB
StaticRAM
Watchdog
SDIO/MMC
Touchscreen I/F
RTC
Figure 1.SPEAr320S architectural block diagram
10/97Doc ID 022508 Rev 1
Page 11
SPEAr320SDevice functions
2 Device functions
2.1 CPU subsystem
The core of the SPEAr320S is an ARM926EJ-S reduced instruction set computer (RISC)
processor.
Main features:
●Supports the 32-bit ARM and 16-bit Thumb instruction sets, enabling the user to trade
off between high performance and high code density. It also includes features for
efficient execution of Java byte codes.
●The ARM CPU can be clocked at a frequency up to 333 MHz and includes both an
instruction (16 KB) and a data cache (16 KB). In addition to the capability of running
any real-time operating system (RTOS) available for ARM9 processors, the
ARM926EJ-S subsystem also provides a memory management unit (MMU) that
enables to support high-level operating systems (HLLs) like Linux and Windows
Embedded Compact 7.
●Includes an embedded trace module (ETM Medium+) for real-time CPU activity tracing
and debugging. It supports 4-bit and 8-bit normal trace mode and 4-bit demultiplexed
trace mode, with normal or half-rate clock.
For detailed information, please refer to the following public documents available from the
●32 KB ROM (BootROM), storing a factory-defined device bootstrap firmware.
●8 KB Static RAM (SRAM), partly used by bootstrap firmware, but also available as
general-purpose memory after system startup.
The firmware in BootROM is automatically executed after SPEAr320S reset and supports
the following bootstrap modes:
●Boot from serial NOR Flash
●Boot from parallel NAND Flash
●Boot from parallel NOR Flash
●Boot from USB Device port
The BootROM firmware selects the boot mode from the boot pin settings (see Section 3.4.4:
Boot pins). A setting is also available to allow the BootROM execution to be bypassed.
Doc ID 022508 Rev 111/97
Page 12
Device functionsSPEAr320S
The first three modes support alternate ways of locating and starting the selected operating
system or target custom software. Such modes require a second-level boot firmware to be
stored in external Flash memory. A reference code for such boot loader (called “XLoader”) is
provided by STMicroelectronics in source and binary formats for the SPEAr320S evaluation
boards. Such code must be adapted according to the specific DDR memory components
found on target customer systems.
The fourth mode can be used for installing and updating the software on external Flash
memories through a PC-based software utility provided by STMicroelectronics exploiting a
USB link between a PC and a target SPEAr320S board.
2.3 Multiport DDR controller (MPMC)
SPEAr320S integrates a high-performance controller able to manage DDR2 (double data
rate) and LPDDR (low power DDR) external dynamic memory devices.
Main features:
●Support for DDR2 up to 333 MHz (666 MT/sec)
●Support for LPDDR up to 166 MHz (333 MT/sec)
●Support for 8-/16-bit external data bus
●Support for up to 1 GByte DDR2/LPDDR memory address space
●Full initialization of memories on controller reset
●6 independent internal ports: five of them are used to access the external memory
while one is reserved for programming the controller configuration registers
●Programmable built-in port arbitration scheme to ensure high memory bandwidth
utilization
●Fully pipelined read and write commands
●Self-refresh mode for power saving
●Integrated physical layer (PHY) and delay locked loops (DLLs) for fine tuning of the
timing parameters, maximizing the data valid windows at different frequencies
2.4 Serial NOR Flash controller (SMI)
SPEAr320S integrates a Flash memory controller able to manage serial, SPI-compatible,
NOR Flash and EEPROM external memory devices.
Main features:
●Support for up to 32 MByte external serial memory storage capacity (2 x 16 MB
addressable banks by independent chip select signals)
●SMI clock up to 50 MHz (fast read mode) or 20 MHz (normal mode), with software
configurable 7-bit prescaler
The bootstrap requires that the external serial Flash is located at bank 0 (enabled after
power-on reset). During the boot phase, a sequence of instructions is automatically sent to
bank 0. Refer to SPEAr320S reference manuals for more details.
12/97Doc ID 022508 Rev 1
Page 13
SPEAr320SDevice functions
The BootROM firmware has been tested with the following external serial memory
components:
●Micron M25P and M45P families (SPI Flash)
●Micron M95 family (SPI EEPROM), except for M95040, M95020 and M95010
●ATMEL AT25F family (SPI Flash)
●YMC Y25F family (SPI Flash)
●Microchip/SST SST25LF family (SPI Flash)
2.5 Parallel NAND Flash controller (FSMC)
SPEAr320S integrates a flexible static memory controller able to manage external parallel
NAND Flash memories.
Main features:
●8-/16-bit external data bus; 16-bit only supported when Mode 3 (expanded automation
mode) chip configuration is selected by software.
●Support for up to 4 memory banks
●Independent timing configuration and chip select signal for each memory bank
●Fully programmable timings:
–wait states (up to 31)
–bus turnaround cycles (up to 15)
–output enable and write enable delays (up to 15)
●External asynchronous wait control
●Internal AHB bus burst transfer support to reduce Flash memory access time
The BootROM firmware directly supports the external NAND Flash components shown in
Ta bl e 2.
Table 2.NAND Flash devices supported by the BootROM firmware
Part numberVendorDensityCapacity
K9F1208V0ASamsung64 Mb8 MBx8512 + 16 bytes
NAND128W3A28N6Micron128 Mb16 MBx8512 + 16 bytes
NAND256W3A2BN6Micron256 Mb32 MBx8512 + 16 bytes
KM29U256Samsung256 Mb32 MBx8512 + 16 bytes
NAND512W3A2C2A6Micron512 Mb64 MBx8512 + 16 bytes
NAND01GW3B2BN6Micron1 Gb128 MBx82048 + 64 bytes
NAND01GW4B2AN6Micron1 Gb128 MBx161024 words + 32 bytes
K9F1G16U0MSamsung1 Gb128 MBx161024 words + 32 bytes
NAND01GR3BMicron1 Gb128 MBx82048 + 64 bytes
NAND02GW3B2CN6Micron2 Gb256 MBx82048 + 64 bytes
NAND02GW3AMicron2 Gb256 MBx82048 + 64 bytes
Bus
width
Page size
Doc ID 022508 Rev 113/97
Page 14
Device functionsSPEAr320S
Table 2.NAND Flash devices supported by the BootROM firmware (continued)
Part numberVendorDensityCapacity
K9F2G08V0ASamsung2 Gb256 MBx8512 + 16 bytes
NAND04GW3B2BN6Micron4 Gb512 MBx82048 + 64 bytes
K9F4G08V0ASamsung4 Gb512 MBx8512 + 16 bytes
NAND08GW3B2CN6Micron8 Gb1 GBx82048 + 64 bytes
K9K8G08V0ASamsung8 Gb1 GBx8512 + 16 bytes
K9F8G08V0MSamsung8 Gb1 GBx8512 + 16 bytes
2.6 External memory interface (EMI)
SPEAr320S integrates an additional external memory interface that can be used to manage
external parallel NOR Flash memories as well as FPGA devices. This interface is available
only when Mode 3 (expanded automation mode) chip configuration is selected by software.
Main features:
●24-bit address bus
●16-bit data bus
●4 chip select signals
●Support for single asynchronous transfers
●Support for peripherals using Byte Lane procedure
Bus
width
Page size
The external Flash component must be in read mode at reset. Usually, this is true for most
parallel NOR devices.
2.7 USB 2.0 Host ports (UHC)
SPEAr320S provides two USB 2.0 Host ports with integrated PHYs.
Main features:
●Each port can be independently configured for high-speed mode (USB 2.0, up to
480 Mbps); in this case, the corresponding controller is programmed according to
standard EHCI specifications.
●Each port can be independently configured for full-speed mode (USB 1.1, up to
12 Mbps) or low-speed mode (USB 1.1, up to 1.5 Mbps); in this case, the
corresponding controller is programmed according to standard OHCI specifications.
●Internal 2 KB FIFO queues
●Internal DMA support
●Dedicated output control signals to manage external power switches
●Dedicated input signals to sense any over-current condition detected by external power
switches
14/97Doc ID 022508 Rev 1
Page 15
SPEAr320SDevice functions
2.8 USB 2.0 Device port (UDC)
SPEAr320S provides a USB 2.0 Device port with integrated PHY.
Main features:
●Support for all standard modes:
–high-speed mode (USB 2.0, up to 480 Mbps)
–full-speed mode (USB 1.1, up to 12 Mbps)
–low-speed mode (USB 1.1, up to 1.5 Mbps)
●Up to 16 physical endpoints, configurable as different logical endpoints
●Internal 4 KB FIFO queue (shared among all the endpoints)
●DMA mode, with descriptor-based structures in application memory
●Slave-only mode
●Support for 8-, 16- and 32-bit wide data transactions on the internal bus
●Support for USB plug detection (UPD)
2.9 Fast Ethernet ports (MII/RMII)
SPEAr320S features three multiplexed Ethernet MACs, supporting up to two ports
concurrently.
The three controllers are named:
●MII0
●RMII0
●MII1/RMII1
2.9.1 MII0 Ethernet controller
Main features:
●Media independent interface (MII) to an external PHY as defined in the IEEE 802.3u
specification
●Support for 10 and 100 Mbps data transfer rates
●Support for both full-duplex and half-duplex (CSMA/CD protocol) operating modes
●Integrated FIFO queues (4 KB RX, 2 KB TX)
●Native DMA with single-channel transmit and receive engines, providing 32-/64-/128-bit
data transfers; DMA provides ring-buffer or linked-list descriptor options.
●Programmable Ethernet frame length to support both standard and jumbo frames (with
size up to 16 KB)
●Flexible address filtering modes
●Statistics counter registers for RMON/MIB
●Support for 802.1Q VLAN tagging
●Wake-on-LAN support
●Automatic padding and CRC generation on transmitted frames
Doc ID 022508 Rev 115/97
Page 16
Device functionsSPEAr320S
2.9.2 RMII0 and MII1/RMII1 Ethernet controllers
These functional blocks extend Ethernet capability by covering the Media independent
interface (MII) and Reduced media independent interface (RMII) standards.
They can be used in two ways:
●as a single additional MAC controller with Media independent interface (MII1)
●as two MAC controllers with Reduced media independent interface (RMII0, RMII1)
In RMII configuration, each controller has an independent set of data and control lines. The
reference clock (50
Main features:
●Compatible with IEEE Standard 802.3
●UNH tested
●10 and 100 Mbit/s operation
●Full and half duplex operation
●Statistics counter registers for RMON/MIB
●Automatic pad and CRC generation on transmitted frames
●Automatic discard of frames received with errors
●Address checking logic supports up to four specific 48-bit addresses
●Supports promiscuous mode where all valid received frames are copied to memory
●Hash matching of unicast and multicast destination addresses
●External address matching of received frames
●Supports serial network interface operation
●Half-duplex flow control by forcing collisions on incoming frames
●Full-duplex flow control with recognition of incoming pause frames and hardware
generation of transmitted pause frames
●Support for 802.1Q VLAN tagging with recognition of incoming VLAN and priority
tagged frames
●Multiple buffers per receive and transmit frame
●Jumbo frames of up to 10240 bytes supported
MHz) is shared by the controllers.
2.10 MMC-SD card/SDIO controller
The MMC-SD card /SDIO controller conforms to the SD Host Controller Standard
Specification, version 2.0. It handles SD/SDIO protocol at transmission level by packing
data, adding cyclic redundancy check (CRC) and start/end bit as well as checking for
transaction format correctness.
The controller is designed to work with I/O cards, read-only cards and read/write cards, and
can operate either in SD mode (1-bit, 4-bit, 8-bit) or in SPI mode.
16/97Doc ID 022508 Rev 1
Page 17
SPEAr320SDevice functions
The interface is compliant to the following standards:
●SD Host Controller Standard Specification, version 2.0
●SDIO Card Specification, version 2.0
●SD Memory Card Specification Draft, version 2.0
●SD Memory Card Security Specification, version 1.01
●MMC Specification, version 3.31 and 4.2
Main features:
●Up to 100 Mbps data rate using 4 parallel data lines (SD4 bit mode)
●Up to 416 Mbps data rate using 8-bit parallel data lines (SD8 bit mode)
●DMA-based and non-DMA modes of operation
●Support for MMC Plus and MMC Mobile
●Card detection (insertion / removal)
●Card password protection
●Host clock rate variable between 0 and 48 MHz
●Multimedia card interrupt mode
●Cyclic redundancy check: CRC7 (command) and CRC16 (data integrity)
●Error correction code (ECC) support for MMC4.2 cards
●Supports for Read Wait Control and Suspend/Resume
●FIFO overrun and under-run handling by stopping SD clock
2.11 CAN 2.0 ports
SPEAr320S provides two independent CAN (controller area network) bus ports, typically
used in automotive, industrial and medical applications. For the connection to the physical
layer, an additional transceiver per port is required.
For communication on a CAN network, the controller enables to configure individual
message objects. The message objects and identifier masks for acceptance filtering of
received messages are stored in an integrated message RAM. All functions concerning the
handling of messages are implemented by a message handler. Those functions are the
acceptance filtering, the transfer of messages between the CAN core and the message
RAM, the handling of transmission requests as well as the generation of interrupts.
Main features:
●Support for CAN protocol, version 2.0 part A and B
●Transfer rate up to 1 Mbps
●Internal RAM storage for up to 16 message objects (16 x 136 bytes memory)
●Identifier mask per message object
●Maskable interrupts
●Programmable loop-back mode for self-test operation
●Disabled automatic retransmission mode for time triggered CAN applications
Doc ID 022508 Rev 117/97
Page 18
Device functionsSPEAr320S
2.12 Asynchronous serial ports (UART)
The SPEAr320S has 7 UART ports. The actual number of concurrently exploitable ports
depends on the selected chip operating mode. The different capabilities of each port are
summarized in
Table 3.SPEAr320S UART capabilities
PortSpeedHardware flow controlModem signals
UART0Up to 3 MbpsYesYes (as alternate function)
UART1Up to 7 MbpsYes (except for Mode 1 and 2) Yes (except for Mode 1 and 2)
●Automatic generation of preamble, start and stop flags
●RZI (return-to-zero inverted) modulation/demodulation scheme for SIR and MIR modes
●4PPM (4-pulse position modulation) modulation/demodulation scheme for FIR mode
●Synchronization by DPLL in FIR mode
●Payload data transfer controllable by either CPU or DMA controller
●Two clock domains:
–Dedicated clock (IRDA_CLK signal) for accurate signal generation (48 MHz)
–Independent and variable clock for the bus interface (13 MHz)
2.17 Legacy IEEE 1284 parallel port (SPP)
SPEAr320S provides a parallel port (slave mode only) compliant to the legacy IEEE 1284
standard.
Main features:
●Unidirectional 8-bit data transfer from SPEAr320S slave to external host
●Additional 9th bit for parity/data/command
●Maskable interrupts for data, device reset, auto line feed
20/97Doc ID 022508 Rev 1
Page 21
SPEAr320SDevice functions
2.18 A/D converter (ADC)
SPEAr320S provides an integrated analog-to-digital converter.
Main features:
●Successive approximation conversion method
●8 x analog input channels, ranging from 0 to 2.5 V
●10-bit resolution
●Sampling rate up to 1 Msamples/s
●Support for 13.5-bit resolution at 8 Ksamples/s by oversampling and accumulation
●INL ± 1 LSB, DNL ± 1 LSB
●Programmable conversion speed (minimum conversion time is 1 µs)
●Programmable averaging of multiple values from 1 (no averaging) up to 128
●Programmable auto scan for all the 8 channels
2.19 General purpose I/Os (GPIO/XGPIO)
Up to 102 GPIOs are available in SPEAr320S when some embedded IPs are not needed in
the customer application (see
Section 3.4: Shared IO pins (PL_GPIOs)).
SPEAr320S provides two mechanisms:
●a basic GPIO module (called “basGPIO”): this functional block provides 6 pins, each
one programmable by software with the following features:
–direction: input (default at reset) or output
–interrupt triggering mode
●the possibility to configure and use any PL_GPIO pin as alternative to the
corresponding predefined signal purpose (called extended GPIO or “XGPIO”). XGPIOs
have the same capability of basic GPIOs, while the register programming model is
different.
Doc ID 022508 Rev 121/97
Page 22
Device functionsSPEAr320S
2.20 LCD display controller (CLCD)
SPEAr320S has an integrated display controller able to directly interface a variety of color
and monochrome LCD panels.
Main features:
●Programmable resolution up to 1024 x 768 (XGA)
●Programmable timing parameters
●Support for TFT (thin film transistor) color displays
●Supports for STN (super twisted nematic) displays (single and dual panel) with 4- or 8-
bit interfaces
●AC bias signal for STN and data enable signal for TFT panels
●Gray scaling algorithm
The set of supported pixel widths and formats for each display type is shown in Ta b le 4.
Table 4.Pixel widths and formats available for different display types
Display1 bpp 2 bpp 4 bpp 8 bpp 16 bpp 24 bpp
Palette of 16
colors over
64K
Palette of 16
colors over
3375
Palette of 16
gray levels over
15
Color TFT
Color STN
Mono STN
Palette of 2
colors over 64K
Palette of 2
colors over 3375
Palette of 2 gray
levels over 15
Palette of 4
colors over 64K
Palette of 4
colors over 3375
Palette of 4 gray
levels over 15
2.21 Touchscreen interface (OUT_X)
SPEAr320S provides a toggling output signal (OUT_X) that can be connected to an external
touchscreen panel. This interface operates in combination with the A/D converter (ADC).
Two coordinates can be read by software from the ADC: one at the end of the high period
and one at the end of the low period of OUT_X signal.
Palette of
256 colors
over 64K
Palette of
256 colors
over 3375
Palette of
256 colors
over 3375
RGB 5:5:5 +
intensity
(64K colors)
RGB 4:4:4
(4096 colors)
--
RGB 8:8:8
(16M colors)
-
22/97Doc ID 022508 Rev 1
Page 23
SPEAr320SDevice functions
2.22 JPEG codec accelerator (JPGC)
SPEAr320S provides an integrated hardware accelerator for decoding and encoding
standard JPEG images.
JPEG data streams to be decoded must be compliant with the interchange format syntax
specified in the ISO/IEC 10918-1. The JFIF image file format is also supported through
header processing.
The output format for decoding (and input format for encoding) is a MCU stream, not a
conventional bitmap format like RGB. Displaying a decoded JPEG still picture would require
further steps and algorithms like color space conversion and scaling.
Main features:
●Compliance with the baseline JPEG standard (ISO/IEC 10918-1)
●Single-clock per pixel encoding/decoding
●Support for up to four channels of component color
●8-bit/channel pixel depths
●Programmable quantization tables (up to four)
●Programmable Huffman tables (two AC and two DC)
●Programmable minimum coded unit (MCU)
●Configurable JPEG header processing
●Support for restart marker insertion
●Use of two DMA channels and two 8 x 32-bit FIFOs (local to the JPEG) for efficient
transferring and buffering of encoded/decoded data from/to the Codec core.
2.23 Digital audio port (I2S)
The SPEAr320S integrates a digital audio port compliant to standard I2S (Philips)
specifications.
Main features:
●I2S master mode
●Stereo (2.0) playback and recording
●Support for standard sampling rates (8, 16, 32, 44.1, 48, 96, 192 kHz); the clock input is
24 MHz, so the rate precision depends on the chosen rate and divider.
●Support of a range of audio samples: 12 / 16 / 20 / 24/ 32 bits
●Programmable thresholds for internal FIFO queues
●Capability of using DMA transfer
2.24 Cryptographic co-processor (C3)
SPEAr320S provides an embedded cryptographic co-processor (C3). C3 is a high-
performance instruction-driven DMA-based engine that can be used to accelerate the
processing of security algorithms.
After its initial configuration by the main CPU, it runs in a completely autonomous way (DMA
data in, data processing, DMA data out), until the completion of all the requested operations.
C3 firmware is fetched from system memory.
Doc ID 022508 Rev 123/97
Page 24
Device functionsSPEAr320S
Main features:
●Supported cryptographic algorithms:
–Advanced encryption standard (AES) cipher in ECB, CBC, CTR modes
–Data encryption standard (DES) cipher in ECB and CBC modes
–SHA-1, HMAC-SHA-1, MD5, HMAC-MD5 digests
●Hardware chaining of cryptographic stages for optimized data flow when multiple
algorithms are required to process the same set of data (for example, encryption and
hashing on the fly)
2.25 System controller (SYSCTR)
The system controller provides an interface for controlling the operation of the overall
system.
Main features:
●Power saving system mode control
●Crystal oscillator and PLL control
●Configuration of system response to interrupts
●Reset status capture and soft reset generation
●Watchdog and timer module clock enable
Using three mode control bits, the system controller switches the SPEAr320S to any of the
four different modes: DOZE, SLEEP, SLOW and NORMAL.
●SLEEP mode: in this mode, the system clocks, HCLK and CLK, are disabled and the
system controller clock, SCLK, is driven by a low-speed oscillator (nominally
32768 Hz). When either a FIQ or an IRQ interrupt is generated (through the VIC), the
system enters DOZE mode. Additionally, the operating mode setting in the system
control register automatically changes from SLEEP to DOZE.
●DOZE mode: in this mode, the system clocks, HCLK and CLK, and the system
controller clock are driven by a low-speed oscillator. The system controller moves into
SLEEP mode from DOZE mode only when none of the mode control bits are set and
the processor is in wait-for-interrupt state. If SLOW mode or NORMAL mode is
required, the system moves into the XTAL control transition state to initialize the crystal
oscillator.
●SLOW mode: during this mode, both the system clocks and the system controller clock
are driven by the crystal oscillator. If NORMAL mode is selected, the system goes into
the “PLL control” transition state. If neither the SLOW nor the NORMAL mode control
bits are set, the system goes into the “Switch from XTAL” transition state.
●NORMAL mode: in NORMAL mode, both the system clocks and the system controller
clock are driven by the PLL output. If the NORMAL mode control bit is not set, then the
system goes into the “Switch from PLL” transition state.
24/97Doc ID 022508 Rev 1
Page 25
SPEAr320SDevice functions
2.25.1 Reset and clock generator
The reset and clock generator is a fully programmable block that generates all the clocks
necessary to the chip.
The default operating clock frequencies are:
●Clock @ 333 MHz for the CPU.
●Clock @ 166 MHz for AHB bus and AHB peripherals.
●Clock @ 83 MHz for, APB bus and APB peripherals.
●Clock @ 333 MHz for DDR memory interface.
The default values give the maximum allowed clock frequencies. The clock frequencies are
fully programmable through dedicated registers.
The reset and clock generator consists of 2 main parts:
●a multiclock generator block
●two internal PLLs
The multiclock generator block receives a reference signal (which is usually delivered by the
PLL) and generates all clocks for SPEAr320S IPs according to dedicated programmable
registers.
Each PLL uses an oscillator input of 24 MHz to generate a clock signal at a frequency
corresponding at the highest of the group. This is the reference signal used by the multiclock
generator block to obtain all the other requested clocks for the group. Its main feature is the
You can set up the PLL in order to modulate the VCO with a triangular wave. The resulting
signal has a spectrum (and power) spread over a small programmable range of frequencies
centered on F0 (the VCO frequency), obtaining minimum electromagnetic emissions. This
method replaces all the other traditional methods of EMI reduction, such as filtering, ferrite
beads, chokes, adding power layers and ground planes to PCBs, metal shielding and so on.
This offers important cost savings.
In sleep mode, SPEAr320S runs with the PLL disabled, so the available frequency is
24
MHz or a sub-multiple (/2, /4, /8).
2.26 Vectored interrupt controller (VIC)
SPEAr320S integrates a vectored interrupt controller which provides a software interface to
the interrupt system. In any system with an interrupt controller, the software has to
determine the source that requests service and where its service routine is loaded. The VIC
inside SPEAr320S does both of these in hardware. It supplies the starting address, or vector
address, of the service routine corresponding to the highest priority requesting interrupt
source.
As in any ARM9-based system, two levels of interrupts are available:
●fast interrupt requests (FIQ), for fast, low latency interrupt handling
●normal interrupt requests (IRQ), for more general interrupts
The interrupt inputs must be level sensitive, active HIGH, and held asserted until the
interrupt service routine clears the interrupt. Edge-triggered interrupts are not compatible.
The interrupt inputs do not have to be synchronous to HCLK. The VIC does not handle
interrupt sources with transient behavior. For example, an interrupt is asserted and then de-
Doc ID 022508 Rev 125/97
Page 26
Device functionsSPEAr320S
asserted before software can clear the interrupt source. In this case, the CPU acknowledges
the interrupt and obtains the vectored address for the interrupt from the VIC, assuming that
no other interrupt has occurred to overwrite the vectored address. However, when a
transient interrupt occurs, the priority logic of the VIC is not set, and lower priority interrupts
can interrupt the transient interrupt service routine, assuming interrupt nesting is permitted.
There are 32 interrupt lines. The VIC uses a bit position for each different interrupt source.
The software can control each request line to generate software interrupts. There are 16
vectored interrupts. These interrupts can only generate an IRQ interrupt. The vectored and
non-vectored IRQ interrupts provide an address for an interrupt service routine (ISR). The
FIQ interrupt has the highest priority, followed by interrupt vector 0 to interrupt vector 15.
Non-vectored IRQ interrupts have the lowest priority.
The specific interrupt map for the SPEAr320S device is documented in the companion
reference manuals.
2.27 Watchdog timer (WDT)
The ARM watchdog module consists of a 32-bit down counter with a programmable time-out
interval that has the capability to generate an interrupt and a reset signal on timing out. The
watchdog module is intended to be used to apply a reset to a system in the event of a
software failure.
2.28 Real-time clock (RTC)
The real-time clock provides an 1-second resolution clock. This keeps time when the system
is inactive and can be used to wake the system up when a programmed alarm time is
reached. RTC has a clock trimming feature to compensate for the accuracy of the 32.768
kHz crystal and a secured time update.
Main features:
●Time-of-day clock in 24 hour mode
●Calendar
●Alarm capability
●Isolation mode, allowing RTC to work even if power is not supplied to the rest of the
device.
2.29 DMA controller (DMAC)
SPEAr320S provides one DMA controller.
Main features:
●Able to service up to 8 independent DMA channels for serial data transfers between
single source and destination (for instance, memory-to-memory, memory-to-peripheral,
peripheral to- memory, and peripheral-to-peripheral).
●Each DMA channel can support a unidirectional transfer, with internal four-word FIFO
per channel.
26/97Doc ID 022508 Rev 1
Page 27
SPEAr320SDevice functions
2.30 General purpose timers (GPT)
SPEAr320S provides 6 general purpose timers.
Main features:
●Each timer provides a programmable 16-bit counter and a dedicated 4-bit prescaler
able to perform a clock division by 1 up to 256 (different input frequencies can be
chosen through configuration registers, in the range from 3.96 Hz to 48 MHz)
●Operating modes:
–Auto-reload mode: when a software-defined value is reached, an interrupt is
triggered and the counter automatically restarts from zero
–Single-shot mode: when a software-defined value is reached, an interrupt is
triggered, the counter is stopped and the timer is disabled
●Capture capability (only for 4 timers)
2.31 Pulse width modulators (PWM)
SPEAr320S integrates 4 PWM (pulse width modulation) signal generators.
Main features:
●Prescaler to define the input clock frequency to each timer
●Programmable duty cycle from 0% to 100%
●Programmable pulse length
Doc ID 022508 Rev 127/97
Page 28
Pin descriptionSPEAr320S
3 Pin description
This chapter provides a full description of the ball characteristics and the signal multiplexing
of SPEAr320S device.
Section 3.1 shows the pin/ball map of SPEAr320S.
Section 3.2 lists the required external components to connect.
Section 3.3 describes some dedicated pins, such as:
●Clock, reset and 3V3 comparator pins
●Power supply pins
●Debug pins
●Non-multiplexed pins
Section 3.4 provides a complete description of the shared IO pins (PL_GPIOs) and their
configuration modes, as well as detailed information on all multiplexed signals, grouped by
IP.
Section 3.5 explains the available debug modes.
The following table defines the table headers and abbreviations used in this chapter.
Table 5.Headers/abbreviations
HeaderDescriptionAbbreviations
GroupGrouping of signals of the same type/functional block. –
Signal nameName of signal multiplexed on each ball.–
I= Input
Direction (Dir.)Indicates the direction of the signal.
PL_GPIO_# /Ball
Configuration mode
Pin typePad type information
Val ueIndicates the electrical value on the ball.–
PL_GPIO and ball number associated with each
signal on the package.
Indicates the available configuration mode among the
following ones:
– Mode 1
– Mode 2
– Mode 3
– Mode 4
– Alternate function
– Extended mode
See Section 3.4.2 for the description of each mode.
Signal nameDescriptionDir.PL_GPIO_# /BallConfiguration mode
I2C0
I2C0_SCLI2C0 input/output clockIOPL_GPIO_4/C1Alternate function
I2C0_SDAI2C0 input/output dataIOPL_GPIO_5/D2Alternate function
I2C1
PL_CLK2/J173
I2C1_SCLI2C1 input/output clockIO
PL_GPIO_8/C2Extended mode
PL_CLK1/K173
I2C1_SDAI2C1 input/output dataIO
PL_GPIO_9/B2Extended mode
I2C2
PL_GPIO_2/E41
PL_GPIO_19/A32
I2C2_SCLI2C2 input/output clockIO
PL_GPIO_96/H154
PL_GPIO_75/E14
Extended mode
PL_GPIO_0/F3
PL_GPIO_3/D11
PL_GPIO_20/B42
I2C2_SDAI2C2 input/output dataIO
PL_GPIO_97/H164
PL_GPIO_76/F13
Extended mode
PL_GPIO_1/E3
Table 29.I2S signals description
Signal nameDescriptionDir.PL_GPIO_# /BallConfiguration mode
Audio oversampling clock. This is
the clock that I2S_CLK derives from.
audio_over_samp_clk
The interfacing digital-to-analog
OPL_GPIO_35/D81, 2
converter (DAC) can use this clock
to (over)sample the I2S data.
I2S_CLKI2S clockOPL_GPIO_39/A91, 2
I2S_LRI2S word selectOPL_GPIO_40/B91, 2
I2S_RXI2S receive dataIPL_GPIO_42/D91, 2
I2S_TXI2S transmit dataOPL_GPIO_41/C91, 2
56/97Doc ID 022508 Rev 1
Page 57
SPEAr320SPin description
Table 30.SPP signals description
Signal nameDescriptionDir.PL_GPIO_# /BallConfiguration mode
The peripheral pulses this line low
when it has received the previous
SPP_ACKn
data and is ready to receive more
OPL_GPIO_76/F134
data. The rising edge of SPP_ACKn
can be enabled to interrupt the host.
Usage of this line varies. Most
printers will perform a line feed after
SPP_AUTOFDn
each carriage return when this line
IPL_GPIO_72/B164
is low, and carriage returns only
when this line is high.
The peripheral drives this signal high
SPP_BUSY
to indicate that it is not ready to
OPL_GPIO_75/E144
receive data.
SPP_DATA0
PL_GPIO_85/F154
SPP_DATA1PL_GPIO_84/D174
SPP_DATA2PL_GPIO_83/E164
SPP_DATA3PL_GPIO_82/E154
SPP unidirectional data linesO
SPP_DATA4PL_GPIO_81/C174
SPP_DATA5PL_GPIO_80/D164
SPP_DATA6PL_GPIO_79/F144
SPP_DATA7PL_GPIO_78/D154
Usage of this line varies. Peripherals
SPP_FAULTn
usually drive this line low when an
OPL_GPIO_71/D144
error condition exists.
This line is held low for a minimum of
SPP_INITn
50 µs to reset the printer and clear
IPL_GPIO_70/C154
the print buffer.
Usage of this line varies. Printers
SPP_PERROR
typically drive this signal high during
OPL_GPIO_74/C164
a paper empty condition.
The peripheral drives this signal high
SPP_SELECT
when it is selected and ready for
OPL_GPIO_73/A174
data transfer.
SPP_SELINn
SPP_STRBn
The host drives this line low to select
the peripheral.
Data is valid during an active low
pulse on this line.
IPL_GPIO_69/A164
IPL_GPIO_77/B174
Doc ID 022508 Rev 157/97
Page 58
Pin descriptionSPEAr320S
Table 31.Ethernet signals description
Signal nameDescriptionDir.
MII0
PHY collision
This signal is asserted by the PHY when
MII0_COL
MII0_CRS
MII0_MDC
MII0_MDIOManagement data input/outputIOPL_GPIO_10/C3Alternate function
MII0_RXCLK
a collision is detected on the medium.
This signal is not synchronous to any
clock.
(Active high)
PHY CRS
This signal is asserted by the PHY when
either the transmit or receive medium is
not idle. The PHY deasserts this signal
when both transmit and receive medium
are idle. This signal is not synchronous to
any clock. (Active high)
Management data clock
The MAC provides timing reference for
the MAC_MDIO signal through this
aperiodic clock. The maximum frequency
of this clock is 2.5 MHz.This clock is
generated from the application clock
(HCLK) via a clock divider.
Reception clock
This is the reception clock (25/2.5 MHz in
100M/10Mbps) provided by the external
PHY for MII interfaces. The MII0_RXDn
signals that the Ethernet controller
receives are synchronous to this clock.
IPL_GPIO_13/A1Alternate function
IPL_GPIO_12/D4Alternate function
OPL_GPIO_11/E5Alternate function
IPL_GPIO_20/B4Alternate function
PL_GPIO_# /
ball number
Configuration mode
(see Section 3.4.2)
MII0_RXD0
MII0_RXD1PL_GPIO_16/E6Alternate function
MII0_RXD2PL_GPIO_15/B3Alternate function
MII0_RXD3PL_GPIO_14/A2Alternate function
MII0_RXDV
MII0_RXER
58/97Doc ID 022508 Rev 1
PHY receive data
These bits provide the MII receive data
nibble. The validity of the data is qualified
with MII0_RXDV and MII0_RXER.
PHY receive data valid
When high, indicates that the data on the
MII0_RXDn bus is valid. It remains
asserted continuously from the first
recovered byte/nibble of the frame
through the final recovered byte/nibble.
PHY receive error
When high, indicates an error or carrier
extension in the received frame on the
MII0_RXDn bus.
I
IPL_GPIO_19/A3Alternate function
IPL_GPIO_18/D5Alternate function
PL_GPIO_17/C4Alternate function
Page 59
SPEAr320SPin description
Table 31.Ethernet signals description (continued)
Signal nameDescriptionDir.
Transmission clock
This is the transmission clock (25/2.5
MII0_TXCLK
MII0_TXD0PHY transmit data.
MII0_TXD1PL_GPIO_25/C6Alternate function
MII0_TXD2PL_GPIO_24/B5Alternate function
MII0_TXD3PL_GPIO_23/A4Alternate function
MII0_TXEN
MII0_TXER
MII1
MII1_COL
MII1_CRS
MHz in 100 M/10 Mbps) provided by the
external PHY for the MII interface. All the
MII0_TXDn signals generated by the
MAC are synchronous to this clock.
These bits provide the MII transmit data
nibble. The validity of the data is qualified
with MII0_TXEN and MII0_TXER.
PHY transmit data enable
When high, it indicates that valid data is
being transmitted on the MII0_TXDn bus.
PHY transmit error
When high, indicates a transmit error or
carrier extension on the MII0_RXDn bus.
PHY collision
This signal is asserted by the PHY when
a collision is detected on the medium.
This signal is not synchronous to any
clock. (Active high)
PHY CRS
This signal is asserted by the PHY when
either the transmit or receive medium is
not idle. The PHY deasserts this signal
when both transmit and receive medium
are idle. This signal is not synchronous to
any clock. (Active high)
IPL_GPIO_27/B6Alternate function
O
OPL_GPIO_22/D6Alternate function
OPL_GPIO_21/C5Alternate function
IPL_GPIO_83/E162
IPL_GPIO_82/E152
PL_GPIO_# /
ball number
PL_GPIO_26/A5Alternate function
Configuration mode
(see Section 3.4.2)
Management data clock
The MAC provides timing reference for
the MII1_MDIO signal through this
MII1_MDC
MII1_MDIOManagement data input/outputIOPL_GPIO_81/C172
MII1_RXCLK
aperiodic clock. The maximum frequency
of this clock is 2.5 MHz.This clock is
generated inside the Ethernet controller
from the application clock (HCLK) via a
clock divider.
This is the reception clock (25/2.5 MHz in
100M/10Mbps) provided by the external
PHY for MII interfaces. All MII1_RXDn
signals that the Ethernet controller
receives are synchronous to this clock.
Doc ID 022508 Rev 159/97
OPL_GPIO_80/D162
IPL_GPIO_90/G142
Page 60
Pin descriptionSPEAr320S
Table 31.Ethernet signals description (continued)
Signal nameDescriptionDir.
MII1_RXD0
MII1_RXD1PL_GPIO_86/E172
MII1_RXD2PL_GPIO_85/F152
MII1_RXD3PL_GPIO_84/D172
MII1_RXDV
MII1_RXER
MII1_TXCLK
PHY receive data
These bits provide the MII receive data
nibble. The validity of the data is qualified
with MII1_RXDV and MII1_RXER.
PHY receive data valid
When high, indicates that the data on the
MII1_RXDn bus is valid. It remains
asserted continuously from the first
recovered byte/nibble of the frame
through the final recovered byte/nibble.
PHY receive error
When high, indicates an error or carrier
extension in the received frame on the
MII1_RXDn bus.
Transmission clock
This is the transmission clock (25/2.5
MHz in 100M/10Mbps) provided by the
external PHY for the MII. All the MII
transmission signals generated by the
MAC are synchronous to this clock.
I
IPL_GPIO_89/F172
IPL_GPIO_88/F162
IPL_GPIO_97/H162
PL_GPIO_# /
ball number
PL_GPIO_87/G132
Configuration mode
(see Section 3.4.2)
MII1_TXD0PHY transmit data.
MII1_TXD1PL_GPIO_95/H142
MII1_TXD2PL_GPIO_94/H132
MII1_TXD3PL_GPIO_93/G172
MII1_TXEN
MII1_TXER
RMII0/RMII1
RMII_MDC
RMII_MDIOManagement data input/outputIOPL_GPIO_10/C3Extended mode
RMII_REF_CLK
These bits provide the MII transmit data
nibble. The validity of the data is qualified
with MII1_TXEN and MII1_TXER.
PHY transmit data enable
When high, indicates that valid data is
being transmitted on the MII1_TXDn bus.
PHY transmit error
When high, indicates a transmit error or
carrier extension on the MII1_RXDn bus.
Management data clock
The MAC provides timing reference for
the RMII_MDIO signal through this
aperiodic clock. The maximum frequency
of this clock is 2.5 MHz.This clock is
generated from the application clock
(HCLK) via a clock divider.
Contains the CRS (carrier sense) and
data valid information of the receive
interface.
These bits provide the RMII receive data.
The validity of the data is qualified with
RMII0_CRS_DV.
PHY transmit data enable
When high, indicates that valid data is
being transmitted on the RMII_TXDn bus
These bits provide the RMII transmit data.
The validity of the data is qualified with
RMII0_TX_EN.
PHY receive data valid
Contains the crs and data valid
information of the receive interface.
These bits provide the RMII receive data.
The validity of the data is qualified with
RMII1_CRS_DV.
PHY transmit data enable
When high, it indicates that valid data is
being transmitted on the RMII_TXDn bus.
These bits provide the RMII transmit data.
The validity of the data is qualified with
RMII1_TX_EN.
IPL_GPIO_14/A2Extended mode
I
OPL_GPIO_16/E6Extended mode
O
IPL_GPIO_19/A3Extended mode
I
OPL_GPIO_23/A4Extended mode
O
PL_GPIO_# /
ball number
PL_GPIO_26/A5Extended mode
PL_GPIO_27/B6Extended mode
PL_GPIO_24/B5Extended mode
PL_GPIO_25/C6Extended mode
Configuration mode
(see Section 3.4.2)
Doc ID 022508 Rev 161/97
Page 62
Pin descriptionSPEAr320S
3.5 PL_GPIO pin sharing for debug modes
In some cases the PL_GPIO pins may be used in different ways for debugging purposes.
There are three different cases (see also
1.Case 1 - All the PL_GPIO get values from Boundary scan registers during Ex-test
instruction of JTAG . Typically, this configuration is used to verify the correctness of the
soldering process during the production flow.
2. Case 2 - All the PL_GPIO maintain their original meaning but the JTAG Interface is
connected to the processor. This configuration is useful during the development phase,
but offers only “static” debug.
3. Case 3 - Some PL_GPIOs, as shown in Table 32 below, are used to connect the ETM9
lines to an external box. This configuration is typically used only during the
development phase. It offers a very powerful debug capability. When the processor
reaches a breakpoint it is possible, by analyzing the trace buffer, to understand the
reason why the processor has reached the break.
Table 32.Ball sharing during debug
SignalsCase 1 - no debugCase 2 - static debugCase 3 - full debug
This product contains devices to protect the inputs against damage due to high/low static
voltages. However, it is advisable to take normal precaution to avoid application of any
voltage higher/lower than the specified maximum/minimum rated voltages.
Caution:Stresses above those listed in Ta b l e 3 3 may cause permanent damage to the device.
Exposure to maximum rating conditions for extended periods may affect device reliability.
Table 33.Absolute maximum ratings
SymbolParameterMinMaxUnit
1.2Supply voltage for the core- 0.31.44V
V
DD
V
3.3Supply voltage for the I/Os- 0.33.9V
DD
2.5Supply voltage for the analog blocks- 0.33V
V
DD
V
1.8Supply voltage for the DRAM interface- 0.32.16V
DD
RTCRTC supply voltage-0.32.16V
V
DD
T
STG
Storage temperature-55150°C
4.2 Maximum power consumption
Note:These values take into consideration the worst cases of process variation and voltage range
and must be used to design the power supply section of the board.
Table 34.Maximum power consumption
SymbolDescriptionMaxUnit
I
DD(1.2Vsupply)
I
DD(1.8Vsupply)
I
DD(RTC)
I
DD(2.5Vsupply)
I
DD(3.3Vsupply)
P
D
1. Peak current with Linux memory test (50% write and 50% read) plus DMA reading memory.
2. With 30 logic channels connected to the device and simultaneously switching at 10 MHz.
3. Based on bench measurements for worst case silicon under worst case operating conditions. Devices
tested with operating system running, CPU and DDR2 running at 333 MHz, DDR2 driven by PLL2,
SDRAM and all on-chip peripherals and internal modules enabled.
1.2 V current and power are primarily dependent on the applications running and the use of internal chip
functions (DMA, USB, Ethernet, and so on).
3.3 V current and power are primarily dependent on the capacitive loading, frequency, and utilization of the
external buses.
Current consumption of VDD 1.2 supply voltage for the core 400mA
Current consumption of VDD 1.8 supply voltage for the
DRAM interface
(1)
150mA
Current consumption of RTC supply voltage8µA
Current consumption of 2.5V supply voltage for the analog
blocks
Current consumption of 3.3V supply voltage for the I/Os
Maximum power consumption
(3)
(2)
30mA
12mA
870mW
64/97Doc ID 022508 Rev 1
Page 65
SPEAr320SElectrical characteristics
4.3 Recommended operating conditions
To ensure proper operation of the device, it is highly recommended to follow the conditions
shown in the following table.
Table 35.Recommended operating conditions
SymbolParameterMinTypMaxUnit
V
1.2Supply voltage for the core1.141.21.3V
DD
3.3Supply voltage for the I/Os33.33.6V
V
DD
2.5PLL supply voltage
V
DD
V
2.5Oscillator supply voltage 2.252.52.75V
DD
1.8Supply voltage for DRAM interface1.701.81.9V
V
DD
RTCRTC supply voltage 1.31.51.8V
V
DD
T
A
T
J
1. For power supply filtering it is required to add an external ferrite inductor.
2. TA to be considered under JESD51 conditions or equivalent ones.
Ambient temperature
Junction temperature-40–125°C
(1)
(2)
2.252.52.75V
-40–85°C
4.4 Overshoot and undershoot
This product can support the following values of overshoot and undershoot.
Table 36.Overshoot and undershoot specifications
Parameter3V3 I/Os2V5 I/Os1V8 I/Os
Amplitude500 mV500 mV500 mV
Ratio of overshoot (or undershoot) duration with respect to
pulse width
1/31/31/3
If the amplitude of the overshoot/undershoot increases (decreases), the ratio of
overshoot/undershoot width to the pulse width decreases (increases). The formula relating
the two is:
Amplitude of OS/US = 0.75*(1- ratio of OS (or US) duration with respect to pulse width)
Note:The value of overshoot/undershoot should not exceed the value of 0.5 V. However, the
duration of the overshoot/undershoot can be increased by decreasing its amplitude.
4.5 3.3V I/O characteristics
The 3.3 V I/Os are compliant with JEDEC standard JESD8b.
Doc ID 022508 Rev 165/97
Page 66
Electrical characteristicsSPEAr320S
Table 37.Low voltage TTL DC input specification (3 V< VDD <3.6 V)
SymbolParameterMinMaxUnit
V
V
V
hyst
Table 38.Low voltage TTL DC output specification (3 V< VDD <3.6 V)
Low level input voltage0.8V
IL
High level input voltage2V
IH
Schmitt trigger hysteresis300800mV
SymbolParameterTest conditionMinMaxUnit
V
V
OH
1. Maximum current load (IOL) = 10 mA for PL_GPIO and PL_CLK pins. For the IOL max value of dedicated
pins, refer to Chapter 3: Pin description.
Table 39.Pull-up and pull-down characteristics
Low level output voltageIOL= X mA
OL
High level output voltageIOH= -X mA
(1)
(1)
0.3V
V
- 0.3V
DD
SymbolParameterTest conditionMinMaxUnit
R
R
Equivalent pull-up resistanceVI = 0 V2967kΩ
PU
Equivalent pull-down resistanceVI = V
PD
3V329103kΩ
DDE
66/97Doc ID 022508 Rev 1
Page 67
SPEAr320SElectrical characteristics
VDD2V5
24 MHz
CL1CL2
(1)
(1)
MCLK_XI
MCLK_XO
4.6 Clocking parameters
4.6.1 Master clock (MCLK)
External clock generated from a crystal oscillator
Figure 4.MCLK crystal connection
1. CL1 and CL2 are the load capacitors.
The value of the capacitors depends on the type of the selected crystal. To calculate the
value of the load capacitance, use the formula given below.
For this example, Aker C2E-24.000-12-3030-X 24 MHz oscillator has been used.
Formula
CL = (CL1*CL2 / CL1+CL2) + CS
Where CL1 and CL2 are the load capacitors and CS is the circuit stray capacitance.
In our application:
CL1 = CL2 = Cext
This implies:
Cext = (CL-CS)*2
Example:
For the Aker C2E-24.000-12-3030-X crystal, CL = 12 PF
With CS = 3 PF, we have: Cext = CL1 = CL2 = 18 PF
Note:The ESR of the used quarz must be < 50 Ohm.
Doc ID 022508 Rev 167/97
Page 68
Electrical characteristicsSPEAr320S
32.768 kHz
CL1CL2
(1)
(1)
RTC_XIRTC_XO
4.6.2 Real-time clock (RTC)
External clock generated from a crystal oscillator
Figure 5.RTC crystal connection
GN D
1. CL1 and CL2 are the load capacitors.
The value of the capacitors depends on the type of the selected crystal. For example, using
Fox Electronics, P/N NC26LF-327 32.768 KHz oscillator, the value of the capacitors is
15
pF. The oscillator may not start if we use the crystal Fox fx325bs.
If the shunt capacitance (Co) of the crystal is ~7.0 pF, then the maximum ESR of the crystal
must be less than 50 Ohms.
68/97Doc ID 022508 Rev 1
Page 69
SPEAr320SElectrical characteristics
4.7 LPDDR and DDR2 pin characteristics
Table 40.DC characteristics
SymbolParameterTest conditionMinMaxUnit
V
V
V
hyst
Table 41.Driver characteristics
Low level input voltageSSTL18-0.3V
IL
High level input voltageSSTL18V
IH
+0.125V
REF
-0.125V
REF
1V8+0.3V
DDE
Input voltage hysteresis200mV
SymbolParameterMinTypMaxUnit
R
O
Table 42.On-die termination
Output impedance45Ω
SymbolParameterMinTypMaxUnit
RT1Termination value of resistance for on die termination75Ω
RT2Termination value of resistance for on die termination150Ω
Table 43.Reference voltage
SymbolParameterMinTypMaxUnit
V
REFIN
Voltage applied to core/pad0.49 * V
DDE
0.500 * V
0.51 * V
DDE
DDE
V
Doc ID 022508 Rev 169/97
Page 70
Electrical characteristicsSPEAr320S
4.8 ADC pin characteristics
Table 44.ADC pin characteristics
SymbolParametersMinTypMaxUnit
f
ADC_CLK
AV
DD
V
REFP
V
REFN
V
IREF
t
STARTUP
ADC_CLK frequency314MHz
ADC supply voltage2.5V
Positive reference voltage2.5V
Negative reference voltage0V
Internal reference voltage1.9522.05V
Startup time50µs
Input range (absolute)AGND - 0.3AVDD - 0.3V
V
AIN
C
AIN
R
AIN
t
CONV
Conversion rangeV
REFN
Input capacitance56.48pF
Input mux resistance (total
equivalent sampling resistance)
1.522.5KΩ
Conversion time
(f
ADC_CLK
=14 MHz)
V
REFP
1µs
Conversion time13
INLIntegral linearity error±1LSB
DNLDifferential linearity error
±1LSB
V
ADC_CLK
cycles
70/97Doc ID 022508 Rev 1
Page 71
SPEAr320SElectrical characteristics
V
DD
1.2
V
DD
1.8
V
DD
2.5
V
DD
3.3
Power-up sequence
t
t
t
1V2
V3
1V8
MRESET
Start-up time= 2 ms
V5
4.9 Power-up sequence
It is recommended to power up the power supplies in the order shown in Figure 6.
VDD 1.2 is brought up first, followed by VDD 1.8, then VDD 2.5 and finally VDD 3.3. The minimum
time (
Δt) between each power up is >0 µs.
Figure 6.Power-up sequence
4.10 Power-down sequence
All power supplies can be shut down at the same time.
4.11 Reset release
The master reset (MRESET) must be released after all the power supplies are stable and for
a time interval of 2
Figure 7.Reset release
ms, which is the start-up time of the main oscillator.
V
DD
V
DD
V
2
DD
V
3
DD
Doc ID 022508 Rev 171/97
Page 72
Timing requirementsSPEAr320S
t
CK
t
D
CLD[23:0], CLAC,
CLLE, CLLP, CLFP,
CLPOWER
CLCP
5 Timing requirements
This chapter provides the timing requirements for the synchronous and asynchronous IPs
present in SPEAr320S.
The signal transition levels used for timing measurements are: 0.2*VDD and 0.8*VDD.
5.1 External interrupt timing characteristics
In legacy modes, all the interrupts are high-level triggered. In extended mode, interrupt
trigger polarity is programmable as rising or falling edge.
Table 45.PL_GPIO external interrupt input timing
SymbolDescriptionMinUnit
tINTMinimum width for rising edge interrupt pulse24ns
5.2 Reset timing characteristics
Table 46.Cold reset (at power-on)
SymbolDescriptionMinUnit
tRPMRESET pin active low state duration10ms
Note:Warm reset is generated by writing any value to the system controller SYSSTAT register.
5.3 CLCD timing characteristics
The CLCD has a wide variety of configurations, and the parameters change accordingly.
The timing characterization is performed assuming an output load capacitance of 10 pF on
all outputs.
Figure 8.CLCD waveform
72/97Doc ID 022508 Rev 1
Page 73
SPEAr320STiming requirements
t
DQSQ
t
QH
t
QH
t
DQSQ
t
DQSQ
DDR_MEM_DQS_#
DDR_MEM_DQ_#
DDR_MEM_CLKP/
DDR_MEM_CLKN
t
CK
Table 47.CLCD timing requirements
SymbolDescriptionMinMaxUnit
t
CK
t
D
CLCP clock period20.8341.66
CLCP to CLCD output data delay19.5
5.4 DDR2 timing characteristics
The timing parameters listed below are defined by the JEDEC Standard for DDR memories.
DDR memories whose parameters are within the ranges defined in
Ta bl e 50 can be interfaced with SPEAr320S.
Read cycle timing apply to DQS and DQ input to SPEAr. Write cycle timings refer to DQS
and DQ output to SPEAr.
The timing characterization is performed assuming an output load capacitance of 10 pF on
all the DDR pads.
5.4.1 DDR2 read cycle timing characteristics
Figure 9.DDR2 read cycle waveform
ns
Ta bl e 48, Ta bl e 49 and
Table 48.DDR2 read cycle timing requirements
SymbolDescriptionMinMaxUnit
t
CK
DQSQ
t
QH
DDR_MEM_CLKP/CLKN cycle time3
DQS to DQ input setup time00.25tCK+0.4
DQS to DQ input hold time0.25tCK+0.70.5t
CK
Doc ID 022508 Rev 173/97
nst
Page 74
Timing requirementsSPEAr320S
DDR_MEM_DQS_#
DDR_MEM_DQ_#
DDR_MEM_CLKP/
DDR_MEM_CLKN
t
DS
t
DH
t
DH
t
DS
t
DS
t
DH
t
DQSS
t
IStIH
CLK
Address and
commands
5.4.2 DDR2 write cycle timing characteristics
Figure 10.DDR2 write cycle waveform
Table 49.DDR2 write cycle timing requirements
SymbolDescriptionMinMaxUnit
t
DQSS
DS
t
DH
Positive DQS latching edge to associated CK edge-0.50.5
DQ & DQM output setup time relative to DQS00.25tCK – 0.76
DQ & DQM output hold time relative to DQS00.25tCK – 0.84
5.4.3 DDR2 command timing characteristics
Figure 11.DDR2 command waveform
Table 50.DDR2 command timing requirements
nst
SymbolDescriptionMinMaxUnit
t
t
Address and control output setup time00.5tCK – 0.5
IS
Address and control output hold time00.5tCK – 0.59
IH
74/97Doc ID 022508 Rev 1
ns
Page 75
SPEAr320STiming requirements
EMI_A#
EMI_BYTEN#
EMI_D#
EMI_CEn#
EMI_OE
Address
Byte Enable
Data
t
SE
t
SCS
t
ENr
t
DCS
EMI_WAIT
t
CS->Wait
t
WAIT
EMI_A#
EMI_BYTEN#
EMI_D#
EMI_CEn#
EMI_WE
Write Data
Byte Enable
Data
t
SE
t
SCS
t
ENw
t
DCS
EMI_WAIT
t
CS
->t
WAIT
t
WAIT
5.5 EMI timing characteristics
Figure 12. EMI read cycle waveform with acknowledgement on EMI_WAIT
Note:The values of tSE, t
Table 51.EMI timing requirements for read cycle with acknowledgement on WAIT
ENr
, t
DCS
, t
are programmable via the EMI registers.
SCS
SymbolMin
t
CS->Wait
t
WAIT
t
4*t
HCLK
HCLK
Note:Values in Ta bl e 51 refer to the common internal source clock which has a period of
t
= 6 ns.
HCLK
Figure 13. EMI write cycle waveform with acknowledgement on EMI_WAIT
Note:The values of tSE, t
ENw
, t
, t
DCS
are programmable via the EMI registers.
SCS
Doc ID 022508 Rev 175/97
Page 76
Timing requirementsSPEAr320S
EMI_A#
EMI_BYTEN#
EMI_D#
EMI_CEn#
EMI_OE
Address
Byte Enable
Data
t
SE
t
SCS
t
ENr
t
DCS
EMI_A#
EMI_BYTEN#
EMI_D#
EMI_CEn#
EMI_WE
Write Data
Byte Enable
Data
t
SE
t
SCS
t
ENw
t
DCS
Table 52.EMI timing requirements for write cycle with acknowledgement on WAIT
SymbolMin
t
CS->Wait
t
WAIT
t
4*t
HCLK
HCLK
Note:Values in Ta bl e 52 refer to the common internal source clock which has a period of
t
= 6 ns.
HCLK
Figure 14. EMI read cycle waveform without acknowledgement on EMI_WAIT
Note:The values of tSE, t
ENr
, t
DCS
, t
are programmable via the EMI registers.
SCS
Figure 15. EMI write cycle waveform without acknowledgement on EMI_WAIT
Note:The values of tSE, t
76/97Doc ID 022508 Rev 1
ENw
, t
, t
DCS
are programmable via the EMI registers.
SCS
Page 77
SPEAr320STiming requirements
t
D
MII#_TXCLK
MII#_TXD0-MII#_TXD3,
MII#_TXEN, MII#_TXER
t
ck
Table 53.EMI timing requirements
DirectionSignal nameMaxMinUnit
EMI_A0-EMI_A238.6122931.93584
EMD0-EMID159.4712912.260195
EMI_CE08.7646482.90581
EMI_CE17.9773482.636304
EMI_CE29.0276242.930175
Output
EMI_CE39.296313.006315
EMI_BYTEN09.5543883.092855
EMI_BYTEN19.2335923.038856
EMI_RE8.1930182.680564
EMI_WE8.1726192.80189
ns
Input
EMI_D0-EMI_D1510.81881.30245
5.6 Ethernet MII timing characteristics
The timing characterization is performed assuming an output load capacitance of 5 pF on
the MII TX clock (MII#_TXCLK) and 10 pF on the other pads.
5.6.1 MII transmit timing characteristics
Figure 16. MII TX waveform
Table 54.MII TX timing requirements
SymbolDescriptionMinMaxUnit
t
CK
t
D
Note:To calculate the t
you have to apply the following formula: t
MII#_TXCLK clock period4040
MII#_TXCLK to MII output data delay3.3411.86
value for the PHY, you have to consider the next tCK rising edge, so
SETUP
SETUP
= tCK - t
max
Doc ID 022508 Rev 177/97
ns
Page 78
Timing requirementsSPEAr320S
MII#_RXCLK
t
S
t
H
t
CK
MII#_RXD0-MII#_RXD3
MII#_RXER, MII#_RXDV
T
D
MDC
t
CK
t
H
t
S
MDIO(INPUT)
MDIO (OUTPUT)
5.6.2 MII receive timing characteristics
Figure 17. MII RX waveform
Table 55.MII RX timing requirements
SymbolDescriptionMinMaxUnit
t
CK
S
t
H
MII#_TXCLK clock period4040
Setup time requirement for MII receive data12.5
Hold time requirement for MII receive data-2
5.6.3 MDIO timing characteristics
Figure 18. MDC waveform
Table 56.MDC timing requirements
nst
78/97Doc ID 022508 Rev 1
SymbolDescriptionMinMaxUnit
t
CK
t
D
t
S
t
H
MDC clock period614.4614.4
Falling edge of MDC to MDIO output delay2040.64
Setup time requirement for MDIO input9.6
Hold time requirement for MDIO input-6.6
ns
Page 79
SPEAr320STiming requirements
RMII_REF_CLK
RMIIn_TXD0, RMIIn_TXD1
RMIIn_TX_EN
TfTr
TCKhigh
TCKlow
TD
RMII_REF_CLK
Th
TCKhigh
TCKlow
TfTr
Ts
RMIIn_RXD0, RMIIn_RXD1
RMIIn_CRS_DV
Note:When MDIO is used as output the data are launched on the falling edge of the clock as
shown in
Figure 18.
5.7 Ethernet RMII timing characteristics
5.7.1 RMII transmit timing characteristics
Figure 19.RMII TX waveform
Table 57.RMII TX timing requirements
SymbolDescriptionMinMaxUnit
t
CK
RMII_REF_CLK period20
Clock to RMII0_TXD output delay2.959.5
t
D
Clock to RMII1_TXD output delay2.959.3
5.7.2 RMII receive timing characteristics
Figure 20.RMII RX waveform
ns
Doc ID 022508 Rev 179/97
Page 80
Timing requirementsSPEAr320S
FSMC_CS#
FSMC_WE
FSMC_D#
Command
t
CLE
t
WE
t
IO
FSMC_CMD_LE
FSMC_ADDR_LE
FSMC_CS#
FSMC_WE
FSMC_D#
Address
t
ALE
t
WE
t
IO
Table 58.RMII RX timing requirements
SymbolDescriptionMinMaxUnit
t
RMII_REF_CLK period20
CK
Setup time requirement for RMII0 receive data4.9
t
S
Setup time requirement for RMII1 receive data5
Hold time requirement for RMII0 receive data0.1
t
H
Hold time requirement for RMII1 receive data-0.09
5.8 FSMC timing characteristics
The FSMC present in SPEAr320S can interface external parallel NAND Flash memories.
The timing characterization is performed using primetime assuming an output load
capacitance of 3
10
pF on FSMC_ADDR_LE and FSMC_CMD_LE.
Figure 21. Output command signal waveform
pF on the data, 15 pF on FSMC_CSx, FSMC_RE and FSMC_WE and
ns
Figure 22. Output address signal waveform
80/97Doc ID 022508 Rev 1
Page 81
SPEAr320STiming requirements
FSMC_CS#
FSMC_WE
FSMC_D# (out)
Data Out
t
IO
FSMC_D# (in)
FSMC_RE
t
RE -> IO
t
WE
t
RE
t
READ
t
NFIO -> FFs
Figure 23. In/out data address signal waveform
Table 59.FSMC timing requirements
SymbolMinMax
t
CLE
t
ALE
(1)
t
WE
(1)
t
RE
(2)
t
IO
(3)
t
READ
1. Programmable by the Tset bits in the FSMC registers.
2. Programmable by the Thiz bits in the FSMC registers.
3. Programmable by the Twait bits in the FSMC registers.
(((Tset+1) * t
(((Tset+1) * t
(((Thiz +1) * t
-3.92.8
-4.2 2.6
) - 3 ns) (((Tset+1) * t
HCLK
) - 3 ns) (((Tset+1) * t
HCLK
) - 3 ns) (((Thiz +1) * t
HCLK
((Twait+1)* t
HCLK
HCLK
HCLK
HCLK
) + 3 ns)
) + 3 ns)
)+ 3 ns)
Note:Values in Ta bl e 59 refer to the common internal source clock which has a period of t
ns.
HCLK
= 6
Doc ID 022508 Rev 181/97
Page 82
Timing requirementsSPEAr320S
Table 60.FSMC signals timing requirements
DirectionSignal nameMaxMin
FSMC_CMD_LE10.573.1
FSMC_ADDR_LE9.52.8
FSMC_WE8.52.9
FSMC_RE8.42.75
FSMC_CS09.1658363.07661
FSMC_CS18.4737222.81431
Output
FSMC_CS29.1727393.02958
FSMC_CS39.8084263.21934
FSMC_D7-FSMC_D07.7101642.2987158-bit
FSMC_D15-FSMC_D89.3015472.4201658-bit
FSMC_D15-FSMC_D09.3015472.29871516-bit
FSMC_RDY/BUSY6.881.7
FSMC_D7-FSMC_D08.88091.18356 8-bit
Input
FSMC_D15-FSMC_D810.8753021.37802 8-bit
FSMC_D15-FSMC_D010.8753021.1835616-bit
Data path
width
Unit
ns
82/97Doc ID 022508 Rev 1
Page 83
SPEAr320STiming requirements
5.9 I2C timing characteristics
The timing characterization is performed using primetime assuming an output load
capacitance of 10 pF on SCL and SDA.
Figure 24. Output signal waveform for I2C signals
The timings of the high and low level of SCL (t
SCLHigh
and t
SCLLow
) are programmable.
The clock-to-output data delay is:
●MIN (T(clk+data)min) = 5.9
●MAX (T(clk+data)max) = 15
The timings shown in Figure 24 depend on the programmed value of t
SCLHigh
and t
SCLLow.
The values listed in Ta bl e 61 to Ta bl e 63 have been calculated using the minimum
programmable values of :
●High-speed mode: IC_HS_SCL_HCNT= 19 and IC_HS_SCL_LCNT= 53 registers
●Fast-speed mode: IC_FS_SCL_HCNT= 99 and IC_FS_SCL_LCNT= 215 registers
●Standard-speed mode: IC_SS_SCL_HCNT= 664 and IC_SS_SCL_LCNT=
780 registers
These minimum values depend on the AHB clock frequency, which is 166 MHz.
Table 61.I2C timing requirements in high-speed mode
ParameterMinUnit
t
SU-STA
t
HD-STA
t
SU-DAT
t
HD-DAT
t
SU-STO
t
HD-STO
140
325
300
ns
1
620
4745
Doc ID 022508 Rev 183/97
Page 84
Timing requirementsSPEAr320S
T
h
I2S_CLK
I2S_TX, I2S_LR
T
CKhigh
T
CKlow
T
s
T
f
T
r
Table 62.I2C timing requirements in fast-speed mode
ParameterMinUnit
t
SU-STA
t
HD-STA
t
SU-DAT
t
HD-DAT
t
SU-STO
t
HD-STO
Table 63.I2C timing requirements in standard-speed mode
Note:In full-speed mode, the frequency is 24 MHZ (41.6 ns). The data is launched at the falling
edge of the 24
time is always 20.8
MHZ clock and captured on the clock’s rising edge (the effective available
ns)
Doc ID 022508 Rev 185/97
Page 86
Timing requirementsSPEAr320S
SMI_CLK
SMI_DATAIN
t
S
t
H
t
CK
t
D
t
CSf
t
CSr
SMI_DATAOUT
SMI_CS_0,1
5.12 SMI timing characteristics
Figure 27. SMI input/output waveform
Table 67.SMI timing requirements
SymbolDescriptionMinMaxUnit
t
CK
t
D
t
S
t
H
t
CSf
t
CSr
SMI clock period2050
SMI_CLK to SMI_DATAOUT output delay-2.963.05
Setup requirement for SMI_DATAIN8.05
Hold requirement for SMI_DATAIN-2.53
Minimum and maximum delay of falling edge of
SMI_CS_0 , 1 with regard to SMI_CLK
Minimum and maximum delay of rising edge of
SMI_CS_0 , 1 with regard to SMI_CLK
-3.02.9
-2.82.8
ns
86/97Doc ID 022508 Rev 1
Page 87
SPEAr320STiming requirements
1
SSP#_CLK
(CPOL=0)
SSP#_CLK
(CPOL=1)
2
3
5.13 SSP timing characteristics
This module provides a programmable length shift register which allows serial
communication with other SSP devices through a 3- or 4-wire interface (SSP#_CLK,
SSP#_MISO, SSP#_MOSI and SSP#_CSn), where x= 0 to 2 and n= 1 to 4.
The SSP supports the following features related to timings:
●Master/Slave mode operation
●Chip-selects for interfacing multiple slave SPI devices.
●3 or 4 wire interface (SSP_SCK, SSP_MISO, SSP_MOSI and SSP_CSn)
●Single interrupt
●Separate DMA events for SPI receive and transmit
●16-bit shift register
●Receive buffer register
●Programmable character length (2 to 16 bits)
●Programmable SSP clock frequency range
●8-bit clock pre-scaler
●Programmable clock phase (delay or no delay)
●Programmable clock polarity (CPOL)
Note:The following tables and figures show the characterization of the SSP using the SPI
protocol.
Table 68.SSP timing requirements (all modes)
(1)
No.
1T
3T
1. The number used in the graphics to represent the corresponding parameter.
c(CLK)
w(CLKH)
w(CLKL)
ParametersMinMaxUnit
Cycle time, SSP#_CLK24–
Pulse duration, SSP#_CLK high0.49*To 0.51*To
Pulse duration, SSP#_CLK low0.49*To0.51*To
T = Tc(CLK) = SSP#_CLK period is equal to the SSP module master clock divided by a
configurable divider.
No timing characterization has been performed for the UART. For information related to
baud rate generation, refer to:
●Section 2.12: Asynchronous serial ports (UART)
●RM0321, Reference manual, SPEAr320S address map and registers
90/97Doc ID 022508 Rev 1
Page 91
SPEAr320SPackage information
6 Package information
In order to meet environmental requirements, ST offers these devices in different grades of
ECOPACK
specifications, grade definitions and product status are available at:
®
packages, depending on their level of environmental compliance. ECOPACK®
www.st.com.
ECOPACK® is an ST trademark.
Table 73.LFBGA289 (15 x 15 x 1.7 mm) mechanical data
mminches
Dim.
Min.TypeMax.Min.TypeMax.
A1.7000.0669
A10.2700.0106
A20.9850.0387
A30.2000.0078
A40.8000.0315
b0.4500.5000.5500.01770.01970.0217
D14.85015.00015.1500.58460.59060.5965
D112.8000.5039
E14.85015.00015.1500.58460.59060.5965
E112.8000.5039
e0.8000.0315
F1.1000.0433
ddd0.2000.0078
eee0.1500.0059
fff0.0800.0031
Doc ID 022508 Rev 191/97
Page 92
Package informationSPEAr320S
Figure 31. LFBGA289 package dimensions
Table 74.Thermal resistance characteristics
PackageΘ
JC
(°C/W)
LFBGA28918.524.533
1. Measured on JESD51 2s2p test board.
92/97Doc ID 022508 Rev 1
Θ
(°C/W)ΘJA(°C/W)
JB
(1)
Page 93
SPEAr320SAcronyms
Appendix A Acronyms
Table 75.List of acronyms
AcronymDefinition
ADCAnalog-to-digital converter
AESAdvanced encryption standard
AHBAMBA high speed bus
AMBAAdvanced microcontroller bus architecture
APBAdvanced peripheral bus
BISTBuilt-In self test
CANController area network
CBCCipher block chaining
CMOSComplimentary metal-oxide semiconductor
CPUCentral processing unit
CRCCyclic redundancy check
DDRDouble data rate
DESData encryption standard
DLLDelay locked loop (when applied to DDR memories)
DMADirect memory access
EMIExternal memory interface
ETMEmbedded trace macrocell
FIFOFirst-in-first-out
FIQFast interrupt request
FPGAField programmable gate array
FSMCFlexible static memory controller
GBGiga bytes
GPIOGeneral purpose input / output
HLOSHigh-level operating system
HMIHuman machine interface
HWHardware
IrDAInfrared data association
IRQInterrupt request
JPEGJoint photographic experts group
JTAGJoint test action group
KBKilo bytes
LCDLiquid color display
Doc ID 022508 Rev 193/97
Page 94
AcronymsSPEAr320S
Table 75.List of acronyms (continued)
AcronymDefinition
LSBLeast significant bit
MACMedia access control
MBMega bytes
MCUMicrocontroller unit
MD5Message digest 5
MIIMedia independent interface
MMUMemory management unit
MSBMost significant bit
PHYPhysical (device, transceiver, layer)
PLLPhase locked loop
PWMPulse width modulation
RAMRandom access memory
RASReconfigurable array subsystem
RFRadio frequency
RFUReserved for future use
RISCReduced instruction set computing
RMIIReduced media independent interface
ROMRead only memory
RTCReal-time clock
RTOSReal-time operating system
RXReceive
SHA-1Secure hash algorithm
SMISerial memory interface
SoCSystem-on-chip
SPISerial peripheral interface
SPPStandard parallel port
SRAMStatic RAM
SSPSynchronous serial port
SWSoftware
TCMTightly coupled memory
TFTThin film transistor, a display technology
TXTransmit
UARTUniversal asynchronous receiver transmitter
USBUniversal serial bus
94/97Doc ID 022508 Rev 1
Page 95
SPEAr320SAcronyms
Table 75.List of acronyms (continued)
AcronymDefinition
VICVectored interrupt controller
WDTWatchdog timer
Doc ID 022508 Rev 195/97
Page 96
Revision historySPEAr320S
Revision history
Table 76.Document revision history
DateRevision Changes
5-Apr-20121Initial release.
96/97Doc ID 022508 Rev 1
Page 97
SPEAr320S
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the
right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any
time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no
liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this
document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products
or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such
third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS EXPRESSLY APPROVED IN WRITING BY TWO AUTHORIZED ST REPRESENTATIVES, ST PRODUCTS ARE NOT
RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING
APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY,
DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE
GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER’S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void
any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any
liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.