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.
31:8ReservedReserved0
7:0WIDTHWriting a value to this address indicates the
NOTE: The initial value for WIDTH of 10 ms will cause problems, if the baud rate of the tty0 port is less than 2400
Baud. If baud rates below 2400 Baud are used, this register must be programmed with a larger value.
3.7 CBUS UART, tty2
For details on programming the CBUS UART (TI 16C550C), see the data sheet from Texas Instruments [10]. The
clock frequency for baud rate calculations is 3.6864 MHz.
The UART registers of the UART are 8 bits wide and mapped on 64-bit aligned boundaries. These registers are
described in Table 3.15.
number of milliseconds in length a “Break”
must be on the tty0 port in order to trigger a
reset. Valid values are from 0 to 255.
A value of zero prevents this reset ever occurring.
Table 3.15 UART Registers. BASE = 0x1F00.0900
0x0A
(i.e., 10ms)
IIFIFO0x0000.0010R/WRead: Interrupt identification
Write: FIFO control
LCTRL0x0000.0018R/W
MCTRL0x0000.0020R/WModem control register
LSTAT0x0000.0028R/WLine status register
MSTAT0x0000.0030R/WModem status register
SCRATCH0x0000.0038R/WScratch register
1. The Divisor Latch Registers are accessible through RXTX and INTEN registers when bit 7
(Divisor Latch Access Bit) of the Line Control Register is set.
Line control register
1
3.8 General Purpose I/O
The Malta Board has eight GP inputs and eight GP outputs connected to the Core Board. For usage details, refer to
the documentation on the specific Core Board.
31:1ReservedReservedn/a
0I2CFPGA“1” means that the I2C controller in the FPGA
is enabled and the I2C controller in the South
Bridge is disconnected from the I2C bus.
“0” means that the I2C controller in the FPGA
is disabled and the I2C controller in the South
Bridge is connected to the I2C bus.
The board has an ATX (305 mm x 244mm) form factor and is in accordance with the ATX specification [12] with
regards to board size, mounting hole placement, connector placement, and height constraints.
The connector layout on the rear panel (namely, the shield design as described in Design Guide for Intel ATX Motherboard I/O Implementations Version 1.1 [13] is a subset of Intel Core design #1. This enables the Malta Board to be
installed in an ordinary ATX chassis. Figure 4.2 shows the rear panel connector layout.
Figure 4.2 Rear Panel Connector Layout
Mouse
Keyboard
Ethernet
Dual USB
4.1 Connectors & Jumpers
All jumpers are standard 0.1” pitch. A dot by a pin indicates pin 1. On all jumpers, pins are numbered crosswise, that
is, the end pins are 1 & 2 (this is not always the case on other connectors).
RefTypeDescription
J110 pin 0.1” headerDownload connector for CBUS FPGA EEPROM.
J210 pin 0.1” headerDownload connector for Arbiter EPLD.
J3200way headerConnects the Core Board. Carries amongst other things the CBUS.
J4200way headerConnects the Core Board. Carries amongst other things the primary
J5RJ45Ethernet.
Serial Port (tty0)Serial Port (tty1)
Parallel Port (1284)
Table 4.1 Interface Connectors
PCI bus.
Dual USB ATwo USB host ports.
J625 pin DSUBIEEE1284 / Flash programming port. This can either be used as a par-
Dual 9 pin DSUBtty0 (left) and tty1 (right).
J7Dual 6 pin miniDINConnection to a PC keyboard (lower) and mouse (upper).
J8ATX PSUThis connects the power.
J1840 pin 0.1” headerPrimary IDE interface. Pin 20 is removed from the connector.
J1940 pin 0.1” headerSecondary IDE interface. Pin 20 is removed from the connector.
J20Compact Flash con-
nector
J2134 pin 0.1” header
EJTAG connector. As per EJTAG specification, see Ref
removed from the connector.
Compact Flash interface at Secondary IDE interface.
Type I or II module.
Floppy Disk interface. Connects to FD via IDC ribbon cable (
bits from software. It also allows writing
to the Monitor Flash itself, regardless of
the state of the Lock bits.
Disables writing to the Monitor Flash lock
bits from software.
Page 28
Board Layout
RefSilkscreenPinsOptionsDefaultDescription
Table 4.2 Jumpers (Continued)
JP2EEWR2fit - notfitnotfitWhen fitted
Enables writing to the I
2
C EEPROM
(U14).
Do NOT fit this - it is reserved for production use.
When not
fitted
Disables writing to the
(U14).
I2C EEPROM
JP3CF MASTER2fit - notfitnotfitWhen fittedSets Compact Flash module as Master
IDE drive on the secondary IDE bus.
JP4PCI CLK610 - 37.5
33.33
When not
fitted
(2)
Sets PCI clock- frequency between 10MHz - 37.5MHz.
Sets Compact Flash module as Slave IDE
drive on the secondary IDE bus.
“X” = fitted.
MHz/Pins1-23-45-6
10
12.5
16.67
20
25
(1)
(1)
(1)
(1)
(1)
XXX
X
XX
X
X
Note 1: Only 10BASE-T is supported (100BASE-TX is not supported).
Note 2: Some Core Boards cannot run with a PCI clock frequency of 33.33 MHz. See the respective Core Board
User’s Manuals for maximum clock frequency.
4.2 Switches
Malta’s switches are described in Table 4.3. For those switches that are software-readable, a switch in position “ON”
or “CLOSED” (not in the “OPEN” position) will give a “1” in the appropriate register.
RefTypeDefaultDescription
S28-way
DIP
30
(1)
XX
33.33
37.5XX
Table 4.3 Switches
All OFFThis switch provides a value which can be read from the SWITCH register.
S5-1OFFWhen ON, enables Flash programming via 1284 parallel port.
S5-2OFFWhen ON, set operation mode to big endian.
S5-3OFFIf S5-3 is enabled and an SMP/CMP processor is detected (34K/1004K),
S5-4OFFWhen ON at power-on or at reset, sets YAMON in factory default mode e.g.,
n/aReset button.
n/aNMI/Power ON button. This button will bring the ATX power supply out of
stand-by. It also generates an NMI to the CPU, for example, to shut down the
PSU again.
This button causes a hardware shutdown if pressed for more than four seconds
at a PCI clock at 33MHz. For PCI clocks below 33.33 MHz, the button has to
be pressed for a longer period of time (up to 12 seconds).
This swithch enables writing to the Monitor Flash lock bits. It overrides
Jumper JP1.
If the endianess is changed, Malta must be reset again in order for the new
endian mode to take effect.
If the board is not reset unpredictable operation can occur.
YAMON will initialise all CPUs and place them in an idle loop early on in the
initialisation.
communication on tty0 port is forced to 38.4 kbaud, 8 bits/char, RTS/CTS
hardware handshaking and no parity.
DIP switches S2, S5-2, S5-3, and S5-4 are readable by software.
For the DIP switches S2 & S5, a switch referred to as “1” is marked by a dot or by a “0” in the silkscreen, or the
switch is marked by a “1”.
4.3 Displays / LEDs
The Malta Board has two displays and various individual status LEDs., described in Table 4.4. See also Section 3.5,
"Displays".
RefSilkscreenTypeDescription
D28n/a8-way barControlled by software.
U42n/a8 char ASCII
D7ATX ONGreen SMDIndicates that power is applied to the ATX power-supply.
D2STBYGreen SMDIndicates that power is applied to 3V3STBY (+/-5%) and
D65VGreen SMDIndicates that power is applied to 5V (+/-5%).
Table 4.4 LEDs
display
Used by YAMON to display status.
Can be used for any user purpose.
Also lit when board is in stand-by mode.
5VSTBY (+/-5%). Not led when board is in stand-by
mode.
The two LEDs, described in Table 4.5, are built-in to the RJ45 connector J5 and display status.
Table 4.4 LEDs (Continued)
RefSilkscreenTypeDescription
D43.3VGreen SMDIndicates that power is applied to 3.3V (+/-5%).
D5FPGAGreen SMDIndicates that CBUS FPGA programming completed OK.
D9RSTRed SMDIndicates that RSTN is active.
D1TXYellow SMDEthernet LED3: Blinks on TX Ethernet packets (Program-
mable).
D3SPD100Green SMDEthernet LED2: ndicates that 100 Mbit speed is selected
(Programmable).
Table 4.5 Ethernet Connector LED Functionality
LEDFunction
GreenEthernet LED0: Link up (Programmable)
YellowEthernet LED1: Activity (Programmable)
All four ethernet LEDs are programmed/controlled by the ethernet controller. LED0-LED3 are linked to the four
LEDs.
The board operates with 3.3V and 5V, supplied from a standard PC ATX power supply connected to J8. This should
be able to supply enough current for the board and all conceivable Core Board options. The 12V and -12V is only
connected to the Core Board (only 12V) and the AMR and PCI connectors. See [11] for details of a suitable supply.
Power On/Off is controlled by the South Bridge and its function is similar to a PC.
The board also supports Power Management Events, for eample, Wake On LAN events, used for powering up in
stand-by mode.
A push-button switch (S3) is provided to reset the board. Alternative sources of reset are:
•the CBUS FPGA, when a “magic” value is written to the SOFTRES register
•the EJTAG probe system reset signal (EJRSTN)
•an incoming break on the tty0 port (J6). This break may be disabled by software.
All resets are the same - there is no difference between a “warm” and a “cold” reset. All hardware, including hardware driven by stand-by voltages, are reset at reset.
5.5 Clocks
The PCI clock normally runs at 33 MHz, generated from a 14.31818 MHz crystal using a clock synthesizer/driver
(U13). The PCI clock can be configured via JP4 (see Table 4.1).
This will not affect the clock frequency of a CPU mounted on its Core Board; the Core Board generates its own clock.
5.4 Reset
The Malta Board contains the following clocks:
•RTC (32.768 KHz)
•CBUS UART (tty2) (3.6864 MHz)
•ISA Environment (14.31818 MHz)
•Ethernet (25 MHz)
•PCI clock (33 MHz - configurable to 10, 12.5, 16.67, 20, 25, 30, 33.33 and 37.5 MHz)
•CBUS FPGA (40 MHz)
•USB (48 MHz)
5.6 Interrupt Controller
The interrupt controller is located in the South Bridge device. An NMI interrupt controller (for South bridge NMI and
ON/NMI button) is located in the FPGA (see Section 3.2, "NMI Interrupts").
Interrupts routed to the South Bridge are triggered by the following devices:
•South Bridge internal devices (timer, real time clock, USB)
•SERR (PCI bus) and IOCHK (ISA bus) signals may trigger the South Bridge NMI interrupt
•Various power management related events in the South Bridge may trigger the South Bridge SMI interrupt
•I2C bus controller in the South Bridge may trigger either the South bridge SMI or IRQ9 interrupt
Interrupts routed directly to the Core Card are triggered by the following devices :
•Core card (COREHI, CORELO signals)
•Discrete 16550 UART device (CBUS UART (tty2))
Figure 5.2 shows the interrupt wiring. The figure does not include the connections of SERR from the PCI slots and
the Core Card to the South Bridge.
IRQ 0..15 from devices located in the Super I/O device are routed to the South Bridge using a serial connection.
PCI A..D interrupts including the South Bridge USB controller (using PCI D) are mapped on IRQ 0..15, which are
further multiplexed to South Bridge INTR.
Based on the interrupt sources, the South Bridge generates 3 interrupts : INTR, SMI, and NMI.
Most sources of interrupt are handled in an interrupt controller located in the South Bridge. A few are handled in the
CBUS FPGA (COREHI, CORELO and CBUS UART (tty2) interrupt), this means that CPU and CBUS interrupt
sources can be handled before the PCI bus has been configured. Please use the macros in the header file to access all
registers and fields of the interrupt controller, as described in [3].
IRQ 0..15 are prioritized in the sequence : 0, 1, 8..15, 3..7. IRQ 2 is reserved for cascading the two 82C59 devices that
together constitute the South Bridge Interrupt Controller.
The mapping of IRQ 0..15, as used by YAMON, is shown in Table 5.2.
IRQ #Source(s)Device(s)
0TimerSouth Bridge
1KeyboardSuperI/O
2Reserved by South Bridge (for cascading)
3UART (tty1)SuperI/O
4UART (tty0)SuperI/O
5Not used
6Floppy DiskSuperI/O
7Parallel port (1284)SuperI/O
8Real Time ClockSouth Bridge
Table 5.2 IRQ 0..15 Mapping
9
I2C bus
10PCI A, PCI B (including Ethernet)PCI slot 1..4, Ethernet
11PCI C (including audio),
PCI D (including USB)
12MouseSuperI/O
13Reserved by South Bridge
14Primary IDEPrimary IDE slot
15Secondary IDESecondary IDE slot/Compact flash connector
South Bridge
PCI slot 1..4, Audio, USB (South Bridge)
The mapping of CPU INT0..5 and CPU NMI is shown in Table 5.3.
Table 5.3 CPU INT0..5 and CPU NMI Mapping
CPU INT/NMISource(s)Device(s)
NMISouth Bridge NMI or NMI buttonSouth Bridge or On/NMI Buttom
0South Bridge INTRSouth Bridge
1South Bridge SMISouth Bridge
2CBUS UART (tty2)Discrete 16550
3COREHICore Card
4CORELOCore Card
5Not used, driven inactiveTypically used for CPU internal timer interrupt
There are 2 serial ports (tty0 and tty1) on Malta which are available on the rear edge via standard, male DB9 connectors (J6). These ports are provided by the Super I/O. A third serial port (tty2) is available via a 10-pin header (J22).
This port is provided by the discrete 16550. The pinout of these connectors is shown below:
Each port is electrically identical, with the pinout shown in the table below allowing full hardware handshaking.
The following 5-wire symmetric wired cable must be used to guarantee correct operation of the hardware flow control, which is used by YAMON. Pin connections between the two, 9-pole male connectors (for a standard PC serial
port):
•2 to 3 (RXD to TXD)
•3 to 2 (TXD to RXD)
•5 to 5 (GND to GND)
•7 to 8 (RTS to CTS)
•8 to 7 (CTS to RTS)
5.7.1 File Download
The recommended data terminal program for PCs running Windows OS is Procomm Plus32 from DATASTORM
TECHNOLOGIES. Here is the setup sequence for simple Motorola S-record file downloads:
Now select the ‘com’ port and click on the ‘Modem/ConnectionProperties’ to set the ‘baudrate’(=38400), ‘parity’(=none), data bits(=8), stop bits(=1) and important select ‘use hardware flow control’.
Download protocol setting in the menu area:
• Options->SystemOptions->ModemConnection->Data
Now set ‘current transfer protocol’ to ‘ASCII’, set all delays to ‘0’ and set the CR/LF options to ‘don’t translate
CR/LF’. The file to be downloaded (to Malta) is selected via the path:
• Data->SendFile
5.7.2 Serial Port Reset
The tty0 port (J6) can be used to reset the Malta Board. By default, a “Break” condition on the tty0 port for more than
10 ms will reset the board, exactly as if the reset button had been pressed. This functionality can be disabled, or the
time can be changed to a different value by programming the BRKRES register in the CBUS FPGA (see Section 3.6,
"Reset Control").
5.8 Ethernet
The Ethernet controller (U41 [8]) supports both 10base-T and 100base-TX standard on a twisted pair connection via
the rear panel connector J5. The device has an integrated PHY section and is capable of auto-negotiating the line
speed/duplex with the far end. Its MAC address is stored in the locally-connected EEPROM (U39) and must not be
altered.
Note: Only 10BASE-T is supported (100BASE-TXis not) for PCI clocking frequencies below 33.33 MHz (see Table
4.1).
See Section 4.3, "Displays / LEDs" for a description of the Ethernet LEDs, which are built into the RJ45 connector
and the on-board LEDs.
The ethernet controller supports Wake On LAN for remote wake-up. For additional information, see [8].
5.9 USB
Two host USB ports are available on a double connector (J5) on the rear edge of the board. These are controlled
through the South Bridge[6].
5.10 Keyboard / Mouse / IEEE1284 Parallel Port / Floppy Disk
These functions are provided by the Super I/O chip (U11)[9]. The PC keyboard and mouse are on a double mini-DIN
connector (J7), and the parallel (1284) port is on a 25-pin DSUB connector (J6), both on the rear board edge. The
floppy disk connector is header J21.
The parallel port also allows the user to reprogram the Flash memory, which is usually only done for production or
software upgrades. See Section 5.13, "Flash Memory".
The Super I/O supports one floppy disk, connected via a 34 wires ribbon cable (7 wires twisted, PC-style).
The South Bridge (U9) contains the Real Time Clock for the board [6]. The clock has an external battery backup
(CR2032 coin cell) (J10), which has an expected life time of 5-10 years.
5.12 IDE/CompactFlash (True IDE Mode)
The South Bridge (U9) provides both primary and secondary IDE busses [6]. The primary bus is brought out on connector J18, and may have both master and slave devices attached. The secondary bus connects both to the Compact
Flash connector J20 (Type I or II connector) and to the secondary IDE connector J19. Jumper JP3 selects whether the
Compact Flash module behaves as (if fitted) a master or (if not fitted) as a slave device. If a Compact Flash module is
used, any device plugged into the secondary IDE connector must have the opposite setting.
For additional information about Compact Flash modules, see [15].
5.13 Flash Memory
Malta is fitted with 4 Mbytes of Flash memory (refered to as Monitor Flash), which is used to boot the system. See
Chapter 3, “Memory Map” on page 13 for details of the Malta memory map.
5.11 Real Time Clock (RTC)
The Monitor Flash can be programmed via a download cable, as described in Chapter 6, “1284 Flash Download
Format” on page 45.
The Monitor Flash can also be reprogrammed by software. There is one protection mechanism:
•Jumper JP1 (See Section 4.1, "Connectors & Jumpers") must be installed for any writing to the Monitor Flash
Lock Bits from software.
Note that while the Monitor Flash is being reprogrammed by software, the code that performs the reprogramming
will have to be copied into RAM and executed there, because the Flash is inaccessible during this process.
All the Flash fitted are Intel 16 Mbit FlashFile devices. See Intel’s web site for the documentation, or see YAMON
documentation [3] for an easy-to-use software interface.
From a hardware viewpoint, the Flash appears as a 32-bit wide block, with no individual write control capability to
allow writing to just one, 16-bit halfword. However, this function can be achieved by software by running a
Read-Modify-Write cycle.
5.14 EEPROM
The I2C-connected EEPROM (U14) contains, on manufacture, the board serial number. The remaining locations in
the EEPROM are not available for application use.
A second EEPROM (U39) is directly connected to the Ethernet controller and is used to store the board’s MAC
address.
Connector J16 is an AMR connector [14] that allows an audio/modem interface card to be plugged into the motherboard. This is controlled via U23, a PCI Audio controller [7]. The AMR connector is a dual AC’97 audio codec interface.
5.16 Front Panel Connector
The Front Panel connector (J9), shown in Figure 5.3, contains all signals to/from the front panel of a normal PC-chassis. An additional connector (J30) is available for a three-pin Power LED connector.
Figure 5.3 Front Panel Connector
J9
HD LED
Reset Button
Reserved
5.17 Debug Access
5.17.1 Software Debug
The EJTAG connector (J17) allows connection of a suitable EJTAG debugger probe directly to the CPU. This allows
access to the internal hardware debug functionality of the CPU core. See [4] for details.
12
++
Power LED
On/NMI Button
Reserved
+5V
J30
1
+
Power LED
-
5.17.2 Hardware Debug
You have access to most, if not all, interesting signals on the Malta Board via testpoints (Table 5.5) and HP Logic
Analyser high-density connectors (Table 5.6). Refer to the tables below and the schematics for details of these.
The Malta Board’s Flash memory can be programmed and reprogrammed using a download cable that connects
directly to a PC parallel port. The CBUS FPGA can read data from this port and execute the appropriate erase/write
cycles in the Flash. The PC must be configured so that its printer port is set to “Generic - text only”, to avoid unpredictable escape sequences being sent. The file format is a sequence of ASCII encoded hex bytes as described below.
How to download:
•Connect the parallel cable between the PCs parallel port, and J6 on the Malta.
•Switch S5-1 on the Malta to ON or CLOSED.
•Switch both PC and Malta ON.
•Run the download script to dump the file to the parallel port on the PC or workstation.
•Switch S5-1 to OFF, and reset Malta.
•Disconnect the parallel cable.
According to the memory map in Chapter 3, “Memory Map” on page 13, the Monitor Flash is programmed on base
address 0x1E00.0000 or 0x1FC0.0000. If any address outside the Flash is addressed the attempt will be ignored.
Note: When programming the address 1FC0.0010 it is the Monitor Flash that is being programmed, but when reading
the address it is overridden and does NOT decode to an address in Flash, but rather to register address REVISION.
The only way to read the programmed value back is to read the “non-boot” Monitor Flash address, ie. address
0x1E00.0010. See Chapter 3, “Memory Map” on page 13.
The Malta Board’s Flash devices are organised in sectors of 64 Kbyte. “Erase” and “Set Lock Bit” commands operate
on exactly one sector, this being the sector currently addressed. After the last block of 16 words in a sector are written
into flash, the address counter has advanced to the next sector. This implies that a Set Address (@) to the sector has to
be executed before a Set Lock Bit command (!S) can be issued.
The file to be loaded into the Flash via the 1284 port has the following format:
Type:ASCII hex (both lower- and uppercase letters are accepted).
White space:Any characters below or equal to 20h are ignored (character 20h (space) is
allowed in the Print command. After the character 1Bh (start of a printer initialisation command) it ignores any character until next Reset Command.
Word width:32 bits (data has to be in blocks of 16 words and has to be placed on 16 word
boundaries).
The download codes, shown in Table 6.1, are used to control code download and Flash memory handling:
@Sets current writing/erasing address (in physical memory map format)
!RReset download system
!EErase the current Flash sector (64 KB)
!CClear all Flash lock-bits
!SSet current Flash sector lock-bit
#Comment (rest of line)
>Print command (shows next 8 characters in ASCII display, the com-
datadata has to be in blocks of 16 words, without interruption of any Com-
Table 6.1 Download Codes
mand needs exactly 8 non-white space characters). Any character
except for "!" and "#" may be printed - use of these in the print command is reserved.
ments (#) and Print Commands (>)
Example of code download format:
#Example
!R
@1E000000
!E
12345678 23456789 3456789A 456789AB
56789ABC 6789ABCD 789ABCDE 89ABCDEF
9ABCDEF0 ABCDEF01 BCDEF012 CDEF0123
DEF01234 EF012345 F0123456 01234567
# always 16 words in a block
After a Reset it will start at 1E00.0000 (the base of Monitor Flash), erase the base sector, and then write the 16 words
into offset 0.
If an error occurs during Flash download, an error message appears on the ASCII displays. The meaning of the error
messages is shown in Table 6.2.
Table 6.2 Flash Download Error Messages
MessageMeaning
Ill cmdIllegal command received, for example, “R” is received (not !R)
Ill !cmdIllegal “!” command received, for example, “!A” is received
Ill hexIllegal hex received (in data or addr), for example, “ABCDEFGH” both
Hex expHex expected (always data blocks of 16 words), for example, a com-
Err eraError in block erasure or clear lock-bits
Err progError in programming or set block lock-bits
Low voltLow programming voltage detected
Lock detMaster lock-bit, Block lock-bit or RP# lock detected
This chapter describes the external specification with which all Core cards must comply.
7.1 Required Interfaces
This section describes the interfaces that must be present on the Core card.
7.1.1 Power
Power supplies at 3.3V, 5V and 12V, positioned such that if a Core card is placed on the motherboard 180 degrees
incorrectly, all rails are shorted out by a number of pins. This should place the PSU in shutdown mode.
It is not guaranteed that the 5V rail will be present before the 3.3V rail.
7.1.2 PCI Bus
The interface to the core card includes a PCI bus. All core cards shall be 5V tolerant on inputs but drive 3.3V on all
outputs on the PCI bus.
7.1.3 Clock
The PCI bus clock is driven to the Core card from the motherboard. The Core card shall be able to run with this clock
at any frequency from 0-33MHz.
7.1.4 Revision Number
The Core card drives a processor-readable revision number, via pins CREV[7:0], down to the motherboard where the
CPU will be able to read them via the CBUS.
This revision number could for example be set via 8 fit/not-fit resistors.
7.1.5 I
2
C bus
An I2C bus is present on the interface. This will typically be used for interrogating SDRAM DIMMs. See User Manual for the address map.
7.1.6 Interrupts
Six interrupt signals to the MIPS CPU on the Core card are present, as is a single NMI interrupt signal, triggered by a
front-panel push button. Core cards must route all of these interrupts to the CPU—if the CPU chip has fewer external
interrupt pins, they should be ORed together.
The endian control signal, BIGEND, is driven by the motherboard according to setting of S5-2.
7.1.8 CBUS
The CBUS is designed to interface to simple devices on the motherboard which must be accessed by the CPU before
the PCI is up and running, or to devices with a low latency (for example, the interrupt controller and Flash memory).
CBUS signals are described in Table 7.2.
All core cards decode CPU addresses from 0x1C00.0000 to 0x1FFF.FFFF. These addresses are translated to
addresses 0x0000.0000 to 0x03FF.FFFF on the CBUS.
All CBUS signals must use 3.3 volt signalling levels. Read and write cycles are schown in Figure 7.1and Figure 7.2.
AC timing parameters are shown in Table 7.1.
CCSN inactive
T3Address hold from CCSN inactive20T4CRDN width120T5CRDN active to read data valid-120
T6CRDN inactive to data bus tristated-20
T7Read data hold time after CRDN inactive0T8Address valid to data bus driven0T9Write data setup to CRWN active0-
T10Write data hold time after CWRN inactive10T11CWRN pulse width75T12Address valid to read data valid-150
T13CCSN active to read data valid-150
10-
10-
7.1.9 EJTAG
The EJTAG signals from the “basic” EJTAG connector are taken to the interface from the front panel connector.
7.1.10 Misc.
Various debug, reserved, and presence-detect functions, as described in the following subsections.
The Core card interface signals are carried on J3 and J4, which are 200-pin (4-row) 1.27mm pitch connectors,
SAMTEC type MOLC-150-31-S-Q (male, fitted to Core card). The interface signals are described in Table 7.2.
Table 7.2 Core Card Interface Signals
Direction (from
Signal
INTN[5:0]Inputup-Interrupt signals to CPU.
NMINInputup-NMI signal to CPU
CD[31:0]I/O--CBUS data bus
CCSNOutput--CBUS chip select
CA[25:2]Output--CBUS Address
CRDNOutput--CBUS read strobe
CWRNOutput--CBUS write strobe
SCKI/O--IIC bus clock
SDAI/O--IIC bus data
CINTHINOutput-upCore card interrupt signal down to the moth-
CINTLONOutput-upCore card interrupt signal down to the moth-
CREV[7:0]Output--Indicates Core card revision as a 6.2 bit
BIGENDInput--Sets CPU Endianness.
EJTCKInput-down
EJTMSInput-up
EJTRSTNInput-down
EJTDIInput-up
EJTDOOutput-EJDINTInput-down
JTGCPUInput-downSets Core card’s JTAG output to come direct
CGPI[7:0]Output--General purpose output from Core which can
CGPO[7:0]Input--General purpose input to Core which the
CUU[15:0]---Unused pins, connected to wire-wrap area on
CPRESNOutputstrong
APRESNInputupstrong
D12VInput--Twelve volt power for possible fan
Core Card)
Pull (on Core
Card)
down
Pull (on
Motherboard)Description
erboard (high priority).
erboard (low priority).
binary number
from the CPU rather than also via other circuits.
be read from the motherboard.
motherboard can drive.
both Core and the motherboard.
upWired to zero, to indicate presence of Core
card.
Wired to zero on the motherboard, to indicate
D5VInput--5 Volt power
D3V3Input--3.3 Volt power
CPWR_OKInput--Indicates that power on both 3V3 and 5V rails
CORE_OKOutput-upIndicates that Core is ready to come out of
RSTNInput--Global reset signal.
PCI_AD[31:0]I/O--PCI bus
PCI_DEVSEL
N
PCI_CBEN[3:0
]
PCI_REQNOutput--PCI bus
PCI_GNTNInput--PCI bus
PCI_SERRNI/O--PCI bus
PCI_FRAMENI/O--PCI bus
PCI_IRDYNI/O--PCI bus
PCI_IDSELI/O--PCI bus
PCI_PARI/O--PCI bus
PCI_STOPNI/O--PCI bus
PCI_CLKInput--PCI bus
PCI_TRDYNI/O--PCI bus
PCI_LOCKNI/O--PCI bus
PCI_PERRNI/O--PCI bus
Core Card)
I/O--PCI bus
I/O--PCI bus
Pull (on Core
Card)
Pull (on
Motherboard)Description
is up.
reset.
7.2.1 J3 Connector
The pin list for the J3 connector is shown in Table 7.3.
Note that one corner pillar (top left in figure) is placed offset from a symmetrical position, which is to guarantee the
board cannot be inserted the wrong way around.
The connectors chosen are low-insertion force. You should be able to “lever” the card up by placing a screwdriver
between the mounting pillars and the card.
The Core card is mounted at a height of 11mm over the motherboard when using the connectors given above. However, the existing placement of high components on the Atlas and Malta motherboards results in the height restrictions when placing components on the Core board, as shown in Table 7.5.
Table 7.5 Core Card Component Height Restrictions
LocationHeight Restrictions on Underside
Whole card (default)No underside SMDs thicker than 6.5mm
Zone 1No leaded components at all. No underside SMDs thicker than 1.2mm. (Note: this
requirement applies only to Core cards that must be compatible with Atlas. Malta
does not have this restriction.)
Zone 2No underside SMDs thicker than 4.4mm
Zone 3No underside SMDs thicker than 4.4mm
This appendix lists other documents available from MIPS Technologies, Inc. that are referenced elsewhere in this
document. These documents may be included in the $MIPS_HOME/$MIPS_CORE/doc area of a typical Core-Name soft or hard core release, or in some cases may be available on the MIPS web site, http://www.mips.com.
1.PCI Local Bus Specification
Revision 2.2. December 18, 1998
Change bars (vertical lines) in the margins of this document indicate significant changes in the document since its last
release. Change bars are removed for changes that are more than one revision old.