Contents
Contents
Introduction....................................................................................................................................9
Document Purpose and Scope.............................................................................................9
Other Related Documents ....................................................................................................9
Electronic Information .........................................................................................................10
Component References......................................................................................................10
Terms and Definitions.........................................................................................................11
®
Intel 80332 I/O Processor.................................................................................................12
®
Intel IQ80332 I/O Processor Evaluation Platform Board Features ...................................14
Getting Started.............................................................................................................................15
Kit Content..........................................................................................................................15
Hardware Installation..........................................................................................................15
2.2.1 First-Time Installation and Test..............................................................................15
2.2.2 Power Requirements .............................................................................................16
Factory Settings..................................................................................................................17
2.4.1 Supported Tool Buckets ........................................................................................17
2.4.2 Contents of the Flash.............................................................................................17
Target Monitors...................................................................................................................18
2.5.1 RedHat RedBoot....................................................................................................18
Host Communications Examples........................................................................................19
2.6.1 Serial-UART Communication.................................................................................19
2.6.2 JTAG Debug Communication ................................................................................19
2.6.3 Network Communication........................................................................................20
2.6.4 GNUPro GDB/Insight.............................................................................................21
2.6.4.1 Communicating with RedBoot................................................................21
2.6.4.2 Connecting with GDB.............................................................................23
Hardware Reference Section......................................................................................................25
Functional Diagram.............................................................................................................25
Board Form-Factor/Connectivity.........................................................................................26
Memory Subsystem............................................................................................................28
3.4.1 DDR SDRAM .........................................................................................................28
3.4.1.1 Battery Backup.......................................................................................28
3.4.2 Flash Memory Requirements.................................................................................29
Interrupt Routing.................................................................................................................30
®
Intel IQ80332 I/O Processor Evaluation Platform Board Peripheral Bus..........................31
3.6.1 Flash ROM.............................................................................................................32
3.6.2 UART .....................................................................................................................33
3.6.3 Non-Volatile RAM ..................................................................................................33
3.6.4 Audio Buzzer .........................................................................................................33
3.6.5 HEX Display...........................................................................................................33
3.6.6 Rotary Switch.........................................................................................................33
3.6.7 Battery Status ........................................................................................................34
Debug Interface ..................................................................................................................35
September, 2004
3
Contents
3.7.1 Console Serial Port................................................................................................35
3.7.2 JTAG Debug..........................................................................................................36
3.7.2.1 JTAG Port ..............................................................................................36
Board Reset Scheme..........................................................................................................37
3.9.1 Switch Summary....................................................................................................38
3.9.2 Default Switch Settings of S7A1- Visual................................................................38
3.9.3 Jumper Summary ..................................................................................................39
3.9.4 Connector Summary..............................................................................................39
3.9.5 General Purpose Input/Output Header..................................................................39
3.9.6 Detail Descriptions of Switches/Jumpers...............................................................40
3.9.6.1 Switch S1C2: 80332 Reset....................................................................40
3.9.6.2 Switch S6A1: BPCI-X Reset ..................................................................40
3.9.6.3 Switch S8A1: Rotary..............................................................................40
3.9.6.4 Switch S7A1...........................................................................................40
3.9.6.4.1
3.9.6.4.2
3.9.6.4.3
3.9.6.4.4
3.9.6.4.5
3.9.6.4.6
3.9.6.4.7
3.9.6.4.8
3.9.6.4.9
S7A1-1: PCI-X Bus A Speed Enable corresponding to signal
S7A1-2: Reset IOP core corresponding to signal name
S7A1-3: Configration Cycle Enable corresponding to signal
S7A1-4: PCI-X Bus B Speed Enable corresponding to signal
S7A1-5: PCI-X Bus B Hot-Plug Reset Disable corresponding
Switch S7A1- 6: Hot Plug Capable Disabled corresponding to
Switch S7A1 - 7: SMBUS Manageability Address Bit 0 corre-
Switch S7A1 - 8: SMBUS Manageability Address Bit 3 corre-
Switch S7A1- 9:SMBUS Manageability Address Bit 2 corre-
3.9.6.4.10 Switch S7A1- 10: SMBUS Manageability Address Bit 1 corre-
3.9.6.5 Jumper J7D1: Flash bit-width ................................................................43
3.9.6.6 Jumper J1C1: JTAG Chain....................................................................43
3.9.6.7 Jumper J1D2: UART Control .................................................................43
Software Reference.....................................................................................................................45
DRAM.................................................................................................................................45
Components on the Peripheral Bus....................................................................................45
4.2.1 Flash ROM.............................................................................................................46
4.2.2 Peripheral Bus Memory Map .................................................................................47
Board Support Package (BSP) Examples..........................................................................48
®
4.3.1 Intel 80332 I/O Processor Memory Map..............................................................48
®
®
4.3.3 RedBoot Intel 80332 I/O Processor Files ............................................................49
IQ80321 and IQ80332 Comparisons...........................................................................................51
4
September, 2004
Contents
Getting Started and Debugger ...................................................................................................53
Introduction .........................................................................................................................53
B.1.1 Purpose .................................................................................................................53
B.1.2 Necessary Hardware and Software .......................................................................53
B.1.3 Related Documents ...............................................................................................53
B.1.4 Related Web Sites .................................................................................................54
B.2.1 Hardware Setup.....................................................................................................55
B.2.2 Software Setup ......................................................................................................56
New Project Setup ..............................................................................................................57
B.3.1 Creating a New Project..........................................................................................57
B.3.2 Configuration .........................................................................................................58
Flashing with JTAG.............................................................................................................59
B.4.1 Overview................................................................................................................59
B.4.2 Using Flash Programmer.......................................................................................60
Debugging Out of Flash......................................................................................................61
Building an Executable File From Example Code ..............................................................61
Running the Code|Lab Debugger .......................................................................................62
B.7.1 Launching and Configuring Debugger ...................................................................62
B.7.3 Displaying Source Code ........................................................................................63
B.7.4 Using Breakpoints..................................................................................................63
B.7.5 Stepping Through the Code...................................................................................64
B.7.6 Setting Code|Lab Debug Options ..........................................................................64
Exploring the Code|Lab Debug Windows ...........................................................................65
B.8.1 Toolbar Icons .........................................................................................................65
B.8.2 Workspace Window ...............................................................................................65
B.8.3 Source Code..........................................................................................................65
B.8.4 4 Debug and Console Windows ............................................................................65
B.8.5 Memory Window ....................................................................................................65
B.8.6 Registers Window..................................................................................................66
B.8.7 Watch Window.......................................................................................................66
B.8.8 Variables Window ..................................................................................................66
Debugging Basics...............................................................................................................67
B.9.1 Overview................................................................................................................67
B.9.2 Hardware and Software Breakpoints .....................................................................67
B.9.2.1 Software Breakpoints.............................................................................67
B.9.2.2 Hardware Breakpoints ...........................................................................67
B.9.3 C.9.3 Exceptions/Trapping ....................................................................................68
September, 2004
5
Contents
Figures
®
Intel 80332 I/O Processor Block Diagram ................................................................................13
Serial-UART Communication .....................................................................................................19
JTAG Debug Communication.....................................................................................................19
Network Communication Example .............................................................................................20
Functional Block Diagram...........................................................................................................25
Board Form Factor .....................................................................................................................26
®
Flash Connection on Peripheral Bus..........................................................................................32
JTAG Port Pin-out ......................................................................................................................36
10 RESET Sources .........................................................................................................................37
11 Default Switch Setting Switch S7A1...........................................................................................38
12 Flash Connection to Peripheral Bus...........................................................................................46
®
13 Intel 80332 I/O Processor Memory Map...................................................................................48
®
14 Intel 80332 I/O Processor Hardware Setup Flow Chart ...........................................................55
15 Software Flow Diagram ..............................................................................................................56
6
September, 2004
Contents
Examples
®
Intel 80332 I/O Processor Related Documentation List..............................................................9
Electronic Information.................................................................................................................10
Component Reference................................................................................................................10
Terms and Definitions.................................................................................................................11
Summary of Features .................................................................................................................14
Power Features ..........................................................................................................................27
Flash Memory Requirements......................................................................................................29
®
External Interrupt Routing to Intel 80332 I/O Processor...........................................................30
10 Peripheral Bus Features.............................................................................................................31
11 Flash ROM Features ..................................................................................................................32
12 Rotary Switch Requirements ......................................................................................................33
13 Battery Status Buffer Requirements ...........................................................................................34
14 Reset Requirements/Schemes...................................................................................................37
15 Switch Summary.........................................................................................................................38
16 Switch S7A1 ...............................................................................................................................38
17 Jumper Summary .......................................................................................................................39
18 Connector Summary...................................................................................................................39
19 J2D2 GPIO Header Definition.....................................................................................................39
20 Rotary Switch Settings................................................................................................................40
21 S7A1-1: PCI-X Bus A Speed Enable..........................................................................................40
22 Switch S7A1-2: Reset IOP: Settings and Operation Mode.........................................................40
23 Switch S7A1-3: RETRY: Settings and Operation Mode .............................................................41
24 S7A1-4: PCI-X Bus B Speed Enable: Settings and Operation Mode .........................................41
25 S7A1-5: PCI-X Bus B Hot-Plug Reset Disable: Settings and Operation Mode ..........................41
26 Switch S7A1- 6: Hot Plug Capable Disabled: Settings and Operation Mode .............................41
30 Switch S7A1 - 10: SMBUS Slave Address 0: Settings and Operation Mode .............................42
31 Jumper J7D1: Descriptions.........................................................................................................43
32 Jumper J7D1: Settings and Operation Mode..............................................................................43
33 Jumper J1C1: Descriptions.........................................................................................................43
34 Jumper J1C1: Settings and Operation Mode..............................................................................43
35 Jumper J1D2: Descriptions.........................................................................................................43
36 Jumper J1D2: Settings and Operation Mode..............................................................................43
37 Jumper J7B4: Descriptions.........................................................................................................44
38 Jumper J7B4: Settings and Operation Mode..............................................................................44
39 Jumper J9D3: Descriptions.........................................................................................................44
40 Jumper J9D3: Settings and Operation Mode..............................................................................44
41 Peripheral Bus Memory Map ......................................................................................................47
®
®
board Comparisons51
43 Related Documents ....................................................................................................................53
September, 2004
7
Contents
Revision History
Date
Revision
Description
27 September 2004
001
Initial Release.
8
September, 2004
Introduction
1
1.1
Document Purpose and Scope
®
This document describes the Intel IQ80332 I/O processor evaluation platform board (IQ80332)
®
using DDR-II 400 MHz SDRAM. The Intel 80332 I/O processor (80332) is intended for rapid,
intelligent I/O development. The 80332 is a multi-function device that integrates the Intel XScale®
core (ARM* architecture compliant) with intelligent peripherals including a PCI Express bus
application bridge.
1.2
Other Related Documents
®
Table 1.
Intel 80332 I/O Processor Related Documentation List
Document
Number
Intel® 80332 I/O Processor Developer’s Manual
274065
274066
Intel® 80332 I/O Processor Datasheet
Intel® 80332 I/O Processor Design Guide
273824
Intel® 80332 I/O Processor Specification Update
273927
Intel® 80332 I/O Processor JTAG Support White Paper
Intel® 80332 I/O Processor Product Brief
273963
302746
Intel® 80321 Software Conversion to the Intel® 80332 I/O Processor Application Note
Intel® Flash Recovery Utility (FRU) Reference Manual
IEEE Standard Test Access Port and Boundary-Scan Architecture (IEEE JTAG-1149.1-1990)
273890
274071
PCI Local Bus Specification, Revision 2.3 - PCI Special Interest Group
PCI Express Specification, Revision 1.0a - PCI Special Interest Group
PCI Express Base Specification 1.0a - PCI Special Interest Group
PCI Express Card Electromechanical Specification 1.0a - PCI Special Interest Group
PCI Local Bus Specification, Revision 2.3 - PCI Special Interest Group
PCI-X Specification, Revision 1.0b - PCI Special Interest Group
PCI Bus Power Management Interface Specification, Revision 1.1 - PCI Special Interest Group
PCI Bus Hot-Plug Specification, Revision 1.1 - PCI Special Interest Group
Intel documentation is available from the local Intel Sales Representative or Intel Literature Sales.
To obtain Intel literature write to or call:
Intel Corporation
Literature Sales
P.O. Box 5937
Denver, CO 80217-9808
9
Introduction
1.3
Electronic Information
Table 2.
Electronic Information
Support Type
Location/Contact
The Intel World-Wide Web (WWW) Location:
Customer Support (US and Canada):
1-916-377-7000
1.4
Component References
Component Reference
Table 3.
Component Part Number
Additional Information
Intel
•
•
Manufacturer: Intel Corporation
StrataFlash® 28F640J3C
Memory
Intel(R)
•
•
Manufacturer: Intel Corporation
Gigabit
82545EM
Ethernet
Controller
•
•
Manufacturer: Grayhill*
URL:
Rotary Switch
DR FC 16
GroupID=Series94HBinaryCoded&GroupDisplayLabel=&RestSes=No
•
•
•
•
•
•
•
•
•
•
Manufacturer: Agilent Technologies*
Hex Display HDSP-A103
Manufacturer: RDI*
DMT 1206
AudioBuzzer
SMT
Manufacturer: SIMTEK*
STK14C88-3
NVSRAM
N 35
Manufacturer: XILINK*
XC9572XL -
CPLD
10TQ100C
Manufacturer: National*
Temperature
LM75CIMX-3
Sensor
Program-
MAX6306UK
mable Reset
29D3
•
•
Manufacturer: Maxim*
IC
•
•
•
•
•
•
•
•
•
•
Manufacturer: IDT* (Integrated Device Technology)
Manufacturer: IDT* (Integrated Device Technology
Manufacturer: Maxim*
Registered
Buffer
IDT74SSTU3
2864BF
Program-
mable PLL
IDTCSPU877
BV
256 bit 1-wire DS2430A_TS
EEPROM
OC
Manufacturer: Maxim*
3.3V
Transceiver
MAX561
Manufacturer: Analog Devices*
Battery
Charger
ADP3801
10
Introduction
1.5
Terms and Definitions
Table 4.
Terms and Definitions
Acronym/Term
Definition
ARM
CRB
Refers to both the microprocessor architecture and the company that licenses it.
Customer Reference Board
In-Circuit Emulator – A piece of hardware used to mimic all the functions of a
microprocessor.
ICE
IOP
I/O processor
Joint Test Action Group – A hardware port supplied on Intel XScale® microarchitecture
evaluation boards used for in-depth testing and debugging.
JTAG
PPCI-X
PSU
Primary PCI-X.
Power Supply Unit
Secondary PCI-X.
SPCI-X
11
Introduction
®
1.6
Intel 80332 I/O Processor
About the 80332. The 80332 is a multi-function device that combines the Intel XScale® core with
intelligent peripherals, and integrates two PCI Express-to-PCI Bridges. The 80332 consolidates into a
single system:
• Intel XScale® core.
• x8 PCI Express Upstream Link.
• Two PCI Express-to-PCI Bridges supporting PCI-X interface on both segments.
• PCI Standard Hot Plug Controller (segment B).
• Address Translation Unit (ATU): PCI-to-Internal Bus Application Bridge, interfaced to the
segment A.
• High-Performance Memory Controller.
• Interrupt Controller with 17 external interrupt inputs.
• Two Direct Memory Access (DMA) Controller.
• Peripheral Bus Interface (PBI) Unit.
• Performance Monitor Unit (PMU).
• Application Accelerator Unit (AAU).
2
• Two I C Bus Interface Units (BIU).
• Two 16550 Compatible UARTs with flow control (4 pins).
• Eight General Purpose Input Output (GPIO) Ports.
The 80332 is an integrated processor that addresses the needs of intelligent I/O applications and helps
reduce intelligent I/O system costs.
PCI Express is an industry standard, high performance, low latency system interconnect. The 80332
PCI Express upstream link is capable of x8 lane widths at 2.5 GHz operation as defined by the PCI
Express Specification, Revision 1.0. The addition of the Intel XScale® core brings intelligence to the
PCI Express-to-PCI Bridges.
The 80332 integrates dual PCI Express-to-PCI-X Bridges with the ATU as an integrated secondary
PCI device. The Upstream PCI Express port implements the PCI-to-PCI Bridge programming model
according to the PCI Express Specification, Revision 1.0. The Primary Address Translation Unit is
compliant with the PCI-X Specification, Revision 1.0a definitions of an ‘application bridge’.
®
For more in depth information in regards to the 80332, please see the Intel 80332 I/O Processor
Developer’s Manual.
12
Introduction
®
1.7
Intel IQ80332 I/O Processor Evaluation Platform
Board Features
Table 5.
Summary of Features
Feature
Definition
Battery Backup Unit: Battery back up circuit for SDRAM.
Ethernet Intel(R) 82545EM Gigabit Ethernet Controller
Flash ROM: 8 MB Flash ROM 3.3 V – 16-bit Flash I/F.
Form Factor: PCI-X card (312 X 107 mm)
General Purpose I/O: GPIO Pins are used as described in the appropriate section in this document
Hex Display: Two 7-segment Hex LED displays.
JTAG Port: ARM compliant JTAG Header.
Logic analyzer connectors on the DDRII SDRAM interface.
Logic Analyzer:
Interposer Card may be used for the memory bus – Information supplied separately.
•
•
•
256 MB (512 Mb x 16) DDRII SDRAM 400 MHz DIMM.
Memory:
ECC
Registered
Board sources +1.25 V, +2.5 V, +3.3 V, +5 V, +12 V, and -12 V from primary PCI
connector.
Onboard Power:
•
•
All core voltages are derived from 3.3 V supply.
Auxiliary power for the Secondary PCI slot.
Power LED: Power on (green).
Primary PCI: PCI Express - x8 lane
Support for “RAID” Implementation – Ability to make the devices plugged in the
secondary expansion slots “Private”.
RAID Support
Integrated XOR engine and two iSCSI CRC32C off-load engines.
•
•
•
1 64-bit PCI-X connector - 133 MHz.
Secondary PCI:
Serial Port:
1 64 bit 100 MHz PCI-X
Intel(R) 82545EM Gigabit Ethernet Controller also on the 100 MHz PCI.
Dual RJ11 serial port connectors. The 80332 has two integrated UART serial ports
which are 16550 compatible.
14
Getting Started
2
The 80332 is a software development environment for IQ80332. Software updates and additional
offerings from vendors can change frequently. To keep up-to-date, please visit
2.1
Kit Content
The 80332 Kit contains the following items:
• IQ80332 with 400 MHz DDRII SDRAM DIMMs
• Code|Lab* Development Environment from Accelerated Technology Incorporated*
• JTAG Emulation unit
• Serial Cable and RJ11 Adapter
2.2
Hardware Installation
Warning: Static charges can severely damage the boards. Be sure you are properly grounded before removing
the board from the anti-static bag.
2.2.1
First-Time Installation and Test
For first-time installation, visually inspect the 80332 for any damage made during shipment. Follow
the host system manufacturer’s instructions for installing a PCI Express adapter card. The board is a
full-length host bus adapter card that requires a PCI Express slot free from obstructions. The IQ80332
has a x8 (read as ‘by eight’) edge connector.
Note: Please note, at this time the IQ80332 does NOT work in a passive backplane. This is due to the
nature of the PCI Express linking protocol. For the I/O processor to successfully come out of reset,
a link must be established on the PCI Express bus. Without another device on a passive backplane
to ‘talk to’, a link is not established.
15
Getting Started
2.2.2
Power Requirements
The 80332 requires a 3.3 V supply coming through the PCI Express primary connector. Plug the
board into a desktop with a PCI Express slot.
is used to power the secondary PCI-X slot. This connector is compatible with a standard ATX hard
drive power connector.
Caution: Before connecting power to the entire system, verify that the auxiliary system power to the
secondary PCI-X slot and the main power to the 80332 are both connected. Both power rails should
come up at the same time. When there is not a card plugged into the secondary PCI-X slot, then the
auxiliary power can be left unconnected.
16
Getting Started
2.3
Factory Settings
Make sure that the switch/jumper settings are set to proper positions as explained in Section 3.9,
2.4
Development Strategy
2.4.1
Supported Tool Buckets
For developing and debugging software application, the production version of the 80332 kit includes
the Code|Lab Development Environment. Support for the Code|Lab development environment is
available from ATI*. Please refer to the enclosed package.
The kit also contains evaluation copies for several Software Development Tools. These tools are for
evaluation purposes and do not include any support. Please contact the vendor directly for additional
information and support. They include, but are not limited to:
• RedHat* GNUPro tools
• ARM RealView Developer Suite
• WindRiver* VxWorks* RTOS and Tornado* Development Tools
• Wasabi Systems NetBSD* ODS
• TimeSys* Linux* RTOS
• Accelerated Technology Inc.*, Nucleus Plus* RTOS and Development Tools
Please contact your Intel representative for the latest updates or visit
2.4.2
Contents of the Flash
The production version of the board contains an image for RedHat RedBoot* target monitor.
17
Getting Started
2.5
Target Monitors
2.5.1
RedHat RedBoot
RedBoot* is an acronym for “RedHat Embedded Debug and Bootstrap”, and is the standard
embedded system debug/bootstrap environment from RedHat, replacing the previous generation of
debug firmware: CygMon and GDB stubs. It provides a bootstrap environment for a range of
embedded operating systems, such as embedded Linux and eCos*, and includes facilities such as
network downloading and debugging. It also provides a simple Flash file system for boot images.
RedBoot provides a set of tools for downloading and executing programs on embedded target
systems, as well as tools for manipulating the target system's environment. It can be used for both
product development (debug support) and for end product deployment (Flash and network booting).
Here are some highlights of RedBoot capabilities:
• Boot scripting support
• Simple command line interface for RedBoot configuration and management, accessible via
• Integrated GDB stubs for connection to a host-based debugger (GBD/Insight) via serial or
Ethernet. (Ethernet connectivity is limited to local network only)
• Attribute Configuration - user control of aspects such as system time and date (when
applicable), default Flash image to boot from, default fail-safe image, static IP address, etc.
• Configurable and extensible, specifically adapted to the target environment
• Network bootstrap support including setup and download, via BOOTP, DHCP and TFTP
• X/Y-Modem support for image download via serial
• Power On Self Test
18
Getting Started
2.6
Host Communications Examples
How to communicate to the host.
2.6.1
Serial-UART Communication
board is plugged into a host machine, as in the figure below. You can use an additional laptop
computer, but it is not necessary. The host computer, when loaded with the proper software can
communicate with the board.
Figure 2.
Serial-UART Communication
Laptop computer
2.6.2
JTAG Debug Communication
board is plugged into a host machine, as in the figure below. You can use an additional laptop
computer, but it is not necessary. The host computer, when loaded with the proper software can
communicate with the board.
Figure 3.
JTAG Debug Communication
Laptop computer
19
Getting Started
2.6.3
Network Communication
Using a standard network connection, the user can communicate with the board via the ethernet port.
Redboot also allows the user to remotely boot the platform using a BOOTP server through the
network Connection.
Figure 4.
Network Communication Example
A
B
C
D
E
F
G
H
S
EL EC TE
-L IN
D
O
N
E
20
Getting Started
2.6.4
GNUPro GDB/Insight
2.6.4.1
Communicating with RedBoot
Hardware Setup:
• Host with UNIX/Linux or Win32 installed
• IQ80332 with serial cable
• RedHat RedBoot monitor Flashed to the platform board
Recommended Mapping of UART Ports to Host Com Ports
• Host port connected to the platform board UART.
The following communication tools can be used:
• Win32 using HyperTerminal
• UNIX using Kermit
• Linux using Minicom
• Solaris using Tip
RedBoot Monitor startup:
Description: terminal emulator runs on host and communicates with the board via the serial cable.
Start: Power up the IQ80332. While the 'reset' is asserted, the two 7-segment LEDs sequentially
display “88”, “A0” through “A6”, followed by “SL” (Scrub loop). When RedBoot is
successfully booted, it displays the characters “A1” on the LEDs. When the final state of “A1”
does not occur, reset the processor again.
The time for reset is approximately 1 or 2 seconds.
Win32 on Host Connecting with HyperTerminal.
21
Getting Started
To bring up a HyperTerminal session on a Win32 platform: Go to Start, Programs, Accessories,
Communications, HyperTerminal
• HyperTerminal setup screens:
— “Connection Description” Panel:
•
Enter name.
— “Connect To” Panel:
•
Select host com2 port (or whichever port you are using).
— Port Settings:
•
•
•
•
•
Bits per second: 115200
Data Bits: 8
Parity: none
Stop Bits: 1
Flow Control: none
— Start HyperTerminal:
•
Select Call from HyperTerminal panel.
— Reset or power up 80332 board.
— The Host screen reads:
RedBoot(tm) debug environment - built dd:mm:yy, Mon dd 2004
Platform: 80332
Copyright (C) 2004, RedHat, Inc.
RAM: 0xa0000000-0xa2000000
FLASH: 0x00000000 - 0x00800000, 64 blocks of 0x00020000 bytes each.
IP: 192.168.0.1, Default server: 0.0.0.0
RedBoot>
For further information on the GDB/Insight Debugger, refer to the content of the GNUPro CD and/or
the GNUPro Debugging Tools manual. This setup assumes that RedBoot is Flashed on the board.
22
Getting Started
2.6.4.2
Connecting with GDB
Below are the GDB commands entered from the command prompt. Be sure system path is set to
access “xscale-elf-gdb.exe”. File name in example “hello”. Bold type represents input by user:
1
>xscale-elf-gdb -nw hello
• Start GDB executable, loads debug information and symbols.
(GDB) set remotebaud 115200
• Set baud rate for the 80332.
Connect COM port:
• When using Windows command prompt:
(GDB) target remote com1
Example: screen output from board to host (GDB) target remote com1:
Remote debugging using com1.
(GDB)
• When using Linux
(GDB) target remote /dev/ttyS0
(GDB) load
• Load the program to the board, may have to wait a few seconds.
(GDB) break main
• Set breakpoint at main.
(GDB) continue
• Start the program using 'continue' verse the usual 'run'.
• Program hits break at main() and wait.
1. To be supplied separately.
23
Getting Started
This Page Left Intentionally Blank
24
Hardware Reference Section
Hardware Reference Section
3
3.1
Functional Diagram
Figure 5 shows the functional block for the 80332.
Figure 5.
Functional Block Diagram
Target Market
ROMB
PCI Express RAID card
DDR II 400
DDR SDRAM
Battery
HEX
LED
Backup
Buzzer
Local Bus
Intel®
80332
I/O
PCI-X 2.0 Bus Slot (266MHz)
Slot
Slot
RS-232
RS-232
I2C
PCI-X Bus IOP (100 MHz)
Gig-E
GPIOs
JTAG
Processor
X8 Edge Connector
25
Hardware Reference Section
3.2
Board Form-Factor/Connectivity
Table 6.
Form-Factor/Connectivity Features
Description
The 80332 connects to the Primary PCI-Express bus of the host machine.
The 80332 has two PCI-X expansion slot.
The 80332 has two serial ports and one RJ-45 Ethernet port.
The 80332 has one JTAG port compliant with ARM Multi-ICE 20-pin connector standard. The JTAG is targeted for the Intel
XScale® core and the CPLD, and is used for software debug purposes.
Figure 6.
Board Form Factor
A ux
P ow er
P C I-X S lot (stradd les b oard e dge )
P erip hera l B us H eade r
Pow er Statu
s
82545 EM
G bE
D D R II D IM M
C P LD
Flash
R otary
Sw itch
B uz
zer
D IP Sw itch
Se rial
E E PR O M
Intr/GP IO
H ea der
107
Intel®
80332
I/O
R J-45
E therne
t
B attery
P C I-X R t A ngle S lot
P rocessor
RJ-1 1
S erial ports
(M ou nted on Back S ide of P C B)
P C I-E
E dge
312
26
3.3
Power
The 80332 draws power from the PCI Express bus. The power requirements for the 80332 are shown
expansion slot.
Table 7.
Power Features
Voltage Rail
Typical Current
Maximum Current
+3.3 V
+5 V
TBD mA
TBD mA
TBD mA
6971 mA
7 mA
+12 V
105 mA
Note: The maximum current was calculated, but not measured. This numbers do not include the power
required by a PCI-X card mounted on the expansion slot(s).
27
Hardware Reference Section
3.4
Memory Subsystem
The Memory Controller of 80332 controls the DDR SDRAM memory subsystem. It features pro-
grammable chip selects and support for error correction codes (ECC). The memory controller can
be configured for DDR SDRAM at 333 MHz and DDR-II at 400 MHz. The memory controller
supports pipelined access and arbitration control to maximize performance. The memory controller
interface configuration support includes Unbuffered DIMMs, Registered DIMMs, and discrete
DDR SDRAM devices.
This IQ80332 has DDR-II at 400 MHz DIMM on the board. The memory subsystem of the
evaluation board consists of the SDRAM as well as the Flash memory subsystems.
3.4.1
DDR SDRAM
The DDR SDRAM interface consists of a 64-bit wide data path to support up to 3.2 Gbytes/sec
throughput. An 8-bit Error Correction Code (ECC) is stored into the DDRII SDRAM array along
with the data and is checked when the data is read.
The IQ80332 features on board registered DDRII 400 MHz SDRAM, arranged 512 Mbit x16 in
density (256 MB), and with ECC.
3.4.1.1
Battery Backup
Battery backup is provided to save any information in DDR during a power failure. The evaluation
board contains a 4V Li-ion battery, a charging circuit and a regulator circuit.
DDRII technology provides enabling data preservation through the self-refresh command. When the
processor receives an active Primary PCI-X reset, the self-refresh command issues, driving SCKE
signals low. Upon seeing this condition, the board logic circuit holds SCKE low before the processor
loses power. Batteries maintain power to DDRII and logic, to ensure self-refresh mode. When the
circuit detects PRST# returning to inactive state, the circuit releases the hold on SCKE. Removing the
battery can disable the battery circuit. When the battery remains in the platform when it is de-powered
and/or removed from the chassis, the battery maintains DDRII for about four hours. Once power is
reapplied, the battery is fully charged.
The CPLD contains information in regards to the battery status. Please see Section 3.6.7, “Battery
Status” on page 34 for more details.
28
Hardware Reference Section
3.4.2
Flash Memory Requirements
Total Flash memory size is 8 MB.
Table 8.
Flash Memory Requirements
Description
IQ80332 Total Flash size is 8 MB
80332 Flash technology is based on Intel StrataFlash® family
80332 Flash uses a 16-bit interface
80332 Flash utilizes the 80332 Peripheral Bus
80332 May be programmed using the PCI-X interface – Flash Recovery Utility (FRU) Utility
80332 May be programmed using a RAM based software target monitor – RedHat RedBoot and ARM Firmware Suite
80332 May be programmed using a JTAG emulation/debug device
29
Hardware Reference Section
3.5
Interrupt Routing
The 80332 Interrupt routing.
®
Table 9.
External Interrupt Routing to Intel 80332 I/O Processor
Interrupt
System Resource
HPI#
Temperature Sensor, Header
PCI-X Slot INTB#, Header
S_INTA#
S_INTB#
S_INTC#
S_INTD#
P_INTA#
P_INTB#
P_INTC#
P_INTD#
PCI-X Slot INTC#, Header
PCI-X Slot INTD#, Header
PCI-X Slot INTA#, Header
PCI-X Card Edge INTA#, Header
PCI-X Card Edge INTB#, Header
PCI-X Card Edge INTC#, Header
PCI-X Card Edge INTD#, Header
30
Hardware Reference Section
®
3.6
Intel IQ80332 I/O Processor Evaluation Platform
Board Peripheral Bus
®
Figure 7.
Intel IQ80332 I/O Processor Evaluation Platform Board Peripheral Bus Topology
Agilent*
HDSP-A103 Hex
Display
FLASH 28F640J3C
RDI
16-bit
8 Mb
DMT-1206-SMT
Audio Buzzer
Intel® 80332
I/O Processor PBI Bus
XILINX
XC9572XL-
10TQ100C
CPLD
Grayhill
HAB16W
Rotary Switch
SIMTEK
STK14C88-3 N 35
NVSRAM
PC 104
Connector
The devices on the bus include Flash ROM, audio buzzer, CPLD, HEX display, NVSRAM, and
rotary switch.
Table 10.
Peripheral Bus Features
Description
The bus width can be 8-bit or 16-bit and runs at 66 MHz.
The bus is utilized for attaching debug and Flash devices.
The interfaces/devices that are utilized include an audio buzzer, CPLD, a rotary switch, a HEX Display, and
NVSRAM.
31
Hardware Reference Section
3.6.1
Flash ROM
Table 11.
Flash ROM Features
Description
Flash is an Intel StrataFlash® technology – Part number: 28F640J3C
Flash size is 8 MB
The connection to the peripheral bus is depicted by Figure 8
Figure 8.
Flash Connection on Peripheral Bus
FLASH
28F640J3A
16-bit
CS
8 Mb
Intel® 80332
I/O
Processor
Intel® 80332 I/O Processor Bus
B3236-02
32
Hardware Reference Section
3.6.2
UART
The 80332 has two integrated UARTs. Each asynchronous serial ports supports all the functions of a
16550 UART. The UART signals are connected to a dual RS-232 buffer and then to a RJ-11 serial
port connector mounted on the bracket of the evaluation board. The serial port and GPIO signals are
muxed on the same pins. Jumper J1D2, located next to the serial port buffer can disable the buffer to
allow the signals to be used as GPIO signals. Please see Section 3.9.3, “Jumper Summary” on
page 39 for more details.
3.6.3
3.6.4
Non-Volatile RAM
In addition to the 8MB Flash device, the IQ80332 has a separate 32k by 8 non-volatile RAM device
on the peripheral bus. The NVRAMs address range is from CE87 0000 to CE87 FFFF (in hex).
Audio Buzzer
The 80332 evaluation board has an audio buzzer that is turned on and off by writing to the Buzzer
Control Register located in the CPLD. Jumper J9D3 adjusts the volume from off, to soft, to loud.
address range is from CE86 0000 to CE86 FFFF (in hex). Please see Section 4.2.2, “Peripheral Bus
Memory Map” on page 47 for more details.
3.6.5
3.6.6
HEX Display
The two pairs of Agilent HDSP-A103 seven segment LEDs are used for displaying POST codes or
other software generated debug codes. Both HEX displays are individually addressed. The left HEX
display address range is CE84 0000 to CE84 FFFF (in hex). The right HEX display address range is
CE85 0000 to CE85 FFFF (in hex). Please see Section 4.2.2, “Peripheral Bus Memory Map” on
page 47 for more details.
Rotary Switch
The 80332 provides a Rotary Switch (S8A1) for the user to select from different boot-up flavors.
Setting ‘0’ enables private devices on the secondary PCI-X bus. Setting ‘0’ allows Redboot to
configure and use devices in slot A. Position ‘1’ allows the host to see all the devices on the
secondary PCI bus. The default setting is position 0. Other settings are currently not validated with
Redboot. Other settings may be used with other software applications. Please see Section 4.2.2,
“Peripheral Bus Memory Map” on page 47 for more details on addressing the rotary switch.
Table 12.
Rotary Switch Requirements
Description
Rotary switch has a 4-bit resolution (16 positions).
Default setting is ‘0’. This enables private devices on PCI-X bus.
Position ‘1’ allows host to see all devices on the secondary bus.
33
Hardware Reference Section
3.6.7
Battery Status
A CPLD on the IQ80332 provides the following status for the battery. Please see Section 4.2.2, “Peripheral
Bus Memory Map” on page 47 for more details on addressing the CPLD.
Table 13.
Battery Status Buffer Requirements
Read/
Write
BIT
Name
Description
•
•
0 = No backup battery
0
1
2
3
R
Battery Present
Battery Charged
Battery Discharged
1 = Battery backup is present
•
•
0 = Battery is not fully charged
1 = Battery is fully charged
R
R
•
•
0 = Battery backup is not fully discharged
1 = Battery backup is fully discharged
•
•
0 = Disable battery backup
1 = Enable battery backup
R/W
*
Battery Enable
Reserved
4-7
Undefined
34
Hardware Reference Section
3.7.2
JTAG Debug
The 80332 has a 20-pin JTAG connector (J7D2) that is in compliant with ARM Multi-ICE guidelines.
3.7.2.1
JTAG Port
Figure 9.
JTAG Port Pin-out
VTref
nTRST
TDI
1
2
4
6
8
Vsupply
GND
3
5
GND
TMS
7
GND
TCK
9
10 GND
12 GND
14 GND
16 GND
18 GND
20 GND
RTCK
TDO
11
13
15
17
nSRST
DBGRQ
DBGACK 19
A9457-01
36
Hardware Reference Section
3.8
Board Reset Scheme
Table 14.
Reset Requirements/Schemes
Description
Primary PCI reset, resets all devices on the board. It occurs during the power-up.
The SRST signal from the JTAG connector is a bi-directional signal that can force a reset similar to the
power-up reset on the board.
Figure 10.
RESET Sources
DDR II SDRAM
Reset
Button
M_RST#
RESETIN
Debounce
#
B_RST#
PCI-X 2.0 Con B
Power
PWRDELAY
Delay
Intel® 80332 I/O
Processor
A_RST#
PCI-X Con A
TRST
TRST
#
JTAG
Con
#
CPLD
SRST
#
PWRGD
RST#
LAN_PWR_GOOD
Voltage
Monitor
82545EM
Isolation
Pwrgood
PCI-E Con
37
Hardware Reference Section
3.9
Switches and Jumpers
3.9.1
Switch Summary
Please note that the term ‘open’ refers to the individual pin of switch S7A1 being pushed in at bottom
(small dot on pin away from the ‘open’ label on the switch). The term ‘closed’ refers to the pin being
more details.
Table 15.
Switch Summary
Factory
Default
Switch
Association
Description
S1C1
80332
Reset
Reset
S6A1
BPCI-X
S7A1-1
S7A1-2
S7A1-3
S7A1-4
S7A1-5
S7A1-6
S7A1-7
S7A1-8
S7A1-9
APCI-X Bus PCI-XBus A Speed Set
Closed
Open
IOP
IOP
RESET: Sets IOP Reset-Mode operation
RETRY: Sets IOP RETRY-Mode operation
Open
BPCI-X Bus PCI-X Bus B speed set
Closed
Closed
Closed
Open
BPCI-X Bus PCI-X Bus B Hot Plug Reset
BPCI-X Bus Hot Plug Capable Disable
SMBUS Bus SMBUS Manageability address bit 5
SMBUS Bus SMBUS Manageability address bit 3
SMBUS Bus SMBUS Manageability address bit 2
Open
Open
S7A1-10 SMBUS Bus SMBUS Manageability address bit 1
S8A1 CPLD Rotary Switch
Open
Position 1
3.9.2
Default Switch Settings of S7A1- Visual
Table 16.
Switch S7A1
Closed
Open
Open
Closed
Closed
Closed
Open
Open
Open
Open
S7A1
1
S7A1
2
S7A1
3
S7A1
4
S7A1
5
S7A1
6
S7A1
7
S7A1
8
S7A1
9
S7A1
10
Figure 11.
Default Switch Setting Switch S7A1
1
2
3
4
5
6
10
9
7
8
Open
38
Hardware Reference Section
3.9.3
Jumper Summary
Table 17.
Jumper Summary
Jumper
Description
Factory Default
J1C1
J1D2
J7B4
J7D1
J9D3
JTAG Chain Enable
Disables UART
1-2
Open
1-2, 3-4
Open
Open
SM_SCLK to EEPROM, SM_SDTA to EEPROM
16-bit Flash Enable
Buzzer Volume
3.9.4
Connector Summary
Table 18.
Connector Summary
Connector
Description
J1D1
J1E1
RJ45 Network Connector for GbE NIC.
RJ11 Dual Serial Port Connector.
J1L1, J1M1,
J1M2, J1N1,
J2M1, J2M2
SMA connectors
J1R1
J2A1
J2D1
J2D2
Secondary PCI-X Expansion bus Slot
Secondary PCI-X Expansion bus Slot.
Power header for fan.
GPIO tap-in Header
J1B1, J5D1,
J5C1
Test headers
J2E1
J5B1
Edge connector for primary PCI Express Bus.
DIMM
J7A1
PC104 Mod connector.
I2C 4 pin connectors.
J7B1, J7B2
Secondary PCI-X Expansion Slot Power. Please see Section 2.2.2, “Power Requirements”
for more details
J7B3
J7C1
J7D2
J9D1
Test header (empty)
JTAG CPLD Header.
Power header for battery.
3.9.5
General Purpose Input/Output Header
signal assignments. The GPIO signals are muxed with the serial port signals. The serial port must be
disabled to use the GPIO signals. These pins corespond to Jumer J2D2.
Table 19.
J2D2 GPIO Header Definition
Pin
Signal
Pin
Signal
Pin
Signal
1
2
3
GND
4
5
6
GPIO5
GPIO4
GPIO3
7
8
9
GPIO2
GPIO1
GPIO0
GPIO7
GPIO6
39
Hardware Reference Section
3.9.6
Detail Descriptions of Switches/Jumpers
3.9.6.1
Switch S1C2: 80332 Reset
This switch resets 80332.
3.9.6.2
Switch S6A1: BPCI-X Reset
This switch resets the PCI-X B segment bus.
3.9.6.3
Switch S8A1: Rotary
Table 20.
Rotary Switch Settings
Position
Description
0
Enables private devices on the secondary PCI-X slot. Redboot uses this setting to configure
private devices
Factory Default
Disables private devices on the secondary PCI-X slot. This setting allows the host to see all
the devices on the secondary PCI bus.
1
These settings are meaningless to Redboot. Other applications may use these settings for
configuration or software utilization.
2-F
3.9.6.4
Switch S7A1
This 10 pin switch that allows the user to enable or disable various features. Please see specifics
below.
3.9.6.4.1
Table 21.
S7A1-1: PCI-X Bus A Speed Enable corresponding to signal name PBI_AD3
This switch allows the user to force the PCI-X bus A to run at 133 MHz or 100 MHz.
S7A1-1: PCI-X Bus A Speed Enable
S7A1-1
Operation Mode
Open
Enables 133 MHz on PCI-X bus A
Enables 100 MHz on PCI-X bus A (Default Mode)
Closed
3.9.6.4.2
Table 22.
S7A1-2: Reset IOP core corresponding to signal name PBI_AD5
RESET MODE is latched at the de-asserting edge of P_RST# and it determines when the 80332 is held
in reset until the Intel XScale® core Reset bit is cleared in the PCI Configuration and Status Register.
Switch S7A1-2: Reset IOP: Settings and Operation Mode
S7A1-2
Operation Mode
Open
Don't hold in reset, enable IOP core (Default mode).
Hold IOP core in reset.
Closed
40
Hardware Reference Section
3.9.6.4.3
Table 23.
S7A1-3: Configration Cycle Enable corresponding to signal name PBI_AD6
Configuration Cycle Enable or RETRY is latched at the de-asserting edge of P_RST# and it
determines when the Primary PCI interface disable PCI configuration cycles by signaling a Retry
until the Configuration Cycle Retry bit is cleared in the PCI Configuration and Status Register.
Switch S7A1-3: RETRY: Settings and Operation Mode
S7A1-3
Operation Mode
Open
Configuration Retry Enabled. - use when booting in a host (Default mode).
Configuration Retry Disabled.
Closed
3.9.6.4.4
Table 24.
S7A1-4: PCI-X Bus B Speed Enable corresponding to signal name PBI_AD10
This switch allows the user to enables 133 MHz on PCI-X segment B.
S7A1-4: PCI-X Bus B Speed Enable: Settings and Operation Mode
S7A1-4
Operation Mode
Open
Enables 133 MHz on PCI-X bus B.
Enables 100 MHz on PCI-X bus B (Default Mode).
Closed
3.9.6.4.5
Table 25.
S7A1-5: PCI-X Bus B Hot-Plug Reset Disable corresponding to signal name
PBI_AD11
This switch allows the user to enables or disable Hot-Plug Reset on PCI-X segment B.
S7A1-5: PCI-X Bus B Hot-Plug Reset Disable: Settings and Operation Mode
S7A1-5
Operation Mode
Open
PCI-X Bus B Hot-Plug Enable, normal reset mode disabled
Closed
PCI-X Bus B Hot-Plug Disable, normal reset mode (Default Mode).
3.9.6.4.6
Table 26.
Switch S7A1- 6: Hot Plug Capable Disabled corresponding to signal name
PBI_AD15
This switch allows the user to enable hot plug devices on the secondary PCI-X bus B.
Switch S7A1- 6: Hot Plug Capable Disabled: Settings and Operation Mode
S7A1-6
Operation Mode
Open
Hot Plug on Bus B Enabled
Disables Hot Plug on Bus B(Default mode)
Closed
41
Hardware Reference Section
3.9.6.4.7
Table 27.
Switch S7A1 - 7: SMBUS Manageability Address Bit 0 corresponding to signal name
PBI_AD17
This allows 80332 to address SMBus Slave Address bit 0 (PBI_A17).
Switch S7A1 - 7: SMBUS Manageability Address Bit 0: Settings and Operation Mode
S7A1-6
Operation Mode
Open
SMBus Manageablity Address Bit 0 = “1” (Default Mode)
SMBus Manageablity Address Bit 0 = “0”
Closed
3.9.6.4.8
Table 28.
Switch S7A1 - 8: SMBUS Manageability Address Bit 3 corresponding to signal name
PBI_AD18
This allows 80332 to address SMBus Slave Address bit 3 (PBI_A18).
Switch S7A1 - 8: SMBUS Manageability Address Bit 3: Settings and Operation Mode
S7A1-8
Operation Mode
Open
SMBus Manageablity Address Bit 3 = “1” (Default Mode)
SMBus Manageablity Address Bit 3 = “0”.
Closed
3.9.6.4.9
Table 29.
Switch S7A1- 9:SMBUS Manageability Address Bit 2 corresponding to signal name
PBI_AD17
This allows 80332 to address SMBus Slave Address2 (PBI_A17).
Switch S7A1 - 9: SMBUS Manageability Address Bit 2: Settings and Operation Mode
S7A1-9
Operation Mode
Open
SMBus Manageablity Address Bit 2 = “1” (Default Mode)
SMBus Manageablity Address Bit 2 = “0”.
Closed
3.9.6.4.10
Table 30.
Switch S7A1- 10: SMBUS Manageability Address Bit 1 corresponding to signal
name PBI_AD16
This allows 80332 to address SMBus Slave Address 1 (PBI_A16).
Switch S7A1 - 10: SMBUS Slave Address 0: Settings and Operation Mode
S7A1-10
Operation Mode
Open
SMBus Manageablity Address Bit 1 = “1” (Default Mode)
SMBus Manageablity Address Bit 1 = “0”.
Closed
42
Hardware Reference Section
3.9.6.5
Jumper J7D1: Flash bit-width
®
The Intel IQ80332 I/O processor evaluation platform board expects an 8-bit Flash enable.
Table 31.
Jumper J7D1: Descriptions
Jumper
Description
Factory Default
J7D1
8-bit Flash Enable
Open
Table 32.
Jumper J7D1: Settings and Operation Mode
Pins
Operation Mode
1-2
NC
Enables 16-bit Flash
8-bit Flash (default mode)
3.9.6.6
Jumper J1C1: JTAG Chain
Table 33.
Jumper J1C1: Descriptions
Jumper
Description
Factory Default
J1C1
JTAG Chain Enable
1-2
Table 34.
Jumper J1C1: Settings and Operation Mode
J1C1
Operation Mode
Pins 1, 2
Pins 3, 4
Pins 5, 6
Pins 7, 8
Enables JTAG Chain for IOP only (Default Mode).
Enables JTAG Chain for IOP + CPLD
Enables JTAG Chain for IOP + CPLD + GBE
Enables TRST# pull-down resistor
3.9.6.7
Jumper J1D2: UART Control
Table 35.
Jumper J1D2: Descriptions
Jumper
Description
Factory Default
J1D2
UART Control
Open
Table 36.
Jumper J1D2: Settings and Operation Mode
J1D2
Operation Mode
Pins 1, 2
NC
Disables UART/RS-232 port
Enables UART/RS-232 port (Default Mode)
43
Hardware Reference Section
3.9.6.8
Jumper J7B4: SMBus Header
Table 37.
Jumper J7B4: Descriptions
Jumper
Description
Factory Default
J7B4
SMBus Header
1-2, 3-4
Table 38.
Jumper J7B4: Settings and Operation Mode
J7B4
Operation Mode
Pins 1, 2
Pins 3, 4
Pins 5, 6
Pins 7, 8
Pins 9, 10
Pins 11, 12
Connects SM_SCLK to EEPROM U7B2 (Default Mode).
Connects SM_SDTA to EEPROM U7B2 (Default Mode).
Connects SM_SCLK to GE_SMCLK (for GBE control)
Connects SM_SDTA to GE_SMDAT(for GBE control)r
Connects SM_SCLK to PE_SMCLK (for PCI-E bus control)
Connects SM_SDTA to PE_SM_SDAT (for PCI-E bus control)
3.9.6.9
Jumper J9D3: Buzzer Volume Control
Table 39.
Jumper J9D3: Descriptions
Jumper
Description
Factory Default
J9D3
Buzzer Volume
Open
Table 40.
Jumper J9D3: Settings and Operation Mode
J9D3
Pins 2, 3
Pins 1, 2
NC
Operation Mode
Buzzer Volume Soft
Buzzer Volume Loud.
Buzzer Volume Off.
44
Software Reference
Software Reference
4
4.1
DRAM
®
For DDR SDRAM Sizes and Configurations, see theIntel 80332 I/O Processor Developer’s
Manual. This section also contains multiple examples of Address Register Programming.
®
See the Intel 80332 I/O Processor Design Guide, section 8, table 34 for supported DDR333 and
DDR-II configurations.
®
For all registers relating to DRAM and other MCU related registers, see the Intel 80332 I/O
Processor Developer’s Manual.
4.2
Components on the Peripheral Bus
The 80332 has a peripheral bus which contains the following peripheral devices:
• Flash ROM
• CPLD
• Audio Buzzer
• Rotary Switch
• Hex Display
Peripheral memory-Mapped Register Locations and all registers associated with PBI or the Peripheral
®
Bus Interface Unit can be found in the Intel 80332 I/O Processor Developer’s Manual.
45
Software Reference
4.2.1
Flash ROM
®
The Flash ROM is an 8 MB Intel StrataFlash (part# 28F640) that sits on the Peripheral Bus and is
accessed using PCE0.
Figure 12.
Flash Connection to Peripheral Bus
FLASH
28F640J3A
CS
16-bit
8 Mb
Intel® 80332
I/O
Processor
Intel® 80332 I/O Processor Bus
B3236-02
Under normal operation, the very first instruction access by the Intel XScale® core begins at location
0x0 on the 80332 Internal Bus. By default, address 0x0 is pointing to PCE0 where flash is located.
Currently, the Intel Flash Recovery Utility (FRU) cannot be used with the IQ80332. An alternative to
FRU would be to reprogram the flash through JTAG or using Redboot commands, when Redboot is
currently loaded onto the board. For more information on using Redboot to program the flash, please
see Redboot Manual.
46
Software Reference
4.2.2
Peripheral Bus Memory Map
Table 41.
Peripheral Bus Memory Map
Address Range (in Hex)
Size
Data Bus Width
Description
C000 0000 - C07F FFFF
CE80 0000 -CE80 FFFF
CE81 0000 -CE81 FFFF
CE24 0000 -CE82 FFFF
CE83 0000 -CE83 FFFF
CE84 0000 -CE84 FFFF
CE85 0000 -CE85 FFFF
CE86 0000 -CE86 FFFF
CE87 0000 -CE87 FFFF
CE8D 0000 -CE8D FFFF
CE8E 0000 -CE8E FFFF
CE8F 0000 -CE8F FFFF
8 MB
8-bit or 16-bit
8-bit
Flash memory (re-mapped)
Product Code
64 KB
64 KB
64 KB
64 KB
64 KB
64 KB
64 KB
64 KB
64 KB
64 KB
64 KB
8-bit
Board Stepping
CPLD Firmware Revision
Discrete LEDs
8-bit
8-bit
8-bit
Hex Display Left
Hex Display Right
Buzzer Control
32KB NV RAM
Rotary Switch
8-bit
8-bit
8-bit
8-bit
8-bit
ESN I/O
8-bit
Battery Status
47
Software Reference
4.3
Board Support Package (BSP) Examples
Examples provided in this section are based on the RedHat* RedBoot software running on the
IQ80332.
4.3.1
Intel® 80332 I/O Processor Memory Map
Figure 13 depicts the memory space for the 80332 (before RedBoot boots):
®
Figure 13.
Intel 80332 I/O Processor Memory Map
ADDRESS
0000 0000H
Memoryless Boot Registers
0000 0040H
ATU Outbound Direct Addressing Window
8000 0000H
ATU Outbound Memory Translation Windows
8800 0000H
Code / Data External Memory
ATU Outbound I/O Translation Window
9000 0000H
9001 0000H
Code/Data
External Memory
FFFF E000H
FFFF E900H
Peripheral Memory-Mapped Registers
I/O Processor Reserved
Reserved
Address
Space
External Memory
FFFF FFFFH
48
Software Reference
4.3.2
RedBoot* Intel® 80332 I/O Processor Memory Map
Size
(MB)
Virtual Address
Physical Address
Description
0x0000 0000
0x8000 0000
0x8800 0000
0x9000 0000
0x9010 0000
0xA000 0000
0xC000 0000
0xC080 0000
0xCE80 0000
0xCE90 0000
0xD000 0000
0xF00 0000
0x0000 0000
2048
128
128
1
SDRAM - 64-bit ECC
0x8000 0000
ATU Outbound Memory Translation Windows
*
Unused
0x9000 0000
ATU OUtbound I/O Translation Window.
*
255
512
8
Unused
0x0000 0000
SDRAM - 64 bit ECC Uncached
Flash (PCE0#)
Unused
0xC000 0000
*
224
1
0xCE80 0000
PCE1# - Uncached
Unused
*
23
*
512
1
Unused
0xF00 0000
*
Cache flush
0xF010 0000
254
Unused
PMMR - Intel® 80332 I/O Processor Memory Mapped
Registers. Please see Chapter 17 of the Intel® 80332 I/O
Processor Developer’s Manual for more details.
0xFFF0 0000
0xFFF0 0000
1
4.3.3
RedBoot Intel® 80332 I/O Processor Files
Attached in the kit, find a copy of the RedHat eCos for IQ80332 CD. Once the CD is installed, you
may find:
• The RedBoot initialization code source files from the following location:
From the installed directory:
..\RedHat\eCos\packages\hal\arm\xscale\iq80332\current\include
• The RedBoot binary image files (downloadable onto Flash) from the following location:
From the installed directory:
..\RedHat\eCos\loaders\iq80332
To access RedHat GNUPro tools including RedBoot binaries and source code, you may also go to the
following location on the Intel site:
49
Software Reference
4.3.4
RedBoot 80332 DDR Memory Initialization Sequence
In order to set the correct ECC bits, a DDR memory system (DIMM or discrete components) must be
written to with a known value. This process requires 64-bit writes to the entire DDR memory intended
for use. The following explains the sequence for memory initialization by RedBoot on an 80332 board
with an ECC DIMM. It also includes an example for the scrub (ECC initialization) code.
Initialization Sequence:
1. Disable interrupts. (Technically they are disabled at reset, but for soft reset this is included.
2. Init PBIU (Peripheral Bus Interface Unit) chip selects.
3. Enable I cache.
4. Move Flash to 0xF0000000.
5. Set TTB and Enable MMU.
6. Read DIM for memory parameters.
7. Set Memory Parameters.
8. Delay.
9. Turn DDRAM on.
10. Delay.
11. Enable Data Cache.
12. Enable BTB.
13. Flush all.
14. Clear ECC error logs.
15. Battery Test.
16. Enable ECC.
17. Scrub loop: Write zeros to all memory locations
mov
mov
mov
mov
mov
mov
mov
mov
mov
r8, r4
// save DRAM size
r0, #-1
r1, #-1
r2, #-1
r3, #-1
r4, #-1
r5, #-1
r6, #-1
r7, #-1
ldr
r11, = SDRAM_BASE
// scrub Loop
0:
stmia
subs
bne
r11!, {r0-r7}
r12, r12, #32
0
50
IQ80321 and IQ80332 Comparisons
IQ80321 and IQ80332 Comparisons A
This appendix provides a brief description for differences between IQ80332 and IQ80321. Please
®
®
also refer to application note: Intel 80321 Software Conversion to the Intel 80332 I/O Processor
Application Note.
®
®
Table 42.
Intel IQ80321 Evaluation Platform Board and Intel IQ80332 I/O processor
evaluation platform board Comparisons
Intel® IQ80332 I/O Processor Evaluation
Features
Intel® IQ80321 Evaluation Platform Board
Platform Board
I/O Processor
80332
Intel® 80321 I/O Processor
Core/Microprocessor
Technology
Intel XScale® microarchitecture
DDRII 400 MHz SDRAM DIMM
Intel XScale® microarchitecture
Memory Technology
PC1600 DDR SDRAM (100 MHz Clock)
PC board that attaches to a PC/Server/Backplane Extended PC board that attaches to a
by a PCI Express slot – Two PCI-X Expansion Slot PC/Server/Backplane – One PCI-X Expansion Slot
Form Factor
PC/Server/Backplane
Connection
PCI-X 133 MHz/64-Bits or
PCI 66 MHz/64 Bits
PCI Express
One PCI-X 100 MHz/64-bits
One PCI-X 133 MHz/64-bit
One PCI-X 2.0 266 MHz/64-bit
Expansion Card Slot
PCI/PCI-X Bridge
IBM PCI-X Bridge
PCI-X to PCI-X Bridge integrated with the
Reference: IBM 133 PCI-X Bridge
IQ80332l
External interrupts are routed through the XINT
pins on the 80321. They include INTA, INTB form
External interrupts are routed through the XINT
PCI-X expansion slot, INTA from 82544 GBE, and
UART interrupt – Steering and Status registers are
details.
Interrupt Routing
in 80321 – see Intel® 80321 I/O Processor
Developer’s Manual
Internal to 80332 – Refer to Intel® 80332 I/O
Processor Developer’s Manual
Internal to the 80321 - please refer to the Intel®
80321 I/O Processor Developer’s Manual
Timers
2-bit/33-100MHz multiplexed bus with six
chip-enables, Synch/Asynchronous (IQ80321
operates in 33 MHz Asynchronous mode) –
Refer to PBI section in the IIntel® 80321 I/O
Processor Developer’s Manual.
66 MHz multiplexed bus with two chip-enables,
Synch/Asynchronous (80332 operates in 66 MHz
Asynchronous mode) – Refer to PBI section in
Intel® 80332 I/O Processor Developer’s Manual
Local/Peripheral Bus
8-bit or 16-bit, 8 MB accessed through Peripheral 16-bit, 8 MB accessed through Peripheral Bus
Flash Memory
Bus with chip-enable 0 (PCE0)
with chip-enable 0 (PCE0))
One UART on the Peripheral bus – 16C550
device
Serial Debug Port
Two UARTs integrated within the 80332.
Network Debug Port
Rotary Switch
LED HEX Display
JTAG
Intel® 82545EM GbE on the 100 MHz PCI-X bus Intel® 82544 GbE on the PCI-X bus
Same
Same
Same
Same
20-PIN ARM Compliant
20-PIN ARM Compliant
Various Mictors
Logic Analyzer Connection Through PCI-X or PCI Express
51
IQ80321 and IQ80332 Comparisons
This Page Left Intentionally Blank
52
Getting Started and Debugger
Getting Started and Debugger
B
B.1
Introduction
This appendix pertains to Code|Lab version 2.3 and later which uses Microsoft's Visual Studio .NET.
For Code|Lab version 2.2 and earlier, refer to appendix B.
®
For more detailed information on JTAG and the 80332, please see the Intel 80332 I/O Processor
JTAG Support White Paper.
B.1.1
Purpose
The purpose of this appendix is to help the user setup and become familiar with the IQ80332
(IQ80332) and other related hardware and software. This appendix steps the user through an example
program using:
• Code|Lab EDE
• Code|Lab EDE debugger
• Macraigor* Raven* JTAG
This programming also includes:
• software setup
• compiling • linking
• debugging example code
The user tours the major features of the debugger and explores some of the basics of debugging. By
the end of this exercise, the user has been given a general understanding of the ATI* development
tools and can begin working on new applications.
B.1.2
Necessary Hardware and Software
This example uses the ATI Code|Lab plug-in for Microsoft* Visual Studio, the GNU* Pro compiler,
the Macraigor Raven JTAG connector, and the 80332.
B.1.3
Related Documents
Table 43.
Related Documents
Document Title
Document #
Intel® 80332 I/O Processor Developer’s Manual
Intel® 80200 Processor based on Intel® XScale™ Microarchitecture Developer’s Manual
Hot-Debug for Intel® XScale™ Core Debug White Paper
273517
273411
273539
Code|Lab Debug for ARMa
a.
This document installs to C:\Ati\docs\codelab debug.pdf.
Many of these documents load as part of ATI Code|Lab install (Start/Programs/ Accelerated
Technology/Documentation). This menu contains both the ARM* ADS and Code|Lab documents.
53
Getting Started and Debugger
B.2
Setup
B.2.1
Hardware Setup
®
set up the hardware.
• Connect the Raven to the host via the parallel port and to the evaluation board via the 20-pin
JTAG connector.
Note: The parallel port must be configured to EPP mode for the Macraigor Raven to work properly.
The parallel port setting can be changed in the BIOS setup program or in Control Panel. More
information on the Raven can be found at the Macraigor web site. Test software for the Raven is free
and available for download at:
• Connect a serial cable from the evaluation board to the host.
Note: The serial cable connects to the evaluation board with an RJ11 connector and connects to the host
computer serial port via an RJ11 to DB9F adaptor. The serial port configuration is covered in the
configuration section below.
• The 80332 plugs into a bus master PCI Express slot on the backplane or platform.
®
Figure 14.
Intel 80332 I/O Processor Hardware Setup Flow Chart
Host
Parallel Port Cable
Serial Cable
JTAG
20-Pin JTAG Connector
Evaluation Board
Backplane or PCI-X Platform
55
Getting Started and Debugger
B.2.2
Software Setup
ATI Code|Lab is a plug-in to Microsoft Visual Studio .NET, therefore Microsoft Visual Studio .NET must
already be loaded on the system. To load ATI Code|Lab, run setup.exe under the program directory.
Note: Do not install over an old version of ATI Code|Lab. When necessary, uninstall Code|Lab with
Add/Remove programs under the Control Panel before reinstalling.
To view the soft copies of document, Adobe Acrobat Reader is needed. The latest version can be
Figure 15.
Software Flow Diagram
ATI Code|Lab
Macraigor DLL
Debug Monitor Code
Resides in the Flash
Application Code
Loads into Memory
Flash
Memory
Evaluation Board
56
Getting Started and Debugger
B.3
New Project Setup
B.3.1
Creating a New Project
1. Launch Code|Lab EDE for .NET.
2. On the Start Page, select “New Project”.
a. The “New Projects” window appears.
b. Select “Code|Lab Projects” under Project Types and name the project “Project80332” in
the name field.
Note: The directory “Project80332” is created under the path specified in the Location box.
c. Click OK.
3. In the Code|Lab EDE Project Wizard Window:
a. Select “RedHat GNU Tools for XScale” under “Build Toolset”.
b. Select 80332 under “Project Template”.
c. Select “Application” under “Project Type”.
d. Click “Finish”.
4. Close the “Start Page” by clicking on the X in the top right corner of the Start Page window.
5. The new project is now in the “Solution Explorer” window. When this window is not open,
open it by “View, Solution Explorer”.
6. Right click on “Project80332” and select “Save Project80332”.
zip file (…/Tester1LED) from the Software Support section, containing the example code files
to the newly created project folder:
Tester1LED.zip
blink.c
blink.h
led.c
led.h
These files can be placed in any directory on the hard drive.
8. Add the newly downloaded files to the project:
a. In the “Solution Explorer” window, right click on “Project80332” and select “Add, Add
Existing Item”.
b. In the “Add Existing Item” window, use the drop-down menu under “Look In” to find the
four files listed in step 7 on the hard drive. Select all four files and click “open”. The
“Solution Explorer” window now shows these files under “Project80332”.
57
Getting Started and Debugger
B.3.2
Configuration
Examine the main menu of Code|Lab EDE for .NET.
• File
• Edit
• Project
• View
• code|lab EDE
• Build, Debug
• Tools
• Window
• Help
Since Code|Lab is a plug-in to Visual Studio, some of these menu items are Visual Studio and some
are specific to Code|Lab. Click on any of these menu items and the drop-down menu displays the
subordinate menu items. Many of these items have defined tool bar symbols, function keys, and
keyboard patterns as alternatives.
Note: Projects can be built under the “code|lab EDE” menu or under the “build” menu. Always use the
“code|lab EDE” menu to perform Code|Lab project builds. Builds under the “build” menu invoke
the Visual Studio C compiler.
1. On the main menu, select “code|lab EDE, Configuration”.
2. When the “code|lab EDE Configuration” window appears, click on each of the words in the
left box. Notice that the rest of the window changes when you click on different parts of the
menu tree. This is a typical feature of Code|Lab EDE for .NET.
3. Click on Toolsets.
4. Click on the drop-down arrow and select “RedHat GNU Tools for XScale”. The build tool
paths now appear in the box and must be modified as stated below in bold. Note that the
assembler and the linker are invoked by GCC.
a. “Compiler path: $(ToolDir)\BIN\XSCALE-ELF-GCC.EXE”.
b. “Assembler path: $(ToolDir)\BIN\XSCALE-ELF-GCC.EXE”.
c. “Linker path: $(ToolDir)\BIN\XSCALE-ELF-GCC.EXE”.
d. “Librarian path: $(ToolDir)\BIN\XSCALE-ELF-AR.EXE”.
5. In the left box, click on “Debugging, General”. When the checkboxes are available in your
version, set all four debug options to “false”.
6. Click “Apply” and click “OK”.
7. On the main menu, click “code|lab EDE, Project Settings”.
8. When the “code|lab Project Settings” window appears, click on “C/C++/Assembler” in the left
box. Use the drop-down arrow to select “C compiler” for “Build Tool”.
9. Edit the command line box at the bottom so that it contains the following:
-v -Wall -specs=redboot.specs -gdwarf-2 -O0 -c -mcpu=xscale $(InputRelPath) -o
$(OutDir)\$(InputName)$(OutputExt)
10. Use the drop-down arrow to select “Assembler” for “Build Tool. Edit the command line box at
the bottom so that it contains the following:
-v -specs=redboot.specs -o $(OutDir)\$(InputName)$(OutputExt) $(InputRelPath)
11. In the left box, click on “Linker”. Edit the command line box at the bottom so that it contains
the following:
-v -specs=redboot.specs -o $(OutDir)\$(ProjectName).elf $(ObjectFiles) $(Libraries)
12. Click “Apply” and then click “OK”.
13. In the “Solution Explorer” window, right click “Project80332” and select “Save
Project80332”.
58
Getting Started and Debugger
B.4
Flashing with JTAG
B.4.1
Overview
Code|Lab and Raven are capable of reading from, writing to, and erasing the contents of the Flash on
the evaluation board. The board comes with RedBoot loaded in the Flash. RedBoot is the RedHat
debug monitor which initializes the board and has some debug and diagnostic functions. It is capable
of serial communication with the console of a debug program or with Microsoft HyperTerminal, and
it prepares the board for accepting an application program.
Code|Lab invokes a Flash programmer written by Macraigor. More information on the Flash
programmer is located at:
ory_C ode=Software.
This Flash programmer only supports certain file formats: Intel Hex, Motorola srec and standard elf
(executable and linking format). RedBoot.s19 and RedBoot.srec are both srec files. TBD.i32 is an
ARM BootMonitor Intel Hex file. BootMonitor is an ARM version of a debug monitor, which is
similar but not identical to RedBoot.
Macraigor offers conversion tools to convert existing file types to a supported file type. These
conversion tools are located at:
C:\ATI\codelab\codelab Debug\Macraigor\Flash Programmer
The ReadMe.txt file describes the conversions tools. BinToS19.exe converts binary files to srec files
and MakeIntelHex.exe converts a.out files to Intel Hex files. When using the BinToS19.exe
conversion tool, use 0x0 for the starting address. For example, at the CMD prompt in the directory
where BinToS19.exe is located, the command line looks like this:
C:\ATI\codelab\codelab Debug\Macraigor\Flash Programmer>bintos19
C:\temp\redboot_ROM.bin 0x0 c:\temp\redboot_ROM.s19
59
Getting Started and Debugger
B.4.2
Using Flash Programmer
Note: The parallel port must be set to EPP mode or the Macraigor Raven does not work properly.
http://developer.intel.com/design/intelxscale/dev_tools/021022/index.htm RedBoot Debug Monitor
for the IQ80332.
1. Double click on the “Code|Lab Debug” icon on the desktop.
The Connection Window appears.
2. Select Macraigor JTAG Connect
a. Click Setup.
3. Select “ARM XScale”, correct LPT port, and “Raven” (do not press OK).
4. Click Additional Options…, check Enable Option, then press Configure
The Console Options windows now appears.
5. Console Port: (Set appropriately)
Baud Rate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Then Press OK, OK, OK (this returns to the Connect window).
6. Now press Connect.
Assembly code now visible.
7. Select “Memory/Flash…”
The OCDemon Flash Memory Programmer window appears.
8. The Flash programmer needs a file which is architecture specific, in this case. In the Flash
programmer window, select “File/Open”, then choose the file “Xscale TBD.ocd” at:
“C:\MGC\Embedded\codelab\codelab Debug\Macraigor\”.
9. Click the Program button.
10. Click Browse and “Files of type:” All Files, then choose the “redboot_ROM.srec” file
(downloaded and uncompressed from developer.com).
11. Check box “Erase Target Flash Sector(s) Before Programming”.
12. Click Program.
The Flash now programs and verifies; click Close when 100% complete.
13. Cycle power to the board to see that the LEDs on the board sequence “8.8.”, “A5”, “A6”,
“S.L”, then “A1”.
This is the normal LED sequence of RedBoot. The board may need to be reset more than once.
Explore the other features of the Flash programming window. The contents of the Flash can be
erased, copied to a file on the host, and verified against a file on the host.
60
Getting Started and Debugger
B.5
B.6
Debugging Out of Flash
JTAG debuggers can be used on two levels; with or without the source code. When the Flash is
programmed, the debugger can monitor the executable code, halt it, step through it, and monitor the
memory and registers. The executable code is disassembled so that the assembly code can be
examined.
Debugging with source code allows the user to examine the C code that is being executed. This
requires that the source code is available and linked by the debugger to the executable code that is
running on the evaluation board.
Building an Executable File From Example Code
1. Launch Code|Lab EDE and open “Project80332”.
2. Select “code|lab EDE, Rebuild Project”.
Note: A project can have more than one solution, but in this example, there is only one solution for the
project, so there is no difference between “Build Project” and “Build Solution” in this example.
Note: Rebuild cleans and builds. Clean deletes the old .o files in the project and build compiles, links, and
produces the executable files.
61
Getting Started and Debugger
B.7
Running the Code|Lab Debugger
This section is provided to get the system up and running in the Code|Lab Debug environment, but it
is not intended as a full-functional tutorial. Please refer to the ATI Code|Lab Debug Reference
Manual for more detailed information.
B.7.1
Launching and Configuring Debugger
1. In EDE, click on the icon that looks like a red bug. The “Connect” window appears.
perform steps 2-5.
3. Press Connect to enter debug mode.
a. The Code|Lab Debug environment appears with the Assembly window open.
Note: Mouseovers are available for most of the toolbar icons. (Leave the mouse over the debug icons
across the top on the toolbar to see a brief explanation of each.)
4. Click on the go icon and let RedBoot boot (takes a minute) until the RedBoot prompt
“RedBoot>” appears in the Console window (click the Console tab at the bottom of the Debug
window to view the Console window).
5. From the console window:
a. type “diag”.
b. hit “Enter”.
The RedBoot Diagnostic function is invoked.
Try out a few of the tests as desired.
6. Close the Debugger and EDE environment.
7. Reset the board (cycle power).
B.7.2
Manually Loading and Executing an Application Program
1. Launch the Code|Lab Debug Environment from the desktop icon.
2. Ensure “File…/Program Load Options/Load Executable and Symbols” is checked.
3. file, program load options, load executable and symbols.
a. Select “file, open program, browse”.
b. go find c:\<RedBoot downloaded Files>…\Test1LED\O\Test1LED.elf.
4. Hit Go (80, 3, 32, and 21 cycle on the LEDs).
5. Cycle power on the board.
62
Getting Started and Debugger
B.7.3
Displaying Source Code
1. Launch the Code|Lab EDE Debugger and open the “Tester1LED” ELF program.
Note: Use the File/Recent Programs menu for quick access.
2. Select the “Files” view in the lower tab of the WorkSpace window.
3. Bring up “blink.c” and “led.c” source code by double-clicking each filename.
4. Use the “Windows” Menu to arrange the windows, or maximize, minimize, and resize
manually as desired.
5. Press the “Mixed” tab at the bottom of the “blink.c” window. Notice that the assembly along
with each C statement.
6. Press the “Source” tab to revert back to C code only.
B.7.4
Using Breakpoints
Note the small gray circles on the sidebar beside each line of source code. Single-click any of these
gray circles and a red dot appears. The red dot represents a break point. Single-click the red dot to
remove it, or click the “Remove all breakpoints” icon.
Place a breakpoint on the following lines of code in “blink.c”:
displayLED(leds[8],leds[0]); /* LED display '80' */
displayLED(leds[0],leds[3]); /* LED display '03' */
displayLED(leds[3],leds[2]); /* LED Display '32' */
displayLED(leds[2],leds[1]); /* LED display '21' */
displayLED(leds[16],leds[16]); /* LED display ' ' */
1. Click the “Go” icon.
The yellow arrow stops at the first break point and the HEX display does not change.
2. Click the “Go” icon again.
The last instruction has now been executed and an “80” is displayed.
3. Continue on in this fashion, watching the lines execute only as they are called, while the
yellow arrow shows exactly what line is up next in execution.
4. Click the “Remove all breakpoints” icon.
5. Press “Go” again and notice that the program loop is infinite.
6. Press the “Halt” icon to stop execution.
7. Close the debugger and cycle power to the board.
63
Getting Started and Debugger
B.7.5
Stepping Through the Code
The “led.c” file contains a function that is called from code in “blink.c”. This exercise steps through
the code and utilizes a few of the most common step tools.
1. Launch the debugger, open Tester1LED, and open the “blink.c” and “led.c” files.
2. Set a breakpoint on the following line in “blink.c”: displayLED(leds[8],leds[0]); /* LED
display '80'*/
3. Press Go.
Program execution sit on the first breakpoint.
4. Press the “Step Over” icon and notice how execution jumps over the function call to the next
line of execution.
5. Now try the “Step Into” icon and note that the pointer has now jumped into the function
“displayLED”, which is located in the “led.c” file.
6. Press the “Step Over” icon again and watch the pointer advance within the function to the next
executable line.
7. Now press the “Step Out of” icon and notice how execution leaves the called function and
waits on the next executable line in “blink.c”.
8. The animate icon can also be used to provide a “Step Into” effect that occurs at a specified
time interval (default of 1 second). This can be modified in the “Settings” section of the
“View/Options” menu. Experiment with this as desired.
9. Use Halt to stop the animate mode before the next breakpoint.
10. Also note that Go can be pressed at any time to continue execution from the current line to the
next breakpoint or program end.
B.7.6
Setting Code|Lab Debug Options
Besides the Animate debug time interval setting briefly mentioned in step 8 of the previous exercise,
many useful options can be accessed from the “View/Options” menu.
1. Experiment here by bringing up the Registers window (click and change the view options
between binary and decimal; for example).
Hint: Settings tab, Interface, Radix
2. Also try bringing up the Memory window (click) and change the number of columns between
4 and 2 and notice the changes.
Hint: Settings tab, Memory Window, Number of Columns
Note: Press window icons a second time to remove them from view.
Again, there are many features of the debug environment not discussed here. Please see the Code|Lab
manuals for a full description of debug features.
64
B.8
Exploring the Code|Lab Debug Windows
This section discusses some basics of the debug environment. Some of these windows and concepts
have been dealt with during previous exercises in this manual. However, many new windows are also
discussed and basic interaction exercises are given. Begin this section by launching the Code|Lab
Debugger environment and connection via the JTAG port.
B.8.1
B.8.2
Toolbar Icons
Placing the mouse arrow on any icon displays the text function of that icon. When the icon launches a
special window (i.e., Watch, Memory, Call Trace, etc.), the icon brings that window up on the first
click and removes the window when pressed again.
Workspace Window
Click on the Workspace icon. Click on the Files and Browse tabs and examine the contents. Note that
there are more files than the original source files. When you double-click on the source files, blink.c
and led.c, the source window appears for that file. When you double-click on an included file, the
debugger is not be able to find the file.
B.8.3
B.8.4
B.8.5
Source Code
The source code windows are opened by double-clicking on the source files in the Workspace
window under the files tab. Viewing of mixed Assembly and C code or C code only, is controlled by
the tabs at the bottom of these windows.
4 Debug and Console Windows
The Debug window displays debugger activity messages while the Debug tab is displayed. Script
commands can be entered manually at the top of the window. Serial output is displayed while the
Console tab is active. Commands for the running application can be entered at the top of this window.
Memory Window
Click on the Memory window icon. Change the address at the top of the window to 0xffffe100 and
click on the green arrow to the right (or press Enter). This changes the viewable starting address of the
Memory window. The ATU header begins at 0xffffe100 and contains a known number (8086). Also
look at the base and limit registers for the memory and Flash devices, at 0xffffe508 and ffffe688
®
respectively, since they were initialized by RedBoot. Use the Intel 80332 I/O Processor Developer’s
Manual, to see what the values mean.
Note: The tabs at the bottom allow the selection of two memory regions to observe.
65
Getting Started and Debugger
B.8.6
Registers Window
Close all the active windows, then bring up the Registers window. Resize the this window and its
columns to get a good view of all the registers. Notice that there is a Flags tab at the bottom of this
window. This is useful for seeing the system flags defined by the CPSR. These are important
especially during conditional code execution (see the ARM Architecture Reference Manual for more
detail), but the flags are not changed during this exercise.
Click on the registers tab of the registers window and click the Animate icon. Notice how the register
values change during program execution (red values are those that were modified during the last
execution cycle). Click the Halt icon at any time, then try right clicking a register row and selecting
“Go To Memory”. Notice how the Memory window is brought up and the address contained in that
register is shown.
Click on the registers tab. Red means that the register value changed since the last fetch as opposed to
black which represents no change. Register values can be manually changed in this window.
B.8.7
Watch Window
It is often useful during the debugging process to keep an eye on a few select program variables.
1. Open the Tester1LED Program and bring up “led.c”.
2. Click the “Watch” icon to bring up the Watch window.
3. Now add the “left” and “right” variables from “led.c” to the watch window.
Note: For each variable double click the variable name to highlight it, then drag it to the watch window.
4. Click the “Animate” icon and observe the changes.
Note: When focus goes back to the Assembly window during this process, try putting a breakpoint in
led.c, then hit Go.
B.8.8
Variables Window
The Variables behaves very similarly to the Watch window, except that it shows all active variables.
Bring up the Variables window, click Animate, and watch the changes.
66
B.9
Debugging Basics
B.9.1
Overview
Debuggers allow developers to interrogate application code by allowing program flow control, data
observation, and data manipulation. The flow control functions include the ability to single-step
through the code, step into functions, step over functions, and run to breakpoint (hardware or
software). The data observation and manipulation functions include access to memory, registers, and
variables. The combination of the flow control and data functions allows the developer to debug
problems as they occur or to validate the application code. As the size of an application grows, the
need to be able to narrow down the cause of a problem to a few lines of code is imperative.
Debuggers have a finite set of capabilities and limitations. Debuggers can give insight that is difficult
to obtain without them, but they can fail when they are not used within the limits of their
functionality. They are intrusive by definition. They are software programs that interact with software
monitors or hardware (JTAG) to control a target program. Ultimately, the debugger works best when
the developer understands what it can and can not do and uses it within those constraints.
B.9.2
Hardware and Software Breakpoints
®
The following section provides a brief overview of breakpoints. See the Intel 80332 I/O Processor
Developer’s Manual, for more detailed information.
B.9.2.1
Software Breakpoints
Software breakpoints are setup and utilized via debugger utilities (such as Code|Lab). The abilities of
particular line of code, stepped through, and executed again to the next breakpoint via debuggers.
During this process, register values, memory address contents, variable contents, and many other
useful pieces of information can be monitored.
B.9.2.2
Hardware Breakpoints
Hardware breakpoints step and breakpoint in code in either ROM or RAM without altering the code,
stacks, or other target information. Hardware breakpoints handle difficult issues, by providing the
ability to set the processor conditions that cause the program to halt. Use hardware breakpoints to
locate problems such as reentrance, obscure timing, etc.
The 80332 contains two instruction breakpoint address registers (IBCR0 and IBCR1), one data
breakpoint address register (DBR0), one configurable data mask/address register (DBR1), and one
data breakpoint control register (DBCON). The 80332 also supports a 256 entry, trace buffer, that
records program execution information. The registers to control the trace buffer are located in CP14.
67
Getting Started and Debugger
B.9.3
C.9.3 Exceptions/Trapping
A debug exception causes the processor to re-direct execution to a debug event handling routine. The
®
Intel 80200 processor debug architecture defines the following debug exceptions:
• instruction breakpoint
• data breakpoint
• software breakpoint
• external debug break
• exception vector trap
• trace-buffer full break
When a debug exception occurs, the processor actions depend on whether the debug unit is
configured for Halt mode or Monitor mode.
68
|
