LM3S5632 Luminary Micro, Inc, LM3S5632 Datasheet - Page 36

• Manufacturer Part Number: LM3S5632
• Description: Lm3s5632 Arm Microcontroller
• Manufacturer: Luminary Micro, Inc

Architectural Overview
1.4.4.5
1.4.5
1.4.5.1
1.4.5.2
1.4.5.3
36
The LM3S5632 controller supports the USB 2.0 full-speed configuration with Device or USB Host
mode. The specified throughput for a USB 2.0 full-speed controller is 12 Mbps.
Controller Area Network (see page 489)
Controller Area Network (CAN) is a multicast shared serial-bus standard for connecting electronic
control units (ECUs). CAN was specifically designed to be robust in electromagnetically noisy
environments and can utilize a differential balanced line like RS-485 or a more robust twisted-pair
wire. Originally created for automotive purposes, now it is used in many embedded control
applications (for example, industrial or medical). Bit rates up to 1Mb/s are possible at network lengths
below 40 meters. Decreased bit rates allow longer network distances (for example, 125 Kb/s at
500m).
A transmitter sends a message to all CAN nodes (broadcasting). Each node decides on the basis
of the identifier received whether it should process the message. The identifier also determines the
priority that the message enjoys in competition for bus access. Each CAN message can transmit
from 0 to 8 bytes of user information. The LM3S5632 includes one CAN units.
System Peripherals
Programmable GPIOs (see page 238)
General-purpose input/output (GPIO) pins offer flexibility for a variety of connections.
The Stellaris
individual GPIO port. The GPIO module is FiRM-compliant (compliant to the ARM Foundation IP
for Real-Time Microcontrollers specification) and supports 1-33 programmable input/output pins.
The number of GPIOs available depends on the peripherals being used (see “Signal Tables” on page
619 for the signals available to each GPIO pin).
The GPIO module features programmable interrupt generation as either edge-triggered or
level-sensitive on all pins, programmable control for GPIO pad configuration, and bit masking in
both read and write operations through address lines. Pins configured as digital inputs are
Schmitt-triggered.
Three Programmable Timers (see page 283)
Programmable timers can be used to count or time external events that drive the Timer input pins.
The Stellaris
block provides two 16-bit timers/counters that can be configured to operate independently as timers
or event counters, or configured to operate as one 32-bit timer or one 32-bit Real-Time Clock (RTC).
Timers can also be used to trigger analog-to-digital (ADC) conversions.
When configured in 32-bit mode, a timer can run as a Real-Time Clock (RTC), one-shot timer or
periodic timer. When in 16-bit mode, a timer can run as a one-shot timer or periodic timer, and can
extend its precision by using an 8-bit prescaler. A 16-bit timer can also be configured for event
capture or Pulse Width Modulation (PWM) generation.
Watchdog Timer (see page 317)
A watchdog timer can generate nonmaskable interrupts (NMIs) or a reset when a time-out value is
reached. The watchdog timer is used to regain control when a system has failed due to a software
error or to the failure of an external device to respond in the expected way.
The Stellaris
register, interrupt generation logic, and a locking register.
®
®
®
GPIO module is comprised of five physical GPIO blocks, each corresponding to an
General-Purpose Timer Module (GPTM) contains three GPTM blocks. Each GPTM
Watchdog Timer module consists of a 32-bit down counter, a programmable load
Preliminary
June 02, 2008