Development Kit Contents................................................................................................................................10
Power Supplies.............................................................................................................................................15
User Switch and LED.......................................... ... ... .... ... ... ..........................................................................19
Chapter 4: Using the In-Circuit Debugger Interface....................................................................................23
Appendix A: Stellaris® LM3S9B96 Development Board Schematics........................................................ 25
Appendix B: Stellaris® LM3S9B96 Development Board Component Locations......................................33
Appendix C: Stellaris® LM3S9B96 Development Board Connection Details ...........................................35
DC Power Jack....................................................................... ... .... ... ... ... .... ... ................................................... 35
ARM Target Pinout ........................................................................................................................................... 35
Appendix D: Stellaris® LM3S9B96 Development Board Microcontroller GPIO Assignments ................37
Test Port .......................................................................................................................................................53
Camera Connector........................................................................................................................................53
5 V Power Pin...............................................................................................................................................53
Using the Widget Interface ...............................................................................................................................53
Writing Your Own Stellaris Application .........................................................................................................53
Loading a New Image to the FPGA..................................................................... ... .... ... ... ... .... ... ... ...................61
Installing the Software...................................................................................................................................62
Modifying the Default Image.........................................................................................................................62
Primary EM Header ......................................................................................................................................74
Secondary EM Header..................................................................................................................................75
Table F-2. Version Register............................................................................................................................ 55
Table F -3. System Control Register ........................... .... ... ... .................................................... ... ...................56
Table F-5. Interrupt Status Register ...............................................................................................................57
Table F-6. Test Pad Register..........................................................................................................................58
Table F-7. LCD Control Register .................................................................................................................... 59
Table F -8. EPI Signal Descriptions ................... ............................................................................................. 63
The Stellari s® LM3S9B96 Develop ment Board prov ides a plat form for developing systems around
the advanced capabilities of the LM3S9B96 ARM® Cortex™-M3-based microcontroller.
The LM3S9B96 is a member of the Stellaris Tempest-class microcontroller family. Tempest-class
devices include capabilities such as 80 MHz clock speeds, an External Peripheral Interface (EPI)
and Audio I
DK-LM3S9B96 board includes a rich set of peripherals found on other Stellaris boards.
The development board includes an on-board in-circuit debug interface (ICDI) that supports both
JT AG and SWD debugging. A stand ard ARM 20-pin debug header suppor ts an array of debugging
solutions.
The Stellaris® LM3S9B96 Development Kit accelerates development of Tempest-class
microcontrollers. The kit also includes extensive example applications and complete source code.
Features
The Stellaris® LM3S9B96 Development Board includes the following features.
Simple set-up—USB cable provides debugging, communication, and power
Flexible development platform with a wide range of peripherals
2
S interfaces. In addition to new hardware to support these features, the
Color LCD graphics display
– TFT LCD module with 320 x 240 resolution
– Resistive touch interface
80 MHz LM3S9B96 microcontroller with 256 K Flash, 96 K SRAM, and integrated Ethernet
1 MB serial Flash memory
Precision 3.00 V voltage reference
SAFERTOS™ operating system in microcontroller ROM
2
I
S stereo audio codec
– Line In/Out
– Headphone Out
– Microphone In
Controller Area Network (CAN) Interface
10/100 BaseT Ethernet
USB On-The-Go (OTG) Connector
– Device, Host, and OTG modes
September 5, 20107
User LED and push button
Thumbwheel potentiometer (can be used for menu navigation)
MicroSD card slot
Supports a range of debugging options
– Integrated In-circuit Debug Interface (ICDI)
– JTAG, SWD, and SWO all supported
– Standard ARM® 20-pin JT AG debug connector
USB Virtual COM Port
Jumper shunts to conveniently reallocate I/O resources
Develop using tools supporting Keil™ RealView® Microcontroller Development Kit
(MDK-ARM), IAR Embedded Workbench, Code Sourcery GCC development to ols, Code Red
Technologies development tools, or Texas Instruments’ Code Composer Studio™ IDE
Supported by StellarisWare® software including the graphics library, the USB library, and the
peripheral driver library
Optional expansion boards that work with the External Peripheral Interface (EPI) of the
DK-LM3S9B96 development board extend the capabilities of this development platform (each
board sold separately)
– Stellaris® Flash and SRAM Memory Expansion Board (DK-LM3S9B96-FS8) (sold
separately)
•Provides Flash memory, SRAM, and an improved performance LCD interface
For more information on the DK-LM3S9B96-FS8 memory expansion board, see
Appendix E, “Stellaris® LM3S9B96 Flash and SRAM Memory Expansion Board,” on
page 41.
•Provides a transition between the Stellaris External Peripheral Interface (EPI)
connector and the RF Evaluation Module (EM) connecto r
•Enables wireless application development using Low Power RF an d RF ID
evaluation modules on the Stellaris DK-LM3S9B96 platform
For more information on the DK-LM3S9B96-EM2 e xpansion board, see Appendix G,
“Stellaris® LM3S9B96 EM2 Expansion Board,” on page 69.
8September 5, 2010
Figure 1-1.DK-LM3S9B96 Development Board
Debug I nterface
USB Connector for
Debug and/or Power
Stellaris
LM3S39B96
Microcontroller
CAN Bus Interface
3 .5 " LCD T ouc h Panel
USB connector wi th
Host, De vice an d
On-the-Go modes
10/ 100 Et hernet
User LED
microSD Card Slot
Potentiometer
5 VDC supply input
JTAG/SWD In/
Out C onnector
User Switch
Reset switch
Power and
Ground Test
Points
3 .00V Analog
Reference
Headphone Out put
Audi o Li ne Output
Microphone Input
Audi o Li ne I n put
1MB Serial Fl ash Mem ory
Stellaris® LM3S9B96 Development Kit User’s Manual
September 5, 20109
Development Kit Contents
The Stellaris® LM3S9B96 Development Kit contains everything needed to develop and run a
range of applications using Stellaris microcontrollers:
LM3S9B96 development board
8 MB SDRAM expansion board
EPI signal breakout board
Retractable Ethernet cable
USB Mini-B cable for debugger use
USB Micro-B cable for OTG-to-PC connection
USB Micro-A to USB A adapter for USB Host
USB Flash memory stick
microSD Card
20-position ribbon cable
CD containing:
– A supported version of one of the following (including a toolchain-specific Quickstart
guide):
•Keil™ RealView® Microcontroller Development Kit (MDK-ARM)
•IAR Embedded Workbench
•Code Sourcery GCC development tools
•Code Red Te chnologies development tools
•Texas Instruments’ Code Composer Studio™ IDE
– Complete documentation
– Quickstart application source code
– Stellaris® Firmware Development Package with example source code
10September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
USB
USB
USB
T
Stellaris
Tempest-cl ass
LM 3S9B96
Microcontroller
QVGA
Color LCD Module
I/O Signal Break-out
Switch
LED
Tempest LM 3S9B96 D evelo pment Bo ard
I/O Signal B reak-out
I/O signals
Dual
USB
Device
Controller
Debug
JTAG/SWD
Output/Input
Debug USB
Reset
+3.3V
Regulator
SWD/JTAG Mux
UART0
Debug
USB
Control+5V host supply
USB
micro-AB
connector
OTG/Host/Device
T
a
r
g
e
t
C
a
b
l
e
MicroSD
card slot
1GB
1MB
Serial
Flash
EPI
Touch
RJ45
Jack+
Magnetics
Ethernet
Pot
Thumb
wheel
Pot
8MB SDRAM
Headphone
Jack
Line Out
Jack
I2S
Audio
CODEC
Line Output
Phones
Block Diagram
Figure 1-2.DK-LM3S9B96 Development Board Block Diagram
Development Board Specifications
Board supply voltage: 4.75–5.25 Vdc from one of the following sources:
– Debugger (ICDI) USB cable (connected to a PC)
– USB Micro-B cable (connected to a PC)
– DC power jack (2.1x 5.5mm from exte rn al po we r su pp ly)
Break-out power output: 3.3 Vdc (100 mA max)
September 5, 201011
Dimensions (excluding LCD panel):
– 4.50” x 4.25” x 0.60” (LxWxH) with SDRAM board
– 4.50” x 4.25” x 0.75” (LxWxH) with EPI breakout board
Analo g Re fe re nc e: 3. 0 V +/-0.2 %
RoHS status: Compliant
NOTE: When the LM3S9B96 Development Board is used in USB Host mode, the host connector
is capable of supplying power to the connected USB device. The available supply current
is limited to ~200 mA unless the development board is powered from an external 5 V
supply with a =600mA rating.
12September 5, 2010
CHAPTER 2
Stellaris® LM3S9B96 Development Board
Hardware Description
In addition to an LM3S9B96 microcontroller, the development board includes a range of useful
peripheral features and an integrated in-circuit debug interface (ICDI). This chapter describe s how
these peripherals operate and interface to the microcontroller
LM3S9B96 Microcontroller Overview
The Stellaris LM3S9B96 is an ARM Cortex-M3-based microcontroller with 256-KB flash memory,
80-MHz operation, Ethernet, USB, EPI, SAFERTOS™ in ROM, and a wide range of peripherals.
See the LM3S9B96 Microcontroller Data Sheet (order number DS-LM3S9B96) for complete
microcontroller details.
The LM3S9B96 microcontroller is factory-programmed with a quickstart demo program. The
quickstart program resides in on-chip flash memory and runs each time power is applied, unless
the quickstart has been replaced with a user program.
Jumpers and GPIO Assignments
Each peripheral circuit on the development board is interfaced to the LM3S9B96 microcontroller
through a 0.1” pitch jumper/shunt. Figure 2-1 on page 14 shows the fact ory default positions of the
jumpers. The jumpers must be in these positions for the quickstart demo program to function
correctly.
The development board offers capabilities that the LM3S9B96 cannot support simultaneously due
to pin count and GPIO multiplexing limitations. For example, as configured, the board does not
support SDRAM and I
jumpers associated with I
Table 2-1 lists all features and peripherals that are disconnected in the factor y de fa ult
configuration. Using these peripherals requires that other peripherals be disconnected.
Appendix D, “Stellaris® LM3S9B96 Development Board Microcontroller GPIO Assignments,” on
page 37 lists alternative jumper configurations used in conjunction with some of the
StellarisWare™ example applications for this board.
Table 2-1. Board Features and Peripherals that are Disconnected in Factory Default
Configuration
PeripheralJumpers
2
I
S Receive (Audio Input)JP44, 45, 47, 49
Controller Area Network (CAN) JP14, 15
Ethernet Yellow Status LED (LED2)JP2
Analog 3.0V Reference JP33
See Appendix D, “Stellaris® LM3S9B96 Development Board Microcontroller GPIO Assignments,”
on page 37, for a complete list of GPIO assignments. The table lists all default and alternate
2
S receive (microphone or line input) functions at the sa me ti me . The
2
S receive are omitted in the default configuration.
September 5, 201013
assignments that are supported by the 0.1” jumpers and PCB routing. The LM3S9B96 has
additional internal multiplexing that enables additional configurations which may require discrete
wiring between peripherals and GPIO pins.
The ICDI section of the board has a GND-GND jumper that serves no function other than to
provide a convenient place to ‘park’ a spare jumper. This jumper may be reused as required.
Figure 2-1.Factory Default Jumper Settings
Clocking
The development board uses a 16.0-MHz (Y2) crystal to complete the LM3S9B96
microcontroller's main internal clock circuit. An internal PLL, configured in software, multiples this
clock to higher frequencies for core and peripheral timing.
A 25.0-MHz (Y1) crystal provides an accurate timebase for the Ethernet PHY.
14September 5, 2010
Reset
The RESETn signal into the LM3S9B96 microcontroller connects to the reset switch (SW2) and to
the ICDI circuit for a debugger-controlled reset.
External reset is asserted (active low) under any one of the three following conditions:
Power-on reset (filtered by an R-C network)
Reset push switch SW2 held down
By the ICDI circuit (U12 FT2232, U13D 74LVC125A) when instructed by the debugger (this
capability is optional, and may not be supported by all debuggers)
The LCD module has special Reset timing requirement s requiring a ded icated control line from the
microcontroller.
Power Supplies
The development board requires a regulated 5.0 V power source. Jumpers JP34-36 select the
power source, with the default source being the ICDI USB connector . Only one +5 V source should
be selected at any time to avoid conflict between the power sources.
When using USB in Host mode, the power source should be set to either ICDI or to EXT if a +5 V
power supply (not included in the kit) is available.
Stellaris® LM3S9B96 Development Kit User’s Manual
USB
The development board has two main power rails. A +3.3 V supply powers the microcontroller and
most other circuitry. +5 V is used by the OTG USB port and In-circuit Debug Interface (ICDI) USB
controller. A low drop-out (LDO) regulator (U5) converts the +5 V power rail to +3.3 V. Both rails
are routed to test loops for easy access.
The LM3S9B96’s full-speed USB controller supports On-the-Go, Host, and Device configurations.
See Table 2-2 for USB-related signals. The 5-pin microAB OTG connector supports all three
interfaces in conjunction with the cables included in the kit.
The USB port has additional ESD protection diode arrays (D1, D2,D5) for up to 15 kV of ESD
protection.
Table 2-2. USB-Related Signals
Microcontroller PinBoard FunctionJumper Name
Pin 70 USB0DMUSB Data-Pin 71 USB0DPUSB Data+Pin 73 USB0RBIASUSB bias resistorPin 66 USB0IDOTG ID signal (input to microcontroller)OTG ID
Pin 67 USB0VBUSVbus Level monitoring+VBUS
Pin 34 USB0EPEHost power enable (active high)EPEN
Pin 35 USB0PFLTHost power fault signal (active low)PFLT
U6, a fault-protected switch, controls and monitors power to the USB host port. USB0EPEN, the
control signal from the microcontroller , has a pull-down resistor to en sure host-p ort power rema ins
off during reset. The power switch will immediately cut power if the attached USB device draws
September 5, 201015
more than 1 Amp, or if the switches’ thermal limits are exceeded by a device drawing more than
500 mA. USB0PFLT indicates the over-current status back to the microcontroller.
The development board can be either a bus-po wered USB device or self-powered USB device
depending on the power-supply configuration jumpers.
When using the development board in USB-host mode, power to the EVB should be supplied by
the In-circuit Debugger (ICDI) USB cable or by a +5 V source connected to the DC power jack.
Note that the LM3S9B96’s USB capabilities are completely independent from the In-Circuit Debug
Interface USB functionality.
Debugging
Stellaris microcontrollers support programming and debugging using either JTAG or SWD. JTAG
uses the TCK, TMS, TDI, and TDO signals. SWD requires fewer signals (SWCLK, SWDIO, and,
optionally, SWO for trace). The debugger determines which debug protocol is used.
Debugging Modes
The LM3S9B96 development board supports a range of hardware debugging configurations.
Table 2-3 summarizes these configurations.
Table 2-3. Hardware Debugging Configurations
ModeDebug FunctionUseSelected by...
1 Internal ICDI Debug on-board LM3S9B96
2 ICDI out to JTAG/ SWD
header
3 In from JT AG/SWD header For users who prefer an
Debug In Considerations
Debug Mode 3 supports board debugging using an external debug interface such as a Segger
J-Link or Keil ULINK. Most debuggers use Pin 1 of the Debug connec to r to se nse the target
voltage and, in some cases, power the output logic circuit. Installing the VDD/PIN1 jumper will
apply 3.3 V power to this pin in order to support external debuggers.
Debug USB Overview
An FT2232 device from Future Technology Devices International Ltd implements USB-to-serial
conversion. The FT2232 is factory-configured to implement a JTAG/SWD port (synchronous
serial) on channel A and a Virtual COM Port (VCP) on channel B. This feature allows two
simultaneous communications links between the host computer an d the target device using a
single USB cable. Separate Windows drivers for each func tion are provided on the Docume ntation
and Software CD.
microcontroller over Debug
USB interface.
The development board is
used as a USB to SWD/
JTAG interface to an
external target.
external debug interface
(ULINK, JLINK, etc.) with the
development board.
Default mode
Remove jumpers on TCk,
TMS, TDI, TDO, and PIN1
Connecting an external
debugger to the JTAG/SWD
header
The In-Circuit Debug Interface USB capabilities are completely independent from the LM3S9B96’s
on-chip USB functionality.
16September 5, 2010
A small serial EEPROM holds the FT2232 configuration data. The EEPROM is not accessible by
the LM3S9B96 microcontroller. For full details on FT2232 operation, go to www.ftdichip.com.
USB to JTAG/SWD
The FT2232 USB device performs JT AG/SWD serial operations under th e control of the debugger.
A simple logic circuit multiplexes SWD and JTAG functions and, when working in SWD mode,
provides direction control for the bidirectional data line.
Virtual COM Port
The Virtual COM Port (VCP) allows Windows applications (such as HyperTe rm in al) to
communicate with UART0 on the LM3S9B96 over USB. Once the FT2232 VCP driver is in stalled,
Windows assigns a COM port number to the VCP channel. Table 2-4 shows the debug-related
signals.
Table 2-4. Debug-Related Signals
Microcontroller PinBoard FunctionJumper Name
Pin 77 TDO/SWOJT AG data out or trace data outTDO
Pin 78 TDIJTAG data inTDI
Pin 79 TMS/SWDIOJT AG TMS or SWD data in/outTMS
Stellaris® LM3S9B96 Development Kit User’s Manual
Pin 80 TCK/SWCLKJTAG Clock or SWD clockTCK
Pin 26 PA0/U0RXVirtual Com port data to LM3S9B96VCPRX
Pin 27 PA1/U0TXVirtual Com port data from LM3S9B96VCPTX
Pin 64 RSTnSystem ResetRSTn
Serial Wire Out (SWO)
The development board supports the Cortex-M3 Serial-Wire Output (SWO) trace capabilities.
Under debugger control, on-board logic can route the SWO datastream to the VCP transmit
channel. The debugger software can then decode and interpret the trace information received
from the Virtual Com Port. The normal VCP connection to UART0 is interrupted when using SWO.
Not all debuggers support SWO.
See the Stellaris LM3S9B96 Microcontroller Data Sheet for additional information on the Trace
Port Interface Unit (TPIU).
Color QVGA LCD Touch Panel
The development board features a TFT Liquid Crystal graphics display with 320 x 240 pixel
resolution. The display is protected during shipping by a thin, protective plastic film which should
be removed before use.
Features
Features of the LCD module include:
Kitronix K350QVG-V1-F display
320 x RGB x 240 dots
3.5” 262 K colors
September 5, 201017
Wide temperature range
White LED backlight
Integrated RAM
Resist ive to uc h panel
Control Interface
The Color LCD module has a built-in controller IC with a multi-mode parallel interface. The
development board uses an 8-bit 8080 type interface with GPIO Port D providing the data bus.
Table 2-4 shows the LCD-related signals.
The white LED backlight must be powered for the display to be clearly visible. U7 (FAN5331B)
implements a 20 mA constant-current LED power source to the backlight. The backlight is not
normally controlled by the microcontroller, however, the control signal is available on a header. A
jumper may be installed to disable the backlight by connecting it to GND. Alternatively, a wire may
be used to control this signal from a spare microcontroller GPIO line.
Because the FAN5331B operates in a constant current mode, its output voltage will jump up if the
LCD should become disconnected. To prevent over-voltage failure of the IC or diode D3, a zener
(D4) clamps the voltage. The current will limit to 20 mA, but the total board current will be higher
than when the LCD panel is connected. To avoid over-heating the backlighting circuit, install the
BLON jumper to completely shut-down the backlighting circuit.
Power
The LCD module has internal bias voltage generators and requires only a single 3.3 V dc supply.
Resistive Touch Panel
The 4-wire resistive touch panel interfaces directly to the microcontroller, using 2 ADC channe ls
and 2 GPIO signals. See the StellarisW are™ source code for additio nal information on touch panel
implementation.
18September 5, 2010
I2S Audio
The LM3S9B96 development board has advanced audio capabilities using an I2S-connected
Audio TLV320AIC23 CODEC. The factory default configuration has Audio output (Line Out and/or
Headphone output) enabled. Four additional I
and/or Microphone). All four audio interfaces are through 1/8” (3.5mm) stereo jacks. Table 2-6
shows the I
Table 2-6. I
Stellaris® LM3S9B96 Development Kit User’s Manual
2
S signals are required for Audio input (Line Input
2
S audio-related signals.
2
S Audio-Related Signals
Microcontroller PinBoard FunctionJumper Name
I2C0SDACODEC Configuration DataSDA
I2C0SCLCODEC Configuration ClockSCL
I2STXSDAudio Out Serial DataTXSD
I2STXWSAudio Out Framing signalTXWS
I2STXSCKAudio Out Bit ClockBCLK
I2STXMCLKAudio Out System ClockMCLK
I2SRXSDAudio In Serial DataRXSD
I2SRXWSAudio In Framing signalRXWS
I2SRXSCKAudio In Bit ClockBCLK
I2SRXMCLKAudio In System ClockMCLK
a
b
b
b
b
a. Shares GPIO line with Analog voltage reference. Jumper installed by default.
b. Shares GPIO line with LCD data bus – Port D. Jumper omitted by default.
The Audio CODEC has a number of control registers which are configured using the I
signals. CODEC settings can only be written, but not read, using I
example applications for programming information and the TLV320AIX23B data sheet for
complete register details.
The Headphone output can be connected dir ectly to any stand ard headphones. The Lin e Output is
suitable for connection to an external amplifier, including PC desktop speaker sets.
User Switch and LED
The development board provides a user push-switch and LED (see Table 2-7).
Table 2-7. Navigation Switch-Related Signals
Microcontroller PinBoard FunctionJumper Name
PJ7User SwitchSWITCH
PF3User LEDLED
a. Shared with Ethernet Jack Yellow LED. This jumper is installed by default.
2
2
C. See the StellarisW are™
a
C bus
September 5, 201019
20September 5, 2010
CHAPTER 3
Stellaris® LM3S9B96 Development Board External
Peripheral Interface (EPI)
The External Peripheral Interface (EPI) is a high-speed 8/16/32- bit parallel bus for connecting
external peripherals or memory without glue logic. Supported modes include SDRAM, SRAM, and
Flash memories, as well as Host-bus and FIFO mo d es.
The LM3S9B96 development kit includes an 8 MB SDRAM board in addition to an EPI break-out
board. Other EPI expansion boards may be availabl e.
SDRAM Expansion Board
The SDRAM board provides 8 MB of memory (4M x 16) which, once configured, becomes part of
the LM3S9B96’s memory map at either 0x6000 .0 0 00 or 0x80 00 .0 00 0 . Th e SDRAM inte r face
multiplexes DQ00..14 and AD/BA0..14 without requiring external latches or buffers. Of the 32 EPI
signals, only 24 are used in SDRAM mode, with the remaining signals used for non-EPI functions
on the board.
Flash and SRAM Memory Expansion Board
The optional Flash and SRAM Memory Expansion Board (DK-LM3S9B9 6-FS8) is a plug-in fo r th e
DK-LM3S9B96 development board. This expansion board works with the External Peripheral
Interface (EPI) of the Stellari s microcontroller and provides Flash memory, SRAM, and an
improved performance LCD interface.
For more information on the Flash and SRAM Memory Expansion Board (sold separately), see
Appendix E, “Stellaris® LM3S9B96 Flash and SRAM Memory Expansion Board,” on page 41.
FPGA Expansion Board
The FPGA Expansion Board (DK-LM3S9B96-FPGA) is an optional expansion board which
connects directly to the External Peripheral Interface (EPI) port of the Stellaris DK-LM3S9B96
development board to demonstrate the machine-to-machine (M2M), high-bandwidth, parallel
interface capability of the Stellaris microcontroller. Right out of the box, users are able to control
and display the FPGA expansion board’s video on the DK- LM3S9B96 development bo ard’s large,
3.5” touchscreen display.
For more information on the FPGA Expansion Board (sold separately), see Append ix F , “S tellaris®
LM3S9B96 FPGA Expansion Board,” on page 49.
EM2 Expansion Board
The EM2 Expansion Board (DK-LM3S9B96-EM2) is an optional expansion boar d wh ich connects
directly to the External Peripheral Interface (EPI) port of the Stellaris DK-LM3S9B96 development
board. The EM2 Expansion Board provides a transition between the Stellaris External Peripheral
Interface (EPI) connector and the RF Evaluation Module (EM) connector. The DK-LM3S9B96-EM2
enables wireless application development using Low Power RF and RF ID evaluation modules on
the Stellaris DK-LM3S9B96 platform.
For more information on the EM2 Expansion Board (sold separately), see Appendix G, “Stellaris®
LM3S9B96 EM2 Expansion Board,” on page 69.
September 5, 201021
22September 5, 2010
LM3S9B96 Dev Board
Target
Board
Stellaris
MCU
USB
to
JTAG/
SWD
PC with IDE/
debugger
Stellaris
MCU
JT AG or SW D c onnec t s to t he
ext ernal m ic roc ont roller
Rem ov e jum pers to us e I C D I Out F eat ure
`
TCK
TMS
TDI
TDO
Target
Cable
VDD
+3.3 V
CHAPTER 4
Using the In-Circuit Debugger Interface
The Stellaris® LM3S9B96 Development Kit can operate as an In-Circuit Debugger Interface
(ICDI). ICDI acts as a USB to the JTAG/SWD adaptor, allowing debugging of any external target
board that uses a S tellaris mi crocontroller. See “Debugging Modes” on page 16 for a description of
how to enter ICDI Out mode.
Figure 4-1.ICD Interface Out Mode
The debug interface operates in either serial-wire debug (SWD) or JTAG mode, depending on the
configuration in the debugger IDE.
The IDE/debugger does not distinguish between the on-board Stellaris microcontroller and an
external Stellaris microcontroller. The only requirement is that the correct Stellaris device is
selected in the project configuration.
The Stellaris target board should have a 2x10 0.1” pin header with signals as indicated in
Table C-1 on page 35. This applies to both an external Stellaris microcontroller target (Debug
Output mode) and to external JTAG/SWD debuggers (Debug Input mode).
ICDI does not control RST (device reset) or TRST (test reset) signals. Both reset functions are
implemented as commands over JTAG/SWD, so these signals are usually not necessary.
September 5, 201023
24September 5, 2010
APPENDIX A
Stellaris® LM3S9B96 Development Board
Schematics
This section contains the schematics for the DK-LM3S9B96 development board.
Micro, EPI connector, USB, and Ethernet on page 26
LC D CAN, Ser i al Me m ory, and User I/O on page 2 7
Power Supplies on page 28
2
I
S Audio Expansion Board on page 29
EPI and SDRAM Expansion Boards on page 30
In-circuit Debug Interface (ICDI) on page 31
September 5, 201025
1
1
2
2
3
3
4
4
5
5
6
6
DD
CC
BB
AA
Document Number:
RevSheetDate:
of
4/23/200916
Drawing Title:
Page Title:
Size
LM3S9B96 Development Board
Micro, EPI connector, USB and Ethernet
LM3S9B96 Development Board
In-circuit Debug Interface (ICDI)
B
A
DB-LM3S9B96
GND
18
GND
25
GND
34
ADBUS0
24
ADBUS1
23
ADBUS2
22
ADBUS3
21
ADBUS4
20
ADBUS5
19
ADBUS6
17
ADBUS7
16
ACBUS0
15
ACBUS1
13
ACBUS2
12
ACBUS3
11
BDBUS0
40
BDBUS1
39
BDBUS2
38
BDBUS3
37
BDBUS4
36
BDBUS5
35
BDBUS6
33
BDBUS7
32
BCBUS0
30
BCBUS1
29
BCBUS2
28
BCBUS3
27
SI/WUA
10
SI/WUB
26
GND
9
AGND
45
VCC
3
VCC
42
VCCIOA
14
VCCIOB
31
AVCC
46
PWREN#
41
XTOUT
44
XTIN
43
EECS
48
EESK
1
EEDATA
2
TEST
47
RESET#
4
RSTOUT#
5
3V3OUT
6
USBDM
8
USBDP
7
U12
FT2232D
+3.3V
DBG+5V
R41 27
R42 27
+3.3V
+3.3V
DBG_JTAG_EN
R39
10K
R40
1.5K
R44
1.5K
R45
330
+5V
+5V
+5V+5V
FT_TCK
FT_TDI/DI
FT_TDO/DO
FT_TMS/OUTEN
0.1UF
C71
0.1UF
C72
0.1UF
C73
0.1UF
C74
0.1UF
C75
0.1UF
C70
USB Device Controller
Channel A : JTAG / SW Debug
Channel B : Virtual Com Port
5V D- D+ ID G
123
475
6
J13
54819-0572
FT_SRSTN
Debugger USB Interface
R43
USBSH
CS
1
SK
2
DI
3
DO
4
GND
5
ORG
6
NC
7
VCC
8
1K 64X16
U11
CAT93C46
12
Y3
6.00MHz
27PF
C68
27PF
C69
SWO_EN
0.01UF
C67
23
1
U14A
SN74LVC125A
56
4
U13B
SN74LVC125A
98
10
U13C
SN74LVC125A
1211
13
U14D
SN74LVC125A
23
1
U13A
SN74LVC125A
56
4
U14B
SN74LVC125A
98
10
U14C
SN74LVC125A
23
1
U15A
SN74LVC126A
56
4
U15B
SN74LVC126A
98
10
U15C
SN74LVC126A
1211
13
U15D
SN74LVC126A
VCP_TX_SWO
DBGENn
1211
13
U13D
SN74LVC125A
12
34
56
78
910
1112
1314
1516
1718
1920
J14
2X10 HDR-SHRD
+3.3V
TDI
TCK
R46
27
TMS_SWDIO
SRSTN
TDO_SWO
VCP_TX
R47
27
R48
27
R49
27
R50
27
PIN1
JP57
TCK
JP50
PC0/TCK
PC1/TMS
PC2/TDI
PC3/TDO
TMS
JP51
TDI
JP52
TDO
JP53
TCK
TDI
TMS_SWDIO
TDO_SWO
TDI
TMS_SWDIO
TCK
TDO_SWO
SRSTN
R38
10K
+3.3v
RESETn
RSTn
JP54
SRSTN
PA1/U0TX
VCPTX
JP55
PA0/U0RX
VCPRX
JP56
VCP_RX
VCP_RX
VCP_TX
JTAG/SWD In/Out
147
VCC
GND
U14E
SN74LVC125A
147
VCC
GND
U13E
SN74LVC125A
147
VCC
GND
U15E
SN74LVC126A
+3.3V+3.3V+3.3V
0.1UF
C80
+3.3V
R51
10K
+3.3V
R52
10K
R53
10K
Indicates factory-default jumper position.
Schematic page 6
32September 5, 2010
APPENDIX B
Stellaris® LM3S9B96 Development Board
Component Locations
This appendix contains details on compo nent locations, including:
Component placement plot for top (Figure B-1)
September 5, 201033
Figure B-1. Component Placement Plot for Top
34September 5, 2010
Center Positive (+)
APPENDIX C
Stellaris® LM3S9B96 Development Board
Connection Details
This appendix contains the following sections:
DC Power Jack (see page 35)
ARM Target Pinout (see page 35)
DC Power Jack
The EVB provides a DC power jack for connecting an external +5 V regulated (+/-5%) power
source.
The socket is 5.5 mm dia with a 2.1 mm pin.
ARM Target Pinout
In ICDI input and output mode, the Stellaris® LM3S9B96 Development Kit supports ARM’s
standard 20-pin JTAG/SWD configuration. The same pin configuration can be used for debugging
over serial-wire debug (SWD) and JTAG interfaces.
NumberDescriptionDefault FunctionDefault UseAlt. FunctionAlternate Use
10PD0PD0LCD Data 0I2SRXSCKI2S Audio In
11PD1PD1LCD Data 1I2S0RXWSI2S Audio In
12PD2PD2LCD Data 2EPI0S20EPI Breakout
13PD3PD3LCD Data 3EPI0S21EPI Breakout
97PD4PD4LCD Data 4I2SRXSDI2S Audio In
98PD5PD5LCD Data 5I2SRXMCLKI2S Audio In
99PD6PD6LCD Data 6
Stellaris® LM3S9B96 Flash and SRAM Memory
Expansion Board
This document describes the Flash and SRAM memory expansion board
(DK-LM3S9B96-EXP-FS8) plug-in for the DK-LM3S9B96 development board. This expansion
board works with the External Peripheral Interface (EPI) port of the Stellaris microcontroller and
provides Flash memory, SRAM, and an improved performance LCD interface.
Figure E-1. Flash and SRAM Memory Expansion Board
Features
The DK-LM3S9B96-EXP-FS8 memory expansion board has the following features:
8 Megabytes of Flash memory
1 Megabyte of SRAM
Memory-mapped LCD I/F for improved LCD performance
1 kilobit of I
Power LED indicator
2
C memory for storing configuration data
Installation
To install the expansion board on the DK-LM3S9B96 development board, do the following:
1. Remove the DK-LM3S9B96-EXP-FS8 memory expansion board from the antistatic bag.
2. On the DK-LM3S9B96 board, remove any installed board on EPI connector J2.
September 5, 201041
3. On the DK-LM3S9B96 board remove the shunt jumpers on JP16-JP31 and the JP39 headers
Remove board
Remove jumpers
as shown in Figure E-1 on page 41.
Figure E-2. Removing EPI Board from DK-LM3S9B96 Development Board
4. Install the two snap-in nylon standoffs on mounting holes above the EPI connector J2.
5. Place the expansion board on top of the DK-LM3S9B96 board a nd align the st andof fs, the EPI
connector, and the 2x17 J2 header.
6. Press firmly downward until the board snaps in, then verify that the board is firmly seated on
the EPI connector, the 2x17 header, and the standoffs.
7. When powering up the board, verify that the power indicator LED D1 is lit.
42September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
MA[7:0]
MAD[7:0]
EPI[27:8]
EPI[7:0]
OEn
WRn
EPI30
EPI
Connector
FLASH/ SRAM/LCD I F Boa r d
DQ
L
MA[27:8]
ALE
MA27
EPI29
EPI28
MAD[7:0]
A
D
SRAM
WE
OE
1MB
A
D
FLASH
WE
CS
OE
8MB
LCD
Connector
LCD Control
LCD
DECODE
LCD Data
CE2
MA27
MA26
CE1
Hardware Description
The Flash and SRAM memory expansion board is designed for use with the Stellaris EPI module
configured in Host Bus 8 address/data multiplexed mode. This mode requires the use of an
external 8-bit latch for storing the lower 8 address lines A[7:0] transmitted durin g the address
phase of an EPI transfer. This latch can be seen on the expansion board block diagram shown in
Figure E-3.
Figure E-3. Flash/SRAM/LCD IF Expansion Board Block Diagram
Functional Description
The Flash and SRAM memory expansion board schematics are described in this section. The first
Flash/SRAM (Schematic 1 on page 47)
September 5, 201043
page of the schematics shows the memory devices and address latch part of the design. The
second page shows the LCD I/F and regulator.
Page 1 of the schematics shows the EPI connector, address latch, and memory devices.
EPI Connector
The EPI connector J1 is a 50-pin receptacle with 0.5 mm pitch that plugs into the EPI he ad e r on
the DK-LM3S9B96 board. The 32 EPI signals and the 2 I
provided on this connector . It also provides 5 V for the on-board DC regulator. Note that not all EPI
signals are used in this design.
2
C0 signals from the LM3S9B96 are
8-bit Latch
This 8-bit latch is used to store the lower 8-bits of the address, which are transmitted during the
address phase of an EPI transfer. The EPI must be configured in Host bus 8 mode 0 mode (HB8
ADMUX), with EPI30 configured as an Address Latch Enable (ALE) signal to control this latch.
Flash Memory
The Flash memory used is a 64 Mbit, 90-nsec Spansion S29GL064N90TFI040. This 8/16 bit
memory is used in 8-bit mode. Note that MA27 is used as a chip select signal for this memory.
SRAM
The SRAM used is an 8 Mbit, 45 nsec Cypress Semiconductor CY62158EV30LL-45ZSX, which is
an 8-bit memory. Note that MA27 and MA26 are used as chip selects for this memory.
2
I
C Memory
2
This I
C serial memory is used for storing configuration data. This is a 1 kilobit On-Semiconductor
memory.
LCD I/F, Power (Schematic 2 on page 48)
Page 2 of the schematics shows the LCD_DECODE CPLD, LCD interface connector, and the
3.3 V regulator.
LCD_DECODE CPLD
The LCD DECODE CPLD provides address latch and decode for the LCD interface. The LCD
Command and Data registers are mapped on the EPI memory space to streamline access to
these registers. The LCD panel control signals L_RDn, L_RWn, and L_DC and the L_D bus are
controlled by decode logic on the CPLD with timing derived from EPI signals and do not require
direct control from the microcontroller . The LCD latch register is provided to control the XN and YN
signals used for the touchscreen and also the reset signal to the LCD.
The LCD backlight signal L_BL is controlled by the Stellaris GPIO PE2 (MA[24]). PE2 can be
programmed as a GPIO for ON/OFF control of the LCD. A second option is to configure PE2 for
use as CCP2 or CCP4 with a PWM output for brightness control.
The TP1-TP4 testpoints connect to the CPLD JTAG signals and, along with TP5 and TP6, provide
an interface for test and programming of the CPLD.
LCD Interface Connector
The LCD Interface Connector J2 is a 2x17 socket that connects to headers JP16-JP31 and JP39
on the DK-LM3S9B96. All signals previously driven to the LCD from the Stellaris MCU are
replaced by equivalent signals driven from the LCD_DECODE CPLD.
DC Regulator
DC regulator U4 receives 5 V from the EPI connector and provides 3.3 V for the board. LED D1
provides a power indicator and lights when the regulator is providing power to the board.
44September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
Memory Map
The DK-LM3S9B96-EXP-FS8 expansion boa rd memo ry ma p is shown in Table E-1 and T a ble E-2
shows the LCD Latch register.
Table E-1. Flash and SRAM Memory Expansion Board Memory Map
a. For reads to the LCD Command and Data Port registers, the corresponding LCD Port Read Start register must be read first,
followed by a 500 nsec delay before reading this register.
11000
11001
11010
11011
11110
11111
Table E-2. LCD Latch Register
LCD latch setR/W0x6C00.0000
LCD latch clearR/W0x6C00.0001
LCD command portRa/W
LCD data portRa/W0x6C00.0003
LCD command port read startR0x6C00.0006
LCD data port read startR0x6C00.0007
0x6C00.0002
76543210
ReservedRSTYNXN
00000R/WR/WR/W
The LCD Latch register is implemented as a set/clear register. To set a bit, the corresponding bit
must be set when writing to the LCD Latch Set register. To clear a bit, the corresponding bit must
be set when writing to the LCD Latch Clear register.
XNWhen clear, the L_XN signal is set to clear. When set, the L_XN signal is tri-stated. This
signal is used for the X- input to the touchscreen.
YNWhen clear, the L_YN signal is set to clear. When set, the L_YN signal is tri-stated. This
signal is used for the Y- input to the touchscreen.
RSTWhen clear, the L_RSTN signal is set to clear. When set, the L_RSTN signal is reset. This
signal is used to reset the LCD panel.
September 5, 201045
Component Locations
TopBottom
Figure E-4 shows the details of the component locations.
Figure E-4. Component Placement Plot for Top and Bottom
Schematics
This section shows the schematics for the DK-LM3S9B96-EXP-FS8 memory expansion board:
Flash, SRAM on page 47
LCD Interface on page 48
Changed J2 to top entry, moved to bottom. Added R9-R11.
A0
25
DQ0
29
A1
24
A2
23
A3
22
A4
21
A5
20
A6
19
A7
18
A8
8
A9
7
A10
6
A11
5
A12
4
DQ1
31
DQ2
33
DQ3
35
DQ4
38
DQ5
40
DQ6
42
DQ7
44
A13
3
A14
2
A15
1
A16
48
A17
17
RDY
15
WE
11
OE
28
CE
26
VSS
27
VSS
46
VCC
37
64Mbit
BYTE
47
DQ8
30
DQ9
32
DQ10
34
DQ11
36
DQ12
39
DQ13
41
DQ14
43
DQ15/A-1
45
RP
12
A18
16
A19
9
A20
10
A21
13
VPP/WP
14
U1
S29GL064N
Flash, SRAM
1
1
2
2
3
3
4
4
5
5
6
6
DD
CC
BB
AA
Document Number:Rev
Sheet
Date:
of
7/18/2009
22
B
Drawing Title:
Page Title:
Size
B
LCD Interface
FLASH / SRAM / LCD IF board for DK-LM3S9B96
0001
L_YN
L_XN
L_D4
L_D1
L_D0
L_D3
L_D6
L_D7
L_D2
L_D5
L_RSTn
L_BL
L_D0
L_D1
L_D2
L_D3
L_D4
L_D5
L_D6
L_D7
3.3V
C2
0.1uF
L_RDn
MOEn
L_D[7..0]
MAD[7..0]
MAD[7..0]
MA[27..0]
MA[27..0]
3.3V
C6
4.7uF
C8
4.7uF
5V
R7
330
PWR
D1
GREEN_LED
R810K
C9
0.1uF
F_RSTn
F_RSTn
3.3V
L_DC
A0/GOE0
44
A1
45
A2
46
A3
47
A4
48
A5
2
A7
4
A6
3
A8
7
A9
8
A10
9
B0
20
B1
21
B2
22
B3
23
B4
24
B5
26
B6
27
B7
28
B8
31
B9
32
B10
33
B11
34
B12
38
B13
39
B14
40
A12
14
A13
15
A14
16
A15
17
TDI
1
TCK
11
TMS
25
TDO
35
GND01
5
GND1
13
GND11
29
GND2
37
VCC01
6
VCC1
12
VCC11
30
VCC2
36
A11
10
CLK2/IN2
19
CLK1/IN1
18
B15/GOE1
41
CLK3/IN3
42
CLK0/IN0
43
U6
LC4032V
MAD0
MAD1
MAD2
MAD3
MAD4
MAD5
MAD6
MAD7
MA24
MA25
MA26
MA27
ALE
L_WRn
C3
0.1uFC70.1uF
C13
0.1uF
CPLD_TCK
CPLD_TMS
CPLD_TDI
CPLD_TDO
TP1
TP2
TP3
TP4
TP5
TP6
VIN1VOUT
5
SHDN
3
GND2NR
4
U4
TPS73033
MWEn
LCD_DECODE CPLD
L_WRn
L_YP
L_XP
LCD I/F
L_DC
L_BL
L_YN
L_XN
L_D0
L_D1
L_D2
L_D3
L_D4
L_D5
L_D6
L_D7
L_RSTn
L_RDn
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
1
3
5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
J2
SMT Socket 2x17
R910K
R1010K
R1110K
LCD Interface
APPENDIX F
Stellaris® LM3S9B96 FPGA Expansion Board
This chapter describes the FPGA expansion board for the DK-LM3S9B96 development bo ard.The
FPGA expansion board provides a quick start platform to evaluate the capabilities of the Stellaris
External Peripheral Interface (EPI) using the highly integrated DK-LM3S9B96 development
platform.
This combination adds full-screen motion video to the powerful, easy-to-use StellarisWare® GUI
tools. Figure F-1 shows a photo of the FPGA expansion board.
Figure F-1.FPGA Expansion Board
Features
The LM3S9B96 FPGA memory expansion board has the following features:
Xilinx Spartan 3E FPGA with 100k system gates
1/13 " C MO S VGA (6 40 x 480) Colo r Ca me r a Mo du le
1 MB of asynchronous 10 nsec SRAM for graphics/video buffers
Standard 1 x 6 and 2 x 5 JTAG headers for FPGA programming
1 kilobit of I
8 FPGA test pads provide 5 inputs and 3 I/Os
All necessary power regulation
The default FPGA image adds the following features:
EPI operation in GPM D16-A12 mode at 50 MHz, up to 100 MB/s
Graphical on-screen-display (OSD) overlaid on moving QVGA video
September 5, 201049
2
C memory for storing configuration data
Widget-based touchscreen user interface
Screen capture to SDCard or USB stick in Windows bitmap (BMP) format
Brightness, saturation, tint/hue, and sharpness picture controls
Mirror/Flip/Normal Picture controls
Installation
To install the expansion board on the DK-LM3S9B96 development board, do the following:
1. Remove the LM3S9B96 FPGA memory expansion board from the antistatic bag.
2. On the DK-LM3S9B96 board, remove any installed board on EPI connector J2.
3. On the DK-LM3S9B96 board, remove the shunt jumpers on JP16-JP31 and the JP39 header s
as shown in Figure F-1 on page 49.
4. Place the expansion board on top of the DK-LM3S9B96 b oard and press firmly d ownward until
the board snaps in.
5. Connect the the male EPI expansion connector on the bottom side of the FPGA expansion
board to the female EPI expansion connector on the DK-LM3S9B96 development board (J2).
The LCD header pins should fit through the holes on the PCB.
6. Use the included jumper wire to provide 5 V power to J5 from any of the three upper pins
immediately below and to the right of the EXT+5V connector on the development board.
7. When powering up the board, verify that the power indicator LED D1 is lit.
50September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
Remove board
Remove JP16-31
5 V Power
Remove POT/PB4
jumpers
jumper
Figure F-2.Removing EPI Board from DK-LM3S9B96 Development Board
September 5, 201051
Hardware Description
The FPGA expansion board is designed for use with the Stellaris EPI module. Figure F-3 shows a
simplified system block diagram. Components of the default FPGA board are shown in half-tone
outline.
Figure F-3.FPGA Expansion Board Block Diagram
FPGA
The FPGA expansion board features a Xilinx Spartan 3e FPGA, which interfaces to the Stellaris®
microcontroller through its EPI port and acts as a crossbar to the rest of the peripherals.
Camera
The Omnivision OV7690 camera provides color VGA images at up to 30 frames per second to the
FPGA over an 8-bit wide parallel interface. It is configured by the Stellaris microcontroller via I
SRAM
The 1 MB, 8-bit wide, 10 ns SRAM is nominally used as a set of frame buffers. 16 bits of the 20-bit
address space are latched and multiplexed with its data. Access time may be dependent on the
previous address.
Configuration PROM
A Xilinx standard configuration PROM holds the default FPGA image and automatically uploads it
at power-on.
Configuration Pushbutton
To reload the configuration PROM image to the FPGA, press the configuration pushbutton. This
allows you to load a new image via JTAG without resetting the rest of the system.
2
C.
52September 5, 2010
Test Port
Eight uncommitted FPGA pins are brought to test pads. Five of the FPGA pins can only be used
as inputs. The remaining three FPGA pins can be used as inputs or outputs.
Camera Connector
The camera is hosted by the FPC Connector P1 located to the left of the FPGA. To insert or
remove the camera, first open the latch by grasping either side of the connector and gently lifting
straight up. With the latch open, the camera moves easily; do not force. The camera faces away
from the FPGA. Close the latch by pushing down on it gently before use.
Caution – Handle the camera carefully when inserting or removing it from the board. Never force
the camera into a different position, doing so could damage the camera.
5V Power Pin
J5 is used to provide 5-V power to the FPGA expansion board's regulators. This must be
connected for successful board operation. Connect the the male EPI expansion connector on the
bottom side of the FPGA expansion board to the female EPI expansion connector on the
DK-LM3S9B96 development board (J2). The LCD header pins should fit through the holes on the
PCB.
Stellaris® LM3S9B96 Development Kit User’s Manual
24-MHz Oscillator
The camera and the camera interface portion of the FPGA are clocked by a 24-MHz external
oscillator.
External Peripheral Interface (EPI) Module
The External Peripheral Interface (EPI) module provides a slave interface for use with the Stellaris
microcontroller’s EPI controller configured in general-purpose mode A12-D16. The dir ection of the
signal allocation is in relation to the FPGA (for example, a signal labeled In is an input to the
FPGA, a signal labelled Out is an output from the FPGA). See Table F-8 on page 63 for a list of the
EPI signals.
NOTE: Only 16-bit or 32-bit transfers are allowed for this interface.
Using the Widget Interface
This section provides information about writing your own graphics using the widget interface for
the FPGA expansion board.
Writing Your Own Stellaris Application
The Stellaris microcontroller communicates with the default FPGA image through a
memory-mapped interface. To get started, you must first configure the EPI port by doing the
following:
1. Configure the GPIO.
2. Configure the EPI port and map it into memory at 0xA000.0000.
Code Example F-1Configuring the EPI Port
EPIModeSet(EPI0_BASE, EPI_MODE_GENERAL);//General Purpose mode
EPIDividerSet(EPI0_BASE, 1);//Divide system clock by 2
September 5, 201053
EPIConfigGPModeSet(EPI0_BASE,
(EPI_GPMODE_DSIZE_16//16 Bit data
| EPI_GPMODE_ASIZE_12//12 Bit address
| EPI_GPMODE_WORD_ACCESS//Use Word Access Mode
| EPI_GPMODE_READWRITE //Use read and write strobe pins
| EPI_GPMODE_READ2CYCLE//Reads take two cycles
| EPI_GPMODE_CLKPIN//EPI outputs clock to peripheral
| EPI_GPMODE_RDYEN ),//Peripheral emits a ready signal
0,//Not using frame signal, so ignore
0);//Not using clock enable, so ignore
EPIAddressMapSet(EPI0_BASE,
EPI_ADDR_PER_SIZE_64KB//64kB memory space
| EPI_ADDR_PER_BASE_A);//EPI base address is 0xA0000000
Memory Map
The LM3S9B96 FPGA expansion board memory map is shown in Table F-1. The default Stellaris
code maps this into the 0xA000.0XXX memory space. Detailed descriptions for each register are
provide in “Register Descriptions” on page 55.
NOTE: Ten bits are used for addressing, but the EPI controller allocates a 12-bit address space.
The result is that 0x0A00.0000 is equivalent to 0x0A00.0400, 0x0A00.0800, and
0x0A00.0C00.
LGML050[15:0]LCD Graphics Memory Address LowR/W60
LGMH052[4:0]LCD Graphics Memory Address HighR/W60
LGMS054[11:0]LCD Graphics Memory StrideR/W60
MPNC056[9:0]Memory Port Number of ColumnsR/W60
MPR058[8:0]Memory Port Current RowR/W60
MPC05A[9:0]Memory Port Current ColumnR/W60
MPML05C[15:0]Memory Port Address LowR/W60
MPMH05E[4:0]Memory Port Address HighR/W60
MPMS060[11:0]Memory Port StrideR/W60
MPORT080[15:0]Memory PortR/W61
MEMWIN400[15:0]Memory WindowR/W61
Register Descriptions
This section provides the detailed register information for the FPGA expansion board.
Version Register
The Version register communicates the revision numbers of the PCB, the FPGA RTL, and the
Stellaris silicon. A dummy write of 0x0000 to this register determines if the Stellaris silicon is
revision C (or higher) and configures the EPI clocking circuit appropriately. This is required during
initialization for proper operation.
Table F-2. Version Register
15141312111098
PCB Board Version00RevC
RRRRRRRR
76543210
RTL Major VersionRTL Minor Version
RRRRRRRR
Bit NameDescription
VERSION: 0xA000.0000
PCB Board Version:
Revision level of the FPGA expansion board.
RevC:This bit is high if the FPGA believes it is communicating with Revision C of the
silicon (or higher). This bit is only valid after being initialized as described above.
RTL VersionRevision level of the code running in the FPGA expansion board.
September 5, 201055
System Control Register
The System Control register provides access to configuration bits for the video capture and
display system. It is implemented as a read-modify-write register and includes LCD and capture
modes.
Table F-3. System Control Register
15141312111098
0000000PCBrA
RRRRRRRR/W
76543210
SYSCTRL: 0xA000.0002
VCTESTVCQV
GA
R/WR/WR/WR/WR/WR/WR/WR/W
MPRI
VSCALECMKE
N
LGDENLVDENVCEN
Bit NameDescription
VCENVideo capture DMA enable. Enables video capture to memory. Disabling this bit
captures the remainder of the current frame, and then stops.
L VDENLCD Video DMA enable. Enables DMA from the video memory region to the LCD.
LGDENLCD Graphics DMA enable. Enables DMA from the graphics memory region to
the LCD.
CMKENChroma key enable.
VSCALEVideo scale control. Scales the video during output to the LCD. If set, the LCD
DMA engine skips every other pixel and every other row during LCD video DMA
output (Graphics DMA is not affected). As a result, the video object displays at ¼
its normal size.
MPRIMemory port row increment. If set to 0, any read or write to the memory port auto
increments the MPC register at the end of the transfer by 1. If MPC is at the last
column (MPNR-1), then it sets to 0 and the MPR increments by 1. If the end of the
row is reached, then it increments by columns. If set to 1, any read or write
increments by rows.
VCQVGAVideo Capture is QVGA/VGA. If set to 0, the video capture controller assumes
that the camera is configured for VGA capture. If set to 1, it assumes that the
camera is configured for QVGA. This only affects video capture; the camera’s I
2
C
and LCD settings must be reconfigured manually.
VCTESTVideo Capture Test. When set to 1, the incoming pixel stream is ignored and
replaced with a test pattern.
PCBrAPCB is Revision A. An early internal revision of the PCB had a different pin
configuration for the camera data port. Setting this bit to 1 provides backwards
compatibility.
56September 5, 2010
Interrupt Enable Register
The Interrupt Enable register masks or enables interrupts from the FPGA to the Stellaris
LM3S9B96 microcontroller. Masked interrupts will not assert the IRQ line, but they will still appear
in the Interrupt Status Register.
Table F-4. Interrupt Enable Register
15141312111098
00000000
RRRRRRRR
76543210
Stellaris® LM3S9B96 Development Kit User’s Manual
IRQEN: 0xA000.0004
00LRMIELTEIELTSIEVRMIE
RRR/WR/WR/WR/WR/WR/W
Bit NameDescription
VCFSIEVideo capture frame start interrupt enable.
VCFEIEVideo capture frame end interrupt enable.
VRMIEVideo capture row match interrupt enable.
LTSIELCD transfer start interrupt enable.
LTEIELCD transfer end interrupt enable.
LRMIELCD display row match interrupt enable.
Interrupt Status Register
The Interrupt Status register reports and clears interrupts from the camera and LCD systems.
An interrupt latches its corresponding bit high until cleared by writing a 1 to it.
Table F-5. Interrupt Status Register
15141312111098
00000000
VCFEIEVCFSIE
IRQST AT : 0xA000.0006
RRRRRRRR
76543210
00LRMILTEILTSIVRMIVCFEIVCFSI
RRR/WR/WR/WR/WR/WR/W
Bit NameDescription
VCFSIVideo capture frame start interrupt. Clear the interr upt by setting the
corresponding bit to 1. Setting the bit to 0 has no effect.
September 5, 201057
VCFEIVideo capture frame end interrupt. Clear the interrupt by setting the corresponding
VRMIVideo capture row match interrupt. Clear the interrupt by setting the
LTSILCD transfer start interrupt. Clear the interrupt by setting the corresponding bit to
LTEILCD transfer end interrupt. Set to 1 to clear the corresponding bit. Clear the
LRMILCD display row match interrupt. Clear the interrupt by setting the corresponding
Memory Page Register
The Memory Page register selects to memory page to access.
Test PadRegister
The Test Pad register is used to access the on-board test pads TP1-TP8, which are connected to
unused FPGA pins.
Table F-6. Test Pad Register
15141312111098
bit to 1. Setting the bit to 0 has no effect.
corresponding bit to 1. Setting the bit to 0 has no effect.
1. Setting the bit to 0 has no effect.
interrupt by setting the corresponding bit to 1. Setting the bit to 0 has no effect.
bit to 1. Setting the bit to 0 has no effect.
TXPAD: 0xA000.000A
00000000
RRRRRRRR
76543210
TP8TP7TP6TP5TP4TP3TP2TP1
RRRRRR/WR/WR/W
Bit NameDescription
TP1-TP3Te st Pins 1-3 . These are connected to FPGA I/O pins. Writing a 1 sets the
NOTE: The FPGA output driver for these signals is always enabled.
TP4-TP8Test Pins 4-8.These are connected to FPGA input pins. Writing these bits has no
LCD Control Register
The LCD Control register is implemented as a set/clear register and contains four bits for LCD
panel control. To set a bit, set the corresponding bit to 1 when writing to the LCD Control Set
register. To clear a bit, set the corresponding bit when writing to the LCD Control Clear register.
corresponding test pin output to 1. Writing a 0 sets the corresponding test pint
output to 0. Reading these bits returns the valu e at the corresponding test pin
input.
effect. Reading these bits returns the value at the corresponding test pin input.
58September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
Table F-7. LCD Control Register
LCDCTRL: 0xA000.0012
15141312111098
00000000
RRRRRRRR
76543210
0BLRST
RRRRR/2R/WR/WR/W
Bit NameDescription
XNLCD panel touchscreen X control. When set to 0, the LCD Xn signal is set to 0.
When set to 1, the LCD Xn signal is tri-stated.
YNLCD panel touchscreen Y control. When set to 0, the LCD Yn signal is set to 0.
When set to 1, the LCD Yn signal is tri-stated.
RST
BLLCD backlight control. When set to 0, the LCD panel backlight is turned off. When
LCD panel reset control. When set to 0, the LCD RSTn signal is set to 0. When
set to 1 the LCD RSTn signal is set to 1.
set to 1, the LCD panel backlight is turned on.
Chroma Key Register
The CHRMKEY register contains the RGB values to compare for graphics over lay operation.
During LCD screen updates, data from g raphics me mor y is co mpared with this register, if a match
occurs, the corrsponding frame video pixel is sent to the output instead.
Video Capture Row Match Register
During video capture, at the start of a row, the current row value is compared with the VCRM
register. A match ge nerates an interrupt if enabled.
YNXN
Video Memory Address Low Register
The VML register provides a pointer to the start of video capture memory and contains the lower
16-bits of the address.
Video Memory Address High Register
The VMH register provides a po inter to the st art of video capture memory and contains the higher 16-bits
of the address.
Video Memory Stride Register
The VMS register specifies the number of locations in video memory between successive array
elements (stride) and is measured in bytes. Using stride enables better processing time.
LCD Row Match Register
During LCD display DMA output, at the start of each row, the current row value is compared with
the LRM register. A match generates an interr upt if enabled.
September 5, 201059
LCD Video Memory Address Low Register
The LVML register provides a pointer to the start of video data for transfer to the LCD. This
contains the lower 16-bits of the address.
LCD Video Memory Address High Register
The LVMH register provides a pointer to the start of video data for transfer to the LCD. This
contains the higher 16-bits of the address.
LCD Video Memory Stride Register
The LVMS register specifies the number of bytes between the first pixels on adjacent rows in LCD
video memory . Recommen ded to be either the length of a row (in bytes), or the ne xt highest power
of two.
LCD Graphics Memory Address Low Register
The LGML register provides a pointer to the start of gra phics memory for output to the LCD and
contains the lower 16-bits of the address.
LCD Graphics Memory Address High Register
The LGMH register provides a pointer to the start of graphics memory for output to the LCD and
contains the higher 16-bits of the address.
LCD Graphics Memory Stride Register
The LGMS register specifies the number of bytes between the first pixels on adjacent rows in LCD
graphics memory. Recommended to be either the length of a row (in bytes), or the next highest
power of two.
Memory Port Number of Columns Register
The MPNC register specifies the number of columns (in pixels) of the memory port.
Memory Port Current Row Register
The MPR register identifies the selected row in the memory port.
Memory Port Current Column Register
The MPC register identifies the selected column in the memory port.
Memory Port Address Low Register
The MPML register contains the lower address bits of the memory region accessed by the
memory port.
Memory Port Address High Register
The MPMH register contains the upper address bits of the memory region acce sse d by the
memory port.
Memory Port Stride Register
The MPMS register specifies the number of bytes between the first pixels on adjacent rows in the
memory port. Recommended to be either the length of a row (in bytes), or the next highest power
of two.
60September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
Memory Port Register
The MPORT register allows sequential video/graphics memory plane access. A write (read) to this
port generates a memory write (read) to the memory location calculated as follows:
Mem address = {MPH:MPL} + MPR x MPS + MPC.
After the transfer, if the MPC is not at the last pixel of the row, it automatically increments by 1. If
the MPC is at the last pixel of the row, it sets to 0 and the MPR is incremented by MPS.
Memory Window Register
Use the MEMPAGE register to select the active page (1 Kbyte page).
Loading a New Image to the FPGA
The FPGA can be re-imaged using any of the JTAG tool chains that support the Xilinx Spartan 3e
XC3S100e. Two standard JTAG interfaces are provided with the FPGA expansion board: 2 x 7
with 2mm pitch and 1 x 6 with .1" pitch. Once connected, your JTAG scan chain should show an
XC3S100e FPGA and an XCF01S PROM.
NOTE: Images loaded into the PROM must be set to use CCLK as the startup clock. Images
loaded direct to the FPGA may use either CCLK or JTAG CLK.
Figure F-4.FPGA Boundary Scan
NOTE: The LM3S9B96 FPGA boots in JTAG mode, but transitions to serial mode once
configured by the PROM. If your programmer is JTAG-only, you may need to clear the
PROM and power cycle before you can directly program the FPGA via JT AG. This issue is
rare since most tools support both modes. Check with your tool manufacturer for updates.
September 5, 201061
Installing the Software
To install the software, do the following:
1. Plug the provided cable into J4 (on the right side of the board), taking care to ensure proper
alignment and orientation. The silk-screened signal names should match, with the exception
that 2.5 V corresponds to VDD. When correctly aligned, the “JTAG-SPI Full S peed" text should
face in toward the FPGA.
Modifying the Default Image
This section provides the descriptions for the default FPGA image blocks.
Default FPGA Image Blocks
Configuration Registers
The configuration registers are transparently mapped into the Stellaris microcontroller's memory,
and are used to control the flow of the video stre ams. “Register Descriptions” on pa ge 55 provides
the detailed register maps. This is contained within the vregs.v file.
Memory Windower
The memory windower allows the Stellaris microcontroller to work with a rectangular portion of a
frame buffer. For example, this can be used to pull macro-cells for JPEG compression. This is
contained within the mport.v file.
Memory Arbiter
The memory arbiter negotiates access to the external SRAM. The camera capture block is given
highest priority. This is contained within the arb.v file.
Video Compositor
The video compositor assembles the final image from the video and graphics frame buffers, and
passes it directly to the LCD Interface. It also converts the camera's VGA resolution to the LCD's
QVGA resolution by either downsampling. This is contained within the vlcd.v file.
LCD I/F
The LCD interface connects to the Kitronix 3.5" LCD display using an 8-bit parallel mode. This is
usually driven by the Video Compositor, but can also be driven directly by the EPI interface. This is
contained within the vregs.v file.
Camera I/F
The camera interface block captures pixel data from the Omnivision OV7690's 8-bit digital video
port and synchronization signals. This is contained within vcapture.v
Camera FIFO
The Camera FIFO serves two main purposes: reclocking and flow control. The camera and
camera interface run in their own 12-/24-MHz clock domain, whereas the rest of the system runs
off of the EPI clock or twice the EPI clock. The FIFO bridges these difference clock domains. The
camera does not support any flow control functions; once triggered, it proceeds through an entire
image. In order to prevent loss of pixels, this FIFO is 64 elements deep. This is contained within
the vcapture.v and async_fifo_64. v files .
62September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
EPI Signal Descriptions
Table F-8 provides the EPI module’s signal descriptions.
Table F-8. EPI Signal Descriptions
EPI SignalPortFPGA SignalDirectionDescription
EPIOS[31]PG7CLKInEPI Clock
EPIOS[30]PJ6E_IRQnOutInterrupt Signal to Microcontrollera
EPIOS[29]PJ5E_RDInEPI Read Strobe
EPIOS[28]PJ4E_WRInEPI Write Strobe
EPIOS[27]PH7E_RDYOutEPI Ready Signal
EPIOS[26]PH6E_RSTnInFPGA Reset Signal
a. Configure as Stellaris GPIO input with negative level sensitive interrupts. During power up/reset is used for PLL lock status.
b. Configure as Stellaris GPIO output.
September 5, 201063
Component Locations
Figure F-5 shows the details of the component locations from the top view and Figure F-6 shows
the details of the component locations from the bottom view.
Figure F-5.Component Placement Plot for Top
64September 5, 2010
Figure F-6.Component Placement Plot for Bottom
Stellaris® LM3S9B96 Development Kit User’s Manual
Schematics
This section shows the schematics for the LM3S9B96 FPGA memory expansion board:
EPI, LCD, Camera I/F on page 66
SRAM, Power, JTAG on page 67
This document describes the Stella ris® LM3S9B96 EM2 Expansion Board (DK-LM3S9B96-EM2)
for the DK-LM3S9B96 development boar d . Th e EM2 expansion bo ar d pro vide s a tra ns itio n
between the S tellaris Exte rnal Peri pheral Inter face ( EPI) connector and the RF Eval uation Module
(EM) connector. The DK-LM3S9B96-EM2 enables wireless application development using Low
Power RF (LPRF) and RF ID evaluation modules on the Stellaris DK-LM3S9B96 platform.
Figure G-1. EM2 Expansion Board
Features
The DK-LM3S9B96-EM2 expansion board has the following features:
2 sets of EM connectors to support up to 2 RF evaluation modules
1 kilobit of I
EM digital and analog audio signal headers
EM MOD1 SDIO connection headers
32 Khz oscillator for slow clock source to primary EM2 expansion board connector
2
C memory for storing configuration data and EM2 expansion board detection
Installation
To install the EM2 expansion board on the DK-LM3S9B96 development board, do the following:
1. On the DK-LM3S9B96 board (shown in Figure G-2 on page 70), remove any installed board
on EPI connector J2 (A).
September 5, 201069
2. On the DK-LM3S9B96 board (shown in Figure G-2), confirm that shunt jumpers on JP16-JP31
(A) Remove board
(B) Confirm shunt jumpers
(JP16-JP31) installed
(C) Leave JP39
uninstalled
(B) are installed to enable the LCD touch screen. JP39 (C), the leftmost jumper indicated,
should remain uninstalled.
Figure G-2. Removing EPI Board from DK-LM3S9B96 Development Board
3. Place the EM2 expansion board on top of the DK-LM3S9B96 board while aligning the male
EPI expansion connector on the bottom side of the EM2 expansion board with the female EPI
expansion connector on the DK-LM3S9B96 development board (J2).
70September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
Male EPI expansion connector
Bottom side of EM2 module
EM2 Expansion Board
Figure G-3. EM2 Expansion Board
4. Press firmly downward until the board snaps in place.
Figure G-4. Assembled DK-LM3S9B96 Development Board with EM2 Expansion Board
September 5, 201071
Installation of EM Modules onto the EM2 Expa nsion
20-pin sockets
Primary EM header (MOD1) - 20-pin headers
Bottom side of EM moduleTop side of EM2 expansion board
on EM module
Pin 1
tab
Pin 1
slot
Secondary EM header (MOD2) - 20-pin headers
Board
The EM2 expansion board has a primary EM header (MOD1) and a secondary EM header
(MOD2) as indicated on the silk screen (see Figure G-5). The secondary EM header is rotated 180
degrees from the primary EM header.
There are many types of EM modules that can be installed onto the EM2 expansion board. See
the README First document for the EM module you are installing to determine if there is a specific
requirement or recommendation for which header the EM module should be installed in. If
installing a single module and if there is no specific requirement or recommendation in the
module’s README First document indicating which slot it should be installed in, install the single
module into the primary EM header (MOD1).
To install an EM module into the primary mo du le EM slot of the EM2 expansio n boa rd , do th e
following:
1. Attach any supplied antennas to the EM module.
2. Locate the two 20-pin sockets on the back side of the EM module. Note the tab on the side of
each of the 20-pin sockets. This tab denotes pin 1 and aligns with the 20-pin headers on the
EM2 expansion board that contain slots near pin 1 for the tab. See Figure G-5 for details.
Figure G-5. Connecting an EM Module to the EM2 Expansion Board
3. Align the two 20-pin sockets on the EM module over the 20-pin headers on the EM2
expansion board that are within the primary EM silkscreen.
72September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
EM2 expansion board
EM module
Antenna for EM module
DK-LM3S9B96 board
4. Use a slight pressure to seat the EM module firmly on the EM2 expansion board. See
Figure G-6 on page 73 for fully assembled DK-LM3S9B96 board with EM2 expansion board
and wireless EM module.
Figure G-6. Fully Assembled DK-LM3S9B96 Board with EM2 Expansion Board and Wireless EM
Module
Follow these same steps for installing a second module into the secondary EM header location
which will be oriented 180 degrees from the primary EM header location.
NOTE: The secondary EM header should on ly be used whe n two EM modules are in stalled in the
system or when specifically indicated in the EM module’s README First document.
September 5, 201073
Hardware Description
EPI
Connector
UART1
MOD1 GP IO
MOD2 GP IO
MO D1 SHUTDOW N
MO D2 SHUTDOW N
SPI
MOD1 SPI_CS
MOD2 SPI_CS
MOD_I2C
AD_I2C
+3.3 V
CAT24C01
EEPROM
32 KHZ
OSC
/4
/4
/4
SDIO
Header
I2S
Audio
Header
Analog
Audio
Header
I2S
Audio
Header
Analog
Audio
Header
+3.3 V
I2C
UART
SPI
SHUT
DOWN
GPIO
+3.3 V
I2C
UART
SPI
SHUT
DOWN
GPIO
SECONDARY
EM
HEADER
(MOD2)
PRIMARY
EM
HEADER
(MOD1)
The block diagram for the EM2 expansion board is shown in Figure G-7.
Figure G-7. EM2 Expansion Board Block Diagram
Primary EM Header
74September 5, 2010
The primary EM header should always be used when only one EM module is installed unless
otherwise indicated in the README First document for the EM module you are installing.
The primary EM header connects three buses to the EPI connector that are also shared with the
secondary EM header. These buses are I
2
C, UART1, and SPI.
NOTE: The primary and secondary EM headers have a unique SPI chip select signal, but share
the data and clock signals.
The primary EM header contains four GPIO connections to the EPI connector. These GPIOs can
be used as inputs or outputs depending upon th e EM module installed. In addition, four unique
GPIOs are provided to each EM header.
The primary EM header contains one GPIO connection used to shut down and/or reset the EM
module. The actual function depends on the EM module installed. The MODx_nSHUTD signal is
pulled up to 3.3 V on the EM2 adapter. Each header has its own MODx_nSHUTD signal.
The primary EM header contains additional features not found on the secondary EM header
including a 32-KHz oscillator input and a header for a 4-bit SDIO module. These features are not
currently used by the EM modules available today but are available for future expansion.
Secondary EM Header
The secondary EM header should only be u sed wh en two EM m odu les are installed in the system
or when specifically indicated in the EM module’s README First document.
CAT24C01 EEPROM
The EM2 board contains a 1-Kbit I2C EEPROM which connects to an I2C bus separate from the
one connected to the EM headers. This EEPROM contains data that is used by the software
drivers to auto detect that the EM2 expansion board is installed in the system. The EEPROM is
normally write-protected. To make the EEPROM writeable, install a jumper between pins 2 and 3
of JPS1.
I2S Header
The primary EM header and the secondary EM header ea ch contain co nnections to separa te 6-pin
2
I
S headers J2 and J4 respectively. These headers connect to the EM modules only and are not
connected to the EPI header which connects to the DK-LM3S9B9 6. See th e EM mo d ule’s
documentation for more information on the functionality of this header.
Stellaris® LM3S9B96 Development Kit User’s Manual
Analog Audio Header
The primary EM header and the secondary EM header ea ch contain co nnections to separa te 4-pin
analog audio headers J3 and J5 respectively. These headers connect to the EM modules only and
are not connected to the EPI header which connects to the DK-LM3S9B96. See the EM module’s
documentation for more information on the functionality of this header.
SDIO Header
The primary EM header contains a connection to 8-pin SDIO header J1. This header connects to
the EM modules only and is not connected to the EPI header which con nects to the
DK-LM3S9B96. See the EM module’s documentation for more information on the functionality of
this header.
EPI Signal Descriptions
Figure G-1 provides the EPI module's signal descriptions.
PC4PC4MOD1_nSHUTDOutShutdown/Reset Signal for Primary EM Module
PH5PH5MOD2_nSHUTDOutShutdown/Reset Signal for Secondary EM Module
PH0PH0MOD1_GPIO0I/OGPIO for Primary EM Module
PH1PH1MOD1_GPIO1I/OGPIO for Primary EM Module
2
C Bus to EM Modules
2
C Bus to EM Modules
2
C Bus to Auto Discovery EEPROM
2
C Bus to Auto Discovery EEPROM
PH2PH2MOD1_GPIO2I/OGPIO for Primary EM Module
PH3PH3MOD1_GPIO3I/OGPIO for Primary EM Module
PG0PG0MOD2_GPIO0I/OGPIO for Secondary EM Module
PG1PG1MOD2_GPIO1I/OGPIO for Secondary EM Module
PG7PG7MOD2_GPIO2I/OGPIO for Secondary EM Module
PJ2PJ2MOD2_GPIO3I/OGPIO for Secondary EM Module
76September 5, 2010
Stellaris® LM3S9B96 Development Kit User’s Manual
Top
Bottom
Component Locations
Figure G-8 shows the details of the component locations.
Figure G-8. Component Placement Plot for Top and Bottom
Schematics
This section shows the schematics for the EM2 expansion board:
EM2 Expansion Board on page 78
September 5, 201077
5
5
4
4
3
3
2
2
1
1
DD
CC
BB
AA
Primary EM header
Secondary EM header
Stellaris LM3S9B96 EPI header
32KHz Clock
INSTALL RESISTOR R7 WHEN 2nd
MODULE NEEDS SLOW CLK.
In addition to this document, the following references are included on the Stellaris DK-LM3S9B96
Development Kit Documentation and Software CD and are also available for download at
www.ti.com/stellaris
Stellaris LM3S9B96 Microcontroller Data Sheet
Kitron ix LCD Data Sheet
Additional references include:
FT2232D Dual USB/UART FIFO IC Data sheet, version 0.91, 2006, Future Technology
Devices International Ltd.
Texas Instruments TLV320AIC23BPM Audio CODEC Data Sheet
Information on development tool being used:
– RealView MDK web site, www.keil.com/arm/rvmdkkit.asp
– IAR Embedded Workbench web site, www.iar.com
– Code Sourcery GCC development tools web site,
www.codesourcery.com/gnu_toolchains/arm
:
– Code Red Technologies development tools web site, www.code-red-tech.com
– Texas Instruments’ Code Composer Studio™ IDE web site, www.ti.com/ccs
September 5, 201079
80September 5, 2010
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:
ProductsApplications
Audiowww.ti.com/audioCommunications and Telecom www.ti.com/communications
Amplifiersamplifier.ti.comComputers and Peripheralswww.ti.com/computers
Data Convertersdataconverter.ti.comConsumer Electronicswww.ti.com/consumer-apps
DLP® Productswww.dlp.comEnergy and Lightingwww.ti.com/energy
DSPdsp.ti.comIndustrialwww.ti.com/industrial
Clocks and Timerswww.ti.com/clocksMedicalwww.ti.com/medical
Interfaceinterface.ti.comSecuritywww.ti.com/security
Logiclogic.ti.comSpace, Avionics and Defensewww.ti.com/space-avionics-defense
Power Mgmtpower.ti.comTransportation andwww.ti.com/automotive
Microcontrollersmicrocontroller.ti.comVideo and Imagingwww.ti.com/video
RFIDwww.ti-rfid.comWirelesswww.ti.com/wireless-apps
RF/IF and ZigBee® Solutions www.ti.com/lprf