Unpublished rights (if any) reserved under the copyright laws of the United States of America and other countries.
This document contains information that is proprietary to MIPS Technologies, Inc. ("MIPS Technologies"). Any copying, reproducing, modifying or use of
this information (in whole or in part) that is not expressly permitted in writing by MIPS Technologies or an authorized third party is strictly prohibited. At a
minimum, this information is protected under unfair competition and copyright laws. Violations thereof may result in criminal penalties and fines.
Any document provided in source format (i.e., in a modifiable form such as in FrameMaker or Microsoft Word format) is subject to use and distribution
restrictions that are independent of and supplemental to any and all confidentiality restrictions. UNDER NO CIRCUMSTANCES MAY A DOCUMENT
PROVIDED IN SOURCE FORMAT BE DISTRIBUTED TO A THIRD PARTY IN SOURCE FORMAT WITHOUT THE EXPRESS WRITTEN
PERMISSION OF MIPS TECHNOLOGIES, INC.
MIPS Technologiesreserves the right to change the information contained in this document to improve function, design or otherwise. MIPS Technologies does
not assume any liability arising out of the application or use of this information, or of any error or omission in such information. Any warranties, whether
express, statutory, implied or otherwise, including but not limited to the implied warranties of merchantability or fitness for a particular purpose, are excluded.
Except as expressly provided in any written license agreement from MIPS Technologies or an authorized third party, the furnishing of this document does not
give recipient any license to any intellectual property rights, including any patent rights, that cover the information in this document.
The information contained in this document shall not be exported, reexported, transferred, or released, directly or indirectly, in violation of the law of any
country or international law, regulation, treaty, Executive Order, statute, amendments or supplements thereto. Should a conflict arise regarding the export,
reexport, transfer, or release of the information contained in this document, the laws of the United States of America shall be the governing law.
The information contained in this document constitutes one or more of the following: commercial computer software, commercial computer software
documentation or other commercial items. If the user of this information, or any related documentation of any kind, including related technical data or manuals,
is an agency, department, or other entity of the United States government ("Government"), the use, duplication, reproduction, release, modification, disclosure,
or transfer of this information, or any related documentation of any kind, is restricted in accordance with Federal Acquisition Regulation 12.212 for civilian
agencies and Defense Federal Acquisition Regulation Supplement 227.7202 for military agencies. The use of this information by the Government is further
restricted in accordance with the terms of the license agreement(s) and/or applicable contract terms and conditions covering this information from MIPS
Technologies or an authorized third party.
MIPS, MIPS I, MIPS II, MIPS III, MIPS IV,MIPSV, MIPS-3D, MIPS16, MIPS16e, MIPS32, MIPS64, MIPS-Based, MIPSsim, MIPSpro, MIPS Technologies
logo, MIPS-VERIFIED, MIPS-VERIFIED logo, 4K, 4Kc, 4Km, 4Kp, 4KE, 4KEc, 4KEm, 4KEp, 4KS, 4KSc, 4KSd, M4K, 5K, 5Kc, 5Kf, 24K, 24Kc, 24Kf,
24KE, 24KEc, 24KEf, 34K, 34Kc, 34Kf, 74K, 74Kc, 74Kf, 1004K, 1004Kc, 1004Kf, R3000, R4000, R5000, ASMACRO, Atlas, "At the core of the user
experience.", BusBridge, Bus Navigator, CLAM, CorExtend, CoreFPGA, CoreLV, EC, FPGA View, FS2, FS2 FIRST SILICON SOLUTIONS logo, FS2
NAVIGATOR, HyperDebug, HyperJTAG, JALGO, Logic Navigator, Malta, MDMX, MED, MGB, OCI, PDtrace, the Pipeline, Pro Series, SEAD, SEAD-2,
SmartMIPS, SOC-it, System Navigator, and YAMON are trademarks or registered trademarks of MIPS Technologies, Inc. in the United States and other
countries.
All other trademarks referred to herein are the property of their respective owners.
2.3: Wiring It Up................................................................................................................................................12
3.8: General Purpose I/O.................................................................................................................................. 20
5.1: PCI Bus ..................................................................................................................................................... 31
5.3: Power ........................................................................................................................................................ 32
5.7: Serial Ports................................................................................................................................................ 37
5.7.2: Serial Port Reset.............................................................................................................................. 38
5.11: Real Time Clock (RTC) ........................................................................................................................... 39
5.12: IDE/CompactFlash (True IDE Mode)....................................................................................................... 39
Table 4.5: Ethernet Connector LED Functionality................................................................................................... 30
Table 5.1: IDSEL and INT# for PCI Devices........................................................................................................... 31
Table 5.3: CPU INT0..5 and CPU NMI Mapping..................................................................................................... 36
Table 5.4: Serial Port Pinouts ................................................................................................................................. 37
This document is the primary reference document for the Malta™ Development Board.
1.1 Overview
The Malta Board provides a standard platform for software development with MIPS32® and MIPS64® processors.
The platform is composed of two parts: the Malta Motherboard, which holds the CPU-independent parts of the circuitry, and one or more CoreLV or CoreFPGA Core boards, which hold the MIPS CPU plus its System Controller
and fast SDRAM memory.
The Malta Board is designed around a standard PC chipset, which provides all the advantages of easy-to-obtain software drivers. It is supplied with the YAMON ROM monitor in the on-board Flash memory, which can be reprogrammed from a PC or workstation via the IEEE1284 port. The feature set extends from low-level debugging aids,
such as DIP switches, LED displays, and logic analyzer connectors, to sophisticated EJTAG debugger connectivity,
audio support, IDE. flash disks and Ethernet. Four PCI slots on the board give the user a high degree of flexibility in
extending the functionality of the system. The board is an ATX form factor and is intended to be used in an ATXcabinet.
The major components of the Malta Board are shown in Figure 1.1 and listed below:
•ATX form factor
•Daughter card hosting either an FPGA implementation of a synthesizable core or a Lead Vehicle
The Core board shown in Figure 1.1 is a typical implementation. Though the Core Board is not strictly within the
scope of this document, it is worth noting that all Core Boards conform to the same interface specification, which is
described in Chapter 7, “Core Card Design” on page 49. Also worth noting is that most Core Boards generate their
own clock, independently of the PCI clock. Nothing on Malta is synchronized to the Core Board clock—the CBUS
protocol is asynchronous by nature. The CBUS allows the CPU to access peripherals, which either have to be available before the PCI bus has been configured (for example, the Flash memory from which it boots) or those that
require simple, low-latency access (for example, the debug LEDs and ASCII display, the tty2 port. and so on).
The PCI bus is 32-bit, 33 MHz PCI standard version 2.2 compliant (Reference [1]), and allows devices on the bus
DMA access to the DRAM on the Core Board. Four 5V PCI slots are provided on Malta to allow insertion of optional
peripherals (for example, a video controller), and also to provide a way of monitoring traffic on this bus. The PCI bus
contains the following components:
•Core Board connector for connection to the system controller on the Core Board.
•Intel PIIX4E South Bridge, 82371E (U9).
•AMD Ethernet controller, Am79C973 (U41).
•Crystal Audio controller, CS4281 (U23).
•Four 5V, 32 bit PCI connectors (J12-J15) that can be used for debug / trace purposes or for installation of a
PCI board.
The Malta Board has a PC-like structure with a South Bridge. An ISA bus is attached to the South Bridge for connection with the Super I/O (U11). The Super I/O contains the following components:
•PS/2 Keyboard and Mouse (J7).
•1284 parallel port (J6).
•Two serial ports tty0 and tty1 (J6).
•Floppy drive, only drive A supported (J21).
The Monitor Flash is used to boot the system.
In addition to the YAMON monitor, the Malta Board includes a sample Linux port. BSPs for Microsoft® Windows®
CE, Nucleus Plus, and Windriver Systems VxWorks are also available.
In addition to the basic Malta motherboard, you will typically need:
•a suitable standard ATX cabinet with power supply. For a power supply with stand-by capabilities, a minimum
current of 720 mA is required (1A/1.5A peak recommended) for the 5V stand-by voltage.
•the Core Board that contains the MIPS CPU
•a serial cable for RS232 serial connection. The cable must be a Null Modem cable with 9 way ‘D’ female connector in both ends.
2.2 Optional Hardware
The following may also be useful, depending on your application:
•Ethernet cable
•USB cable
•PS2 Keyboard / mouse
•IDE disk drive and cabling
•Type I or II CompactFlash module (supporting True IDE mode)
•Floppy disk drive and cabling
The following are useful for debugging:
•LA probe connectors (that match the AMP Mictor headers) if you have an HP Logic Analyser
•PCI probe board, if you want to be able to monitor activity on the internal PCI bus (for example, FuturePlus
FS2000)
•Standard parallel-port download cable for extending the parallel male-male conversion cable
•Standard 10-pin header to DB9 converter cable for tty2
Begin by connecting the Core Board to the Malta motherboard. Notice that the connectors J3 and J4 have the same
numbers on both boards, and one of the corner mounting pillars is offset to prevent incorrect insertion. When removing the Core Board at some later date, be careful not to bend it. Under each corner of the Core Board is a mounting
pillar, with a gap where a screwdriver can be inserted to gently lever it up. Only apply the screwdriver to the PCB
area around the mounting holes to avoid accidently cutting any tracks.
Before turning on the power, you will probably want to have set up the following:
•tty0. The supplied PROM monitor (YAMON) by default prints its welcome message via the tty0 port (J6), using
38.4 kbaud, 8 bits/char, RTS/CTS hardware handshaking, without parity. A 5-wire cable is sufficient. The implemented signals must be RXD, TXD, RTS, CTS, and GND. See Section 5.7, "Serial Ports" for the serial connector
pinout.
•Ethernet. Twisted-pair ethernet cable will plug into the socket on the rear edge of the board. This will auto configure at 10 or 100Mbit/s, half/full-duplex.
•Check that the settings of S5 switches are correct, as specified in Section 4.2, "Switches".
2.4 Power-up Sequence
When you connect the power supply and switch it on, the board is powered up. Check that the green “ATX ON”,
“3V3”, “5V”, and “STBY” LEDs are on, indicating good power.
NOTE: With some ATX supplies, Malta draws so little current that the supply is not stable. This is technically a
deviation from the ATX spec.
NOTE: The board is brought into “stand-by” mode by pressing the switch marked “ON/NMI” (S4) for more than
four seconds. The “ATX ON” LED is lit when in “stand-by” mode. Press “ON/NMI” to bring up the board again.
The green “FPGA” LED should be on, indicating that the board’s FPGA has booted.
The red “RST” LED should be off. If it is lit, it indicates that something is holding the board in reset.
When the CPU initially boots, YAMON signs-on using the tty0 serial port (the left one) with information about the
board’s configuration, for example, board revision, SDRAM size, etc.
You should now arrive at YAMON’s prompt line. Simultaneously, you should see the word “YAMON”on the ASCII
LED display. If you do not see this, check the YAMON User’s Manual for the meaning of the displayed messages.
Yamon’s help command lists the available commands, and help <command name> gives more detailed information about a specific command.
The board’s default mode is little endian. You can change to big-endian using S5-2, as described in Table 4.3.
This chapter describes the Malta Board’s memory map and its control/status registers as seen by the CPU. The memory map showing the starting addresses of the major devices on the board is shown in Table 3.1.
Base AddressSizeFunction
Table 3.1 Malta Physical Memory Map
0000.0000
0800.0000256 MbytesTypically PCI
1800.000062 MbytesTypically PCI
1BE0.00002 MbyteTypically System controller’s internal registers
1C00.000032 MbytesTypically not used
LEDs
ASCII display
Soft reset
FPGA revision number
CBUS UART (tty2)
General purpose I/O
2
I
C controller
1F10.000011 MbytesTypically System Controller specific.
1FC0.00004MbyteMaps to Monitor Flash
1FD0.00003 MbytesTypically System Controller specific.
The shaded area of the table indicate memory areas whose mapping depends on the implementation of the
Core Board and on software.
The memory area 000F.0000-000F.FFFF (PC BIOS area) is only accessible from the CPU and not from the
PCI bus (the South Bridge decodes this memory area).
Note: Address 1FC0.0010 in Flash memory is “special”—a read from this address reads the contents of the Revision
register, allowing software to identify the hardware environment and configure itself accordingly. The next address,
1E00.0010, decodes to an address in Flash memory.
RAM is typically mapped at the bottom of memory, so that exception vectors are located in fast memory.
Malta does not specify a mapping for addresses above 0x2000.0000. These addresses are accessed via kuseg, using
mapping defined by TLB entries.
The I2C bus (called the SMB bus in the Intel documentation) is controlled by the CBUS FPGA (it can also be controlled by the controller in the South Bridge). The I2C bus address map is shown in Table 3.2.
Note that all addresses shown are physical addresses. You should use the macros in the header files to access all registers and fields [3].
All registers are addressed as 32-bit words, on 64-bit word boundaries. This convention allows software to access all
registers using the same word address in both big- and little-endian modes. Those registers that contain a single value
are not described in bit-field detail; these values occupy the least-significant bit of the register.
3.1 Revision Information
The Revision register contains information about the revision of the Malta and Core Boards.
7:4PROID4-bit binary number gives product ID0x2
3:0PRORV4-bit binary number gives product revision.n/a
3.2 NMI Interrupts
There are two sources of NMI:
•ON/NMI push button
•South Bridge due to assertion of PCI SERR (from PCI slot or Core card) or assertion of ISA IOCHK.
When the ON/NMI push button is activated, the signal is debounced and latched in the NMI interrupt controller. The
South Bridge NMI is routed through the NMI controller as it is. These signals then generate an active state on the
NMIN pin of the MIPS Core Board. The NMISTATUS register can be read to determine the cause of the NMI.
31:1ReservedReservedn/a
1SBPending NMI from the South Bridgen/a
0ONNMIPending NMI from the ON/NMI push buttonn/a
3.3 NMI Acknowledge
The ON/NMI interrupt is by nature transient. Therefore it is debounced and latched and thereafter treated as an ordinary level-based interrupt in the NMI interrupt controller. The NMI interrupt can be cleared by writing a “1” to the
NMIACK register. Note that South Bridge NMI is acknowledged in the South Bridge.
31:1ReservedReservedn/a
0ONNMIWrite 1 to acknowledge ON/NMI NMIn/a
3.4 Switches / Status
The SWITCH, STATUS, and JPMRS registers allow software to monitor the state of various switches and jumpers
on the Malta Board. All DIP switches have a value of “1” for a switch in the “ON” position.
A switch is considered ON if any of the following are true:
•It is in the position marked “ON” on the switch body.
•It is in the position marked “CLOSED” or not in the “OPEN” position as marked on the switch body.
There is no debouncing on these registers, so if software wants to monitor a value while it changes, allowance for this
must be made by waiting for the new value to become stable.
Table 3.5 NMIACK Register
For the DIP switches S2 & S5, bit 0 is marked by a dot or by a “0” in the silkscreen, or the switch is marked by a “1”.
31:5ReservedReserved0
4:2PCICLKPCI clock frequency 10-37.5MHZ
See Table 4.2
Bit 4 is Pins 5-6
Bit 3 is Pins 3-4
Bit 2 is Pins 1-2
“1” = jumper fitted
1EELOCK
0ReservedReserved0
State of JP2: Not fitted ~ “1” =
write protected.
I2C EEPROM
n/a
n/a
3.5 Displays
There are 2 display devices on the board: an 8-LED array (D28 is a 10-LED, but only 8 are used), and an 8-character
ASCII display (U42). These are controlled using the registers shown in Table 3.9 through Table 3.12.
Table 3.9 Display Registers. BASE = 0x1F00.0400
Register NameOffset AddressAccessFunction
LEDBAR0x0000.0008R/W8 bits each corresponding to 1 LED.
ASCIIWORD0x0000.0010WOWriting a 32-bit word to this register
ASCII display position ‘0’. Position ‘0’ is the
left-most positioned character.
There are two reset functionalities that are controlled by software: writing a “magic” value to the SOFTRES register
immediately triggers a reset of the whole board, and the BRKRES register controls how the “break” condition on the
tty0 port is monitored. Both reset functions generate a board reset with the exact same effect as if you had pressed the
reset button.